-
Bug
-
Resolution: Fixed
-
Medium
-
8.19.1, 8.20.12, 9.4.4, 9.4.14
-
8.19
-
28
-
Severity 3 - Minor
-
8
-
Issue Summary
Unable to delete Project Role configuration after deleting or renaming a group in Crowd/LDAP.
Steps to Reproduce
- Configure User Directory with Crowd.
- Synchronise with Crowd, and create "groupfromcrowd" group from Crowd in Jira.
- Configure Project Role with "groupfromcrowd" group in Jira.
- Delete "groupfromcrowd" group in Crowd, or rename it.
- Synchronise with Crowd in Jira.
- Delete Project Role configuration with "groupfromcrowd" group in Jira.
- Reload browser, but Project Role configuration with "groupfromcrowd" group is still remained.
jira-delete-project_role-after-sync-and-crowd-group-deleted.mp4
Expected Results
You can delete Project Role configuration.
Actual Results
You can't delete Project role configuration.
Workaround
- Delete Project Role configuration before Deleting Group in Crowd and Synchronise.
- Add an internal group with the same name back, delete the project role and then delete the newly created group.
- is related to
-
JRASERVER-70937 REST API for Add actor users returns success (200) even if the user doesn't exist
-
- Closed
-
-
JRASERVER-73152 Jira does not remove the group which is deleted from Active Directory or MS Azure Directory under Project's Users&Roles
-
- Closed
-
-
JRASERVER-70842 Deleting a user from LDAP or Crowd server will not delete this user from the projectroleactor table
-
- Gathering Impact
-
- is resolved by
-
WILDT-105 Loading...