[MGNLPN-343] As an editor I want to promote a variant to replace the original Created: 19/Oct/16 Updated: 11/Mar/21 Resolved: 11/Mar/21 |
|
| Status: | Closed |
| Project: | Magnolia Personalization |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Story | Priority: | Neutral |
| Reporter: | Jan Schulte | Assignee: | Unassigned |
| Resolution: | Won't Do | Votes: | 2 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
| Date of First Response: |
| Description |
|
Sometimes a variant must be promoted to replace the original. This is especially important when a winning scenario was found in AB testing. This should work for page variants and component variants. So the following functionality is missing:
|
| Comments |
| Comment by Andrew Warinner [ 20/Oct/16 ] |
|
This functionality popped up from another partner for a customer:
Would there be any implications for versioning of the parent page? |