Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-35018

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

    XMLWordPrintable

Details

    • Suggestion
    • Resolution: Duplicate
    • None
    • None
    • None
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

    Description

      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.

      Attachments

        Issue Links

          causes

          Bug - A problem which impairs or prevents the functions of the product. JRASERVER-24344 Deleted user in Crowd creates trouble in Jira when the user have tasks assigned

          • High - High priority issues
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. JRASERVER-24051 Deleting a user does not remove the user from its LDAP group

          • Medium - Medium priority issues
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. JRACLOUD-66222 Users deleted from LDAP are not logged out

          • Low - Low priority issues
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. JRASERVER-10391 Exceptions in logs when custom field default user is deleted

          • Low - Low priority issues
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. JRASERVER-28970 Deleting a user removes all Project Roles from projectroleactor even if the exist within another User Directory

          • Low - Low priority issues
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. JRASERVER-31613 Hovering over deleted user's name must indicate that user does not exist

          • Low - Low priority issues
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. JRASERVER-34246 Deleted LDAP user's assigned issues cannot be searched in Issue Navigator even though it shows in Project Overview

          • Low - Low priority issues
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. JRASERVER-34563 Deleted LDAP User cannot be removed from Project Role

          • Low - Low priority issues
          • Closed

          Suggestion - JRASERVER-34574 Deleted LDAP users should continue to display "full name" in issues/gadgets

          • Closed
          duplicates

          Suggestion - 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

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

          • Closed

          Suggestion - JRASERVER-24937 When a user is deleted in AD or Crowd, JIRA could keep the user in JIRA as an inactive user

          • Closed

          Activity

            People

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

              Dates

                Created:
                Updated:
                Resolved: