Uploaded image for project: 'Jira Platform Cloud'
  1. Jira Platform Cloud
  2. JRACLOUD-35018

Ability to detect a deleted user in LDAP and disable that user

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Duplicate
    • None
    • None

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      NOTE: This suggestion is for JIRA Cloud. Using JIRA Server? 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.

            [JRACLOUD-35018] Ability to detect a deleted user in LDAP and disable that user

            Mark Lassau (Inactive) added a comment -

            dcurrie@atlassian.com
            JIRA will only keep the user account around if it detects that it is required for displaying historical data.
            So, if that user is the reporter, assignee, or a comment author on any issue, we keep the user and set to disable, otherwise we delete the account.

            Also, the deleting [ 1 ] users log is probably misleading: it will list how many useres it attempts to delete but some subset of these may get "vetoed" and be disabled instead.

            Mark Lassau (Inactive) added a comment - dcurrie@atlassian.com JIRA will only keep the user account around if it detects that it is required for displaying historical data. So, if that user is the reporter, assignee, or a comment author on any issue, we keep the user and set to disable, otherwise we delete the account. Also, the deleting [ 1 ] users log is probably misleading: it will list how many useres it attempts to delete but some subset of these may get "vetoed" and be disabled instead.

              Unassigned Unassigned
              dcurrie@atlassian.com Dave C
              Votes:
              1 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: