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

Jira will not remove users deleted externally after they are marked as inactive

XMLWordPrintable

    • 9.04
    • 19
    • Severity 3 - Minor
    • 50
    • Hide
      Atlassian Update – 27 March 2025

      Dear Customers,

      Thank you for your patience as we've worked on a fix for this bug. We have the fix ready for release, however fix moved from originally planned version 10.5.0 to 10.6.0. Thank you again for your patience, and sorry for inconvenience.

      Best regards

      Dominik Wojtasik
      Senior Software Engineer, Jira Platform

      Atlassian Update – 17 February 2025

      Dear Customers,

      We're happy to announce that in next release 10.5.0 possibility to remove externally deleted users will be added in user management in Jira.
      This manual action is required as externally deleted user is no longer included in subsequent Jira's synchronization.
      Please consult the Create, edit, or remove a user documentation for further instructions.

      Specific scenarios when user is marked as inactive during directory synchronization is described in LDAP user deletion effect in Jira user base.

      Best regards

      Dominik Wojtasik
      Senior Software Engineer, Jira Platform

      Show
      Atlassian Update – 27 March 2025 Dear Customers, Thank you for your patience as we've worked on a fix for this bug. We have the fix ready for release, however fix moved from originally planned version 10.5.0 to 10.6.0. Thank you again for your patience, and sorry for inconvenience. Best regards Dominik Wojtasik Senior Software Engineer, Jira Platform Atlassian Update – 17 February 2025 Dear Customers, We're happy to announce that in next release 10.5.0 possibility to remove externally deleted users will be added in user management in Jira. This manual action is required as externally deleted user is no longer included in subsequent Jira's synchronization. Please consult the Create, edit, or remove a user documentation for further instructions. Specific scenarios when user is marked as inactive during directory synchronization is described in LDAP user deletion effect in Jira user base . Best regards Dominik Wojtasik Senior Software Engineer, Jira Platform

      Issue Summary

      Whenever a user is deleted externally, Jira marks the user as inactive if this user has any data associated to it, that being Issues assigned/reported or comments.

      However, if we transfer the issue assignments/reports to a different user and delete the comments, Jira is unable to remove the user and keeps the user as Inactive.

      Steps to Reproduce

      1. Have an LDAP user deleted with content associated to the user;
      2. Synchronize the directory;
      3. The user will be set as inactive;
      4. Remove all issue assigns, reports or comments of this user;
      5. Synchronize the directory again;
      6. The user profile will remain in Jira's DB and UI showing as an inactive user;
      7. Delete another user from LDAP;
      8. BEFORE synchronizing the directory, remove all issue assigns, reports or comments;
      9. Synchronize the directory and the user will be removed as expected.

      Expected Results

      Inactive users should be removed if there is no comment, issue reported, or created associated to their profile.

      Actual Results

      The users are only removed if the data is transferred before the user is set to inactive.

      Workaround

      Before synchronizing the directory, make sure to transfer all data associated to the user profile so that Jira can remove the profile. For existing inactive users the accounts can be either deleted from the database directly, or after removing all the content associated to the profile, resetting the column deteled_externally to NULL and performing another synch will proceed to remove the inactive user.

      Note about the workaround:

      The described workarounds are only applicable if the object has been deleted from the external LDAP/moved to a location that's not accessible by Jira during the synchronization. If Jira is able to locate the object in the external LDAP, it won't be able to delete the account.

              21d451cf00e1 Dominik Wojtasik
              psouza Pedro Souza
              Votes:
              4 Vote for this issue
              Watchers:
              14 Start watching this issue

                Created:
                Updated:
                Resolved: