• 5
    • 47
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

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

      Atlassian Update – 4 January 2016

      Hi everyone,

      Thanks for voting and commenting on this issue. Your feedback is key to helping us understand how you use JIRA so we can continue improving your experience. We have reviewed this issue over the last few days; unfortunately we don't have any plans to support this in JIRA for the foreseeable future.

      Please remember that jira.atlassian.com is one of many inputs for the JIRA roadmap. You can learn more about our process here.

      I understand that our decision may be disappointing. Please don't hesitate to contact me if you have any questions.

      Regards,
      Dave Meyer
      dmeyer@atlassian.com
      Product Manager, JIRA Platform

      From the Administration User Browser screen, have an "Export List" button/link that exports all the users that match the current filter into a .CSV or Excel file. The columns exported would match the columns currently displayed: Username, Email, Full Name, Login Details, Groups. No formatting needed, just dump the text as displayed in each table cell into a single field (including carriage returns for multi line entries like Login Details).

      This would be much simpler than having to run queries to do this as described at http://confluence.atlassian.com/x/FYJyCw

      The end goal is a simple way to monitor who is logging in most often (need to contact the top 50 users), who has had many recent login failures, who belongs to one group but not another, etc.

            [JRACLOUD-23783] Easy User Export

            Atlassian Update - December 2022

            As per this comment I am closing this ticket.

            If you disagree with the closing of this ticket, please add a comment here saying why and we can reopen it.

            Anusha Rutnam added a comment - Atlassian Update - December 2022 As per this comment I am closing this ticket. If you disagree with the closing of this ticket, please add a comment here saying why and we can reopen it.

            This feature exists: Export users from a site

            I believe this ticket should be closed, but I will wait a week before taking any action in case anyone disagrees. Thank you!

            Anusha Rutnam added a comment - This feature exists: Export users from a site I believe this ticket should be closed, but I will wait a week before taking any action in case anyone disagrees. Thank you!

            This seems to have been implemented for some time - since about March 2018.

            Perry Tancredi added a comment - This seems to have been implemented for some time - since about March 2018.

            Bill Lortz added a comment -

            The use case I have is that we are also a Salesforce user. The plugin from ServiceRocket that coordinates between Jira and Salesforce doesn't have provisions to attach a Salesforce contact to the newly created Salesforce case based on the Jira reporter. So, I have to setup a mapping table on every request type to map between the Jira Requester Field and the Salesforce Contact ID.

            Doing it manually is tedious and very error prone once you have more than a dozen or so different reporters. I have written a salesforce report that extracts the contacts and contact IDs. I reverse engineered the JIRA backup file to extract the Jira users and their email addresses. I then match and combine the two lists. Finally I read in JSON mapping table and replace the section that maps reporters to contacts. I then re-import.

            I would rather not have to rely on running a system backup (which can only be done once a day) and extracting the users from it hoping the internal format doesn't change.

            If I could extract the jira users, it would be an easy change to the script and it would be more supportable.

            I do have a ticket open with ServiceRocket so I don't have to do this mess, but I can still see the need to be able to get the user table and audit it contents externally.

            Bill Lortz added a comment - The use case I have is that we are also a Salesforce user. The plugin from ServiceRocket that coordinates between Jira and Salesforce doesn't have provisions to attach a Salesforce contact to the newly created Salesforce case based on the Jira reporter. So, I have to setup a mapping table on every request type to map between the Jira Requester Field and the Salesforce Contact ID. Doing it manually is tedious and very error prone once you have more than a dozen or so different reporters. I have written a salesforce report that extracts the contacts and contact IDs. I reverse engineered the JIRA backup file to extract the Jira users and their email addresses. I then match and combine the two lists. Finally I read in JSON mapping table and replace the section that maps reporters to contacts. I then re-import. I would rather not have to rely on running a system backup (which can only be done once a day) and extracting the users from it hoping the internal format doesn't change. If I could extract the jira users, it would be an easy change to the script and it would be more supportable. I do have a ticket open with ServiceRocket so I don't have to do this mess, but I can still see the need to be able to get the user table and audit it contents externally.

            If you look at the history of comments the Better Excel plugin has already been bought up - the problem is those with cloud based instances have no options in this regard.

            Christian Wood added a comment - If you look at the history of comments the Better Excel plugin has already been bought up - the problem is those with cloud based instances have no options in this regard.

            Midori added a comment -

            Better Excel Plugin allows you to do this, for those columns you mention (Username, Email, Full Name, Login Details, Groups) and more (Directory, Detailed Project Roles!).

            That add-on is using customizable Excel templates to export information from JIRA to intelligent spreadsheets (with charts, pivot tables, Visual Basic macros, etc.). Although its primary use case is to export JIRA issues, nothing prevents you from exporting users.

            See the Exporting JIRA users to Excel article.
            (Automating these Excel reports for your monitoring use case is just the icing on the cake!)

            Midori added a comment - Better Excel Plugin allows you to do this, for those columns you mention (Username, Email, Full Name, Login Details, Groups) and more (Directory, Detailed Project Roles!). That add-on is using customizable Excel templates to export information from JIRA to intelligent spreadsheets (with charts , pivot tables , Visual Basic macros , etc.). Although its primary use case is to export JIRA issues, nothing prevents you from exporting users. See the Exporting JIRA users to Excel article. ( Automating these Excel reports for your monitoring use case is just the icing on the cake!)

            And this is why I couldn't recommend people start on Jira. An apparently simple request, backed by a number of users customers, and the reply from Atlassian is "give us a few years and then we might implement it or we might decide not to bother after all".
            In the meantime you're wasting spending time on 'features' that nobody asked for, like suddenly rendering simple issue links with icons and descriptions (JRA-60832).

            Ronald Vallenduuk added a comment - And this is why I couldn't recommend people start on Jira. An apparently simple request, backed by a number of users customers, and the reply from Atlassian is "give us a few years and then we might implement it or we might decide not to bother after all". In the meantime you're wasting spending time on 'features' that nobody asked for, like suddenly rendering simple issue links with icons and descriptions ( JRA-60832 ).

            Dave Meyer added a comment -

            Hi hosang.lim and renee.walsh267987192,

            Since users are not managed directly by JIRA in JIRA Cloud (user management is shared across your Cloud instance with Confluence and Bamboo), it's not possible to build a JIRA add-on for this functionality in JIRA Cloud.

            As we work through our plans for managing accounts and identity in Atlassian Cloud over the next couple years, this requirement is certainly on our radar.

            Regards,
            Dave Meyer
            Senior Product Manager, JIRA

            Dave Meyer added a comment - Hi hosang.lim and renee.walsh267987192 , Since users are not managed directly by JIRA in JIRA Cloud (user management is shared across your Cloud instance with Confluence and Bamboo), it's not possible to build a JIRA add-on for this functionality in JIRA Cloud. As we work through our plans for managing accounts and identity in Atlassian Cloud over the next couple years, this requirement is certainly on our radar. Regards, Dave Meyer Senior Product Manager, JIRA

            I second Hosang's comment. We are a Cloud users.. any plans to make this add-on available for the Cloud or any other way to export the user data?

            renee.walsh added a comment - I second Hosang's comment. We are a Cloud users.. any plans to make this add-on available for the Cloud or any other way to export the user data?

            Hosang Lim added a comment -

            I am a Cloud user. Is there an add-on for Cloud?

            Hosang Lim added a comment - I am a Cloud user. Is there an add-on for Cloud?

              Unassigned Unassigned
              2954a19bb3fc Tim Oey
              Votes:
              361 Vote for this issue
              Watchers:
              110 Start watching this issue

                Created:
                Updated:
                Resolved: