Details

    • Feedback Policy:
      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 An updated workflow for server feature suggestions.
    • Current Status:
      Hide
      Atlassian Update – 30 March 2018

      Hi everyone,

      Thank you for your interest in this issue.

      While this suggestion has gathered significant interest, we're unable to implement all of the suggestions you make. We don't plan to work on this for the foreseeable future. This suggestion will be reviewed in about 12 months time, at which point we’ll consider whether we need to alter its status. 

      We understand this decision will be disappointing to everyone who voted for this issue. While we believe this suggestion would improve the product, after careful review of the most pressing needs of our customers, we've decided to prioritize other areas of the Jira Server roadmap, including:

      • Performance and stability improvements
      • Archiving projects for improved performance
      • Optimising the use of custom fields
      • Improving performance of boards
      • Improving Jira notifications
      • Allowing users to edit shared filters and dashboards
      • Mobile app for Jira Server

      We hope that you appreciate our candid and transparent communication. You can learn more about our approach to highly voted server suggestions here.

      To learn more on how your suggestions are reviewed, see our updated workflow for server feature suggestions.

      Kind regards,
      Jira Server Product Management

      Show
      Atlassian Update – 30 March 2018 Hi everyone, Thank you for your interest in this issue. While this suggestion has gathered significant interest, we're unable to implement all of the suggestions you make. We don't plan to work on this for the foreseeable future. This suggestion will be reviewed in about 12 months time, at which point we’ll consider whether we need to alter its status.  We understand this decision will be disappointing to everyone who voted for this issue. While we believe this suggestion would improve the product, after careful review of the most pressing needs of our customers, we've decided to prioritize other areas of the Jira Server roadmap, including: Performance and stability improvements Archiving projects for improved performance Optimising the use of custom fields Improving performance of boards Improving Jira notifications Allowing users to edit shared filters and dashboards Mobile app for Jira Server We hope that you appreciate our candid and transparent communication. You can learn more about our approach to highly voted server suggestions here . To learn more on how your suggestions are reviewed, see our updated workflow for server feature suggestions . Kind regards, Jira Server Product Management
    • UIS:
      144

      Description

      NOTE: This suggestion is for JIRA Server. Using JIRA Cloud? See the corresponding suggestion.

      Original request description:

      There are a number of situations where you want to delete a user - but transfer all of their reported/assigned issues to someone else.

      We have a large number of duplicate users - and we also have had some people leave - and we want to delete them.

      "Merge Users" is the best description I can think of.

        Attachments

        1. failed-workaround.png
          failed-workaround.png
          30 kB
        2. image-2018-03-16-17-44-37-022.png
          image-2018-03-16-17-44-37-022.png
          23 kB
        3. script runner version 2.1.15.png
          script runner version 2.1.15.png
          21 kB
        4. wristwatch.jpeg
          wristwatch.jpeg
          6 kB

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                nickminutello Nick Minutello
              • Votes:
                425 Vote for this issue
                Watchers:
                220 Start watching this issue

                Dates

                • Created:
                  Updated: