[MGNLUI-3139] Renaming roles in Security App doesn't work properly Created: 08/Sep/14  Updated: 05/Dec/14  Resolved: 15/Sep/14

Status: Closed
Project: Magnolia UI
Component/s: security app
Affects Version/s: 5.3.2
Fix Version/s: 5.3.4

Type: Bug Priority: Critical
Reporter: Lars Fischer Assignee: Aleksandr Pchelintcev
Resolution: Fixed Votes: 0
Labels: support, uzh
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File Screen Shot 2014-09-08 at 15.50.01.png    
Issue Links:
causality
is causing MGNLUI-3225 Security App: 'superuser' role can no... Closed
duplicate
duplicates MGNLUI-3026 Role permissions not updated on rename 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

 Description   

Renaming a role does not correctly rename ACL settings for "Userroles".

  • When just renaming a role the old name stays in the "Userroles" ACL and the new name is added to the "Userroles" ACL.
  • When duplicating and then renaming a role, the old name stays in the "Userroles" ACL.
  • The same happens when only duplicating a role.

It seems like renaming roles is basically broken.


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