[MGNLUI-1129] Node order should not matter when configuring node types Created: 16/Apr/13  Updated: 24/Feb/16  Resolved: 08/Aug/13

Status: Closed
Project: Magnolia UI
Component/s: tree/list
Affects Version/s: 5.0
Fix Version/s: 5.1

Type: Bug Priority: Major
Reporter: Antti Hietala Assignee: Federico Grilli
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

build #38 (Apr 12, 2013)


Attachments: PNG File correct-order.png     PNG File wrong-order.png    
Issue Links:
causality
is causing MGNLUI-3165 Filtering of content shown in workben... Closed
relation
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 configuring node types for a workbench, the order in which you configure them matters. But it should not matter. For example, if your content app supports folders and some custom node type, you need to configure the custom node type first. Otherwise the Tree view displays only the folders and the List and Thumbnail views display the folders only (if there's any). This is a problem because in a typical content app you have at least two node types: folders and your custom nodes. Have to be really careful with the order.


Generated at Mon Feb 12 08:43:38 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.