[MGNLUI-3577] Sortable property shouldn't sort by default Created: 11/Sep/15  Updated: 20/Feb/17  Resolved: 10/Feb/17

Status: Closed
Project: Magnolia UI
Component/s: security app, tree/list, workbench
Affects Version/s: 5.4.2
Fix Version/s: 5.4.12, 5.5.2

Type: Bug Priority: Major
Reporter: Mikaël Geljić Assignee: Robert Šiška
Resolution: Fixed Votes: 1
Labels: to-specify, ux
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
causality
caused by MGNLUI-3326 Support sorting by column in trees Closed
relation
is related to MGNLUI-4133 Warn user if using drag & drop in sor... 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:
Sprint: Kromeriz 83
Story Points: 5

 Description   

At the moment, when sortable is turned on for a tree view, then that view is unfortunately already sorted by default (when one just opens the app); it should be as per JCR natural order instead, until one presses the sorting arrows. This is a bug.

Security app is sorted by default, by design. Only this should be driven by the defaultOrder property on the content-connector definition.

Meanwhile, users can accidentally be reordered via DND but you don't see it because it's sorted!!
Actually, when sorted, we should disable the drag-n-drop functionality altogether as it doesn't make sense anymore.


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