-
Bug
-
Resolution: Fixed
-
Low
-
9.4.8, 9.4.9
-
9.04
-
19
-
Severity 3 - Minor
-
50
-
-
Issue Summary
Whenever a user is deleted externally, Jira marks the user as inactive if this user has any data associated to it, that being Issues assigned/reported or comments.
However, if we transfer the issue assignments/reports to a different user and delete the comments, Jira is unable to remove the user and keeps the user as Inactive.
Steps to Reproduce
- Have an LDAP user deleted with content associated to the user;
- Synchronize the directory;
- The user will be set as inactive;
- Remove all issue assigns, reports or comments of this user;
- Synchronize the directory again;
- The user profile will remain in Jira's DB and UI showing as an inactive user;
- Delete another user from LDAP;
- BEFORE synchronizing the directory, remove all issue assigns, reports or comments;
- Synchronize the directory and the user will be removed as expected.
Expected Results
Inactive users should be removed if there is no comment, issue reported, or created associated to their profile.
Actual Results
The users are only removed if the data is transferred before the user is set to inactive.
Workaround
Before synchronizing the directory, make sure to transfer all data associated to the user profile so that Jira can remove the profile. For existing inactive users the accounts can be either deleted from the database directly, or after removing all the content associated to the profile, resetting the column deteled_externally to NULL and performing another synch will proceed to remove the inactive user.
Note about the workaround:
The described workarounds are only applicable if the object has been deleted from the external LDAP/moved to a location that's not accessible by Jira during the synchronization. If Jira is able to locate the object in the external LDAP, it won't be able to delete the account.
- mentioned in
-
Page Loading...
- relates to
-
JDCWUMAL-32 Loading...
-
WILDT-106 Loading...