-
Suggestion
-
Resolution: Duplicate
-
None
-
None
-
None
NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.
If a user is deleted from LDAP, if using a connector user directory on the next sync it will delete that user from JIRA. It doesn't appear this follows some of the inbuilt restrictions around deleting users in the GUI - for example you can delete a user from LDAP and it will remove them even if they're assigned issues. This can leave all sorts of orphaned information and cause problems.
Given we now have deactivate user functionality in JIRA, rather than deleting the user in JIRA can we deactivate the user? This would prevent us from getting into situations where deleting a user has caused problems in JIRA.
Workaround
Deactivate the user in the LDAP engine and JIRA rather then deleting them.
- causes
-
JRASERVER-24344 Deleted user in Crowd creates trouble in Jira when the user have tasks assigned
- Closed
-
JRASERVER-24051 Deleting a user does not remove the user from its LDAP group
- Closed
-
JRACLOUD-66222 Users deleted from LDAP are not logged out
- Closed
-
JRASERVER-10391 Exceptions in logs when custom field default user is deleted
- Closed
-
JRASERVER-28970 Deleting a user removes all Project Roles from projectroleactor even if the exist within another User Directory
- Closed
-
JRASERVER-31613 Hovering over deleted user's name must indicate that user does not exist
- Closed
-
JRASERVER-34246 Deleted LDAP user's assigned issues cannot be searched in Issue Navigator even though it shows in Project Overview
- Closed
-
JRASERVER-34563 Deleted LDAP User cannot be removed from Project Role
- Closed
-
JRASERVER-34574 Deleted LDAP users should continue to display "full name" in issues/gadgets
- Closed
- duplicates
-
JRASERVER-24937 When a user is deleted in AD or Crowd, JIRA could keep the user in JIRA as an inactive user
- Closed
- relates to
-
JRACLOUD-35018 Ability to detect a deleted user in LDAP and disable that user
- Closed
-
JRASERVER-24937 When a user is deleted in AD or Crowd, JIRA could keep the user in JIRA as an inactive user
- Closed