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

Alternate to "delete user" -- leave user in Jira but actually disable

XMLWordPrintable

    • 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.

      People leave. They get fired. They die.

      But through all that they are still in Jira. We change their password to a random one, and edit the email address. But this still clutters up our lists of assignable users, and occasionally results in a dearly departed getting assigned an issue. Jira prevents us from deleting them:

      This user cannot be deleted at this time because there are issues assigned to them, they have reported issues, or they are currently the lead of a project.
      Please note that any components with this user set as the lead will have the component lead set to empty when the user is deleted.

      I am aware that we can bulk assign the reporter to someone else... but then we loose valuable at a glance history. What we'd like is to really disable the users, without deleting them.

      There are many dupes of this report, most closed as "won't fix".

            [JRASERVER-17223] Alternate to "delete user" -- leave user in Jira but actually disable

            jurfalino added a comment -

            JRA-2220 is NOT a duplicate of this issue. It is not the same to 'disable' a user, leaving all issues assigned to him, than to delete a user reassigning all issues to anyone else. The first option allows you to keep history that won´t change anyway but is valuable as it is.

            Suppose you want to delete a user who left the company, then you will never again be able to know which were the issues created or resolved by that person, you loose all history. On the other side, if you leave the user in the system it´s also a mess because you don´t want to see him as assignable in any issue.

            jurfalino added a comment - JRA-2220 is NOT a duplicate of this issue. It is not the same to 'disable' a user, leaving all issues assigned to him, than to delete a user reassigning all issues to anyone else. The first option allows you to keep history that won´t change anyway but is valuable as it is. Suppose you want to delete a user who left the company, then you will never again be able to know which were the issues created or resolved by that person, you loose all history. On the other side, if you leave the user in the system it´s also a mess because you don´t want to see him as assignable in any issue.

            Brian Lane added a comment -

            Bryce,

            I will resolve this as a duplicate to JRA-2220.

            Brian Lane added a comment - Bryce, I will resolve this as a duplicate to JRA-2220 .

              Unassigned Unassigned
              brycenesbitt Bryce Jira Nesbitt
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: