[MGNLPN-362] As an editor, I want to use page and component variants on the same page Created: 02/Feb/17 Updated: 08/Mar/17 Resolved: 10/Feb/17 |
|
| Status: | Closed |
| Project: | Magnolia Personalization |
| Component/s: | Component p13n, Integration |
| Affects Version/s: | None |
| Fix Version/s: | 1.3.3, 1.4.2 |
| Type: | Story | Priority: | Neutral |
| Reporter: | Antti Hietala | Assignee: | Roman Kovařík |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Σ Remaining Estimate: | 2m | Remaining Estimate: | Not Specified |
| Σ Time Spent: | Not Specified | Time Spent: | Not Specified |
| Σ Original Estimate: | 2m | Original Estimate: | Not Specified |
| Issue Links: |
|
||||||||||||||||||||
| Sub-Tasks: |
|
||||||||||||||||||||
| 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)
|
||||||||||||||||||||
| Release notes required: |
Yes
|
||||||||||||||||||||
| Documentation update required: |
Yes
|
||||||||||||||||||||
| Sprint: | Kromeriz 83 | ||||||||||||||||||||
| Story Points: | 5 | ||||||||||||||||||||
| Description |
|
Remove the restriction on page+comp personalization. Allow both on the same page at the same time. Background: By default, page and component personalization are mutually exclusive. You can either personalize a page or its components but not both at the same time. This restriction was put in place to avoid creating complex page-and-components personalization scenarios that might be confusing for editors. Some editors feel they can handle the complexity and would like to have the restriction removed. Provide configuration that allows editors to manage page and component variants on the same page. |