NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? See the corresponding suggestion.
This issue supercedes CWD-2515. I have had a chat with Olli Nevalainen and we agreed that this is a good improvement request for the behavior of JIRA when a user is deleted from the AD side or from Crowd.
Currently, the user would disappear from the JIRA user browser and will show up in gray color in the issues when he is the assignee of reporter. However, this may cause problems later on. I have witnessed one problem of it when retrieving SOAP remote issues which their assignee/reporter does not exist in JIRA due to him/her being deleted from LDAP/Crowd side. There may be more hidden problems about it.
Deleting a user who matches any of this criteria was never possible from the UI:
- Assignee of any issue
- Reporter of any issue
- Lead of any project
Thus, I have raised this improvement request to keep the user in JIRA even after being deleted from the external user management system, but as an inactive user (he/she will not be able to log-in anyway).
Regards,
Ali
- is blocked by
-
JRACLOUD-2220 Deactivate user
- Closed
- is duplicated by
-
JRACLOUD-29202 JIRA Should Handle Deleted LDAP User(s) Better
- Closed
-
JRACLOUD-35018 Ability to detect a deleted user in LDAP and disable that user
- Closed
- is related 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
- supersedes
-
CWD-2515 CROWD and LDAP should respect the application rules
- Closed
- was cloned as
-
CWD-2855 During synchronise of a remote user directory, allow the Host application to decide whether to delete or deactivate missing users.
- Closed