[MAGNOLIA-2284] Editing group details reorders assigned parent groups Created: 24/Jul/08  Updated: 04/Nov/15  Resolved: 04/Nov/15

Status: Closed
Project: Magnolia
Component/s: None
Affects Version/s: 3.5.8
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Jan Haderka Assignee: Unassigned
Resolution: Won't Do 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)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:

 Description   

In documentation I can read that the order of roles and groups assigned to a user/group matters - http://documentation.magnolia.info/administration/security/configgroups.html
But if I do something like that:

  1. Create a new user/group
  2. Click edit the user/group button
  3. Add the user/group to "publishers" and "employees" groups (in this exact order).
  4. Save
  5. Click edit the user/group button
  6. I can see in a dialog that groups are sorted alphabetically, not in
  7. the order that I defined them what breaks the idea of compiling ACL.

Order is stored properly at creation time.
However editing any field (for example description) later and saving the dialog will cause order of groups to be changed in workspace.



 Comments   
Comment by Michael Mühlebach [ 04/Nov/15 ]

Given the thousands of other issues we have open that are more highly requested, we won't be able to address this issue in the foreseeable future. Instead we will focus on issues with a higher impact, and more votes.
Thanks for taking the time to raise this issue. As you are no doubt aware this issue has been on our backlog for some time now with very little movement.
I'm going to close this to set expectations so the issue doesn't stay open for years with few updates. If the issue is still relevant please feel free to reopen it or create a new issue.

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