[MAGNOLIA-167] data nodes in Config should be sorted alphabetically Created: 02/Nov/04  Updated: 17/Mar/09  Resolved: 12/May/06

Status: Closed
Project: Magnolia
Component/s: admininterface
Affects Version/s: 2.0 Final
Fix Version/s: None

Type: Improvement Priority: Trivial
Reporter: Boris Kraft Assignee: Philipp Bärfuss
Resolution: Won't Fix Votes: 0
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   

Currently data nodes in the Config dialog are in some arbitrary order, differing for each content node. This makes it difficult to find a node if you have more than a handful of them. I suggest that the data nodes (properties of a content node) are listed in alphabetical order.



 Comments   
Comment by Bert Schulzki [ 14/Apr/05 ]

This is a a bit complicated as there might be a module that requires a custom order of the node data element.
But as i also understand agree with the wish for alphabetically ordered data nodes, i would suggest to change issue that way:

The user should be able to switch between natural or alphabetical sort order.

This (together with sorting by date) should also apply to all other repositories. You could click the column headlines to change the sort oder.

Comment by Philipp Bracher [ 12/May/06 ]

the order of the nodes can be very important (menu for example). the node datas are already ordererd alphabetically.

The only solution would be to allow a flexible column based sorting in the tree, what is not planded to be done yet

Generated at Mon Feb 12 03:14:45 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.