[MAGNOLIA-3602] Deleting a role that is reffered by a group Created: 06/Apr/11  Updated: 19/May/11  Resolved: 19/May/11

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

Type: Bug Priority: Neutral
Reporter: Zdenek Skodik Assignee: Ondrej Chytil
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File roles.png    
Issue Links:
dependency
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   

can end up in a situation that other role/s, assigned to the group, is/are suddenly showed up as uuids, not as names.

To reproduce:

  1. create a test role
  2. create a test group, assign roles in this order: test, demo-project-base, contact-base, workflow-base, demo-project-publisher. Save.
  3. delete the test role, edit the test group and you should see something similar to attached roles.png

    The same behavior affects also the rest of possible assignments - Groups for Group and Groups for User.


 Comments   
Comment by Jan Haderka [ 17/May/11 ]

Would not rewriting the loops using while and iterator work better then manually taking care of indexes are remove()? If nothing else it would make code easier to read.

Comment by Ondrej Chytil [ 19/May/11 ]

Result of this fix is that in case of non-existing group/role that one is removed from definition of user/group instead of throwing uuid which does not exist anymore.

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