[MGNLPN-164] Variants node isn't added as first child node Created: 12/Jun/14  Updated: 18/Jun/14  Resolved: 18/Jun/14

Status: Closed
Project: Magnolia Personalization
Component/s: Integration
Affects Version/s: 1.0
Fix Version/s: 1.0

Type: Bug Priority: Critical
Reporter: Andreas Weder Assignee: Roman Kovařík
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

eeBundle snapshot: magnolia-enterprise-bundle-5.3-20140612.072113-288
eeBundle snapshot: magnolia-enterprise-bundle-5.3-20140612.210538-295


Attachments: PNG File Variants node not first.png    
Issue Links:
Relates
relates to MGNLPN-181 Sort order of variants node is not ac... Closed
duplicate
duplicates MGNLPN-86 Variants node should be ordered as fi... Closed
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)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:

 Description   

When I create a new variant of a page with child nodes, the "Variants" node is not added as first node, but as the last.



 Comments   
Comment by Roman Kovařík [ 12/Jun/14 ]
  1. We could order variants node as first child when added
    a newly added page can be still ordered before variants node
    still better then scroll hundred pages down
    quick win
  2. Custom container
    keeps variants node as first child no matter what.
Generated at Mon Feb 12 06:34:56 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.