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

    • Icon: Suggestion 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.

      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.

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

            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3054807 ] New: JAC Suggestion Workflow 3 [ 3684525 ]
            Status Original: RESOLVED [ 5 ] New: Closed [ 6 ]
            Owen made changes -
            Workflow Original: Confluence Workflow - Public Facing v4 [ 2606034 ] New: JAC Suggestion Workflow [ 3054807 ]
            Rachel Lin (Inactive) made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2557354 ] New: Confluence Workflow - Public Facing v4 [ 2606034 ]
            Status Original: Closed [ 6 ] New: Resolved [ 5 ]
            Ignat (Inactive) made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 - TEMP [ 2341854 ] New: JIRA PM Feature Request Workflow v2 - TEMP [ 2557354 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 [ 2110489 ] New: JIRA Bug Workflow w Kanban v6 - TEMP [ 2341854 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 - TEMP [ 2078905 ] New: JIRA Bug Workflow w Kanban v6 [ 2110489 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA Bug Workflow w Kanban v6 [ 883224 ] New: JIRA Bug Workflow w Kanban v6 - TEMP [ 2078905 ]
            jonah (Inactive) made changes -
            Description Original: 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.

            h3. Workaround

            Deactivate the user in the LDAP engine and JIRA rather then deleting them.             		New: {panel:bgColor=#e7f4fa}
              *NOTE:* This suggestion is for *JIRA Server*. Using *JIRA Cloud*? [See the corresponding suggestion|http://jira.atlassian.com/browse/JRACLOUD-35018].
              {panel}

            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.

            h3. Workaround

            Deactivate the user in the LDAP engine and JIRA rather then deleting them.
            jonah (Inactive) made changes -
            Link New: This issue relates to JRACLOUD-35018 [ JRACLOUD-35018 ]
            Oswaldo Hernandez (Inactive) made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 [ 705008 ] New: JIRA Bug Workflow w Kanban v6 [ 883224 ]

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

                Created:
                Updated:
                Resolved: