• 48
    • 53
    • Hide
      Atlassian Update – 6 March 2018

      Hi everyone,

      Thanks for your interest in this issue.
      This request is considered a potential addition to our longer-term roadmap.

      We'll typically review this request in about 12 months time, at which point we’ll consider whether we need to alter its status.

      For the nearest future 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

      There are commercial third party apps available, that may be useful in your context:

      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 – 6 March 2018 Hi everyone, Thanks for your interest in this issue. This request is considered a potential addition to our longer-term roadmap. We'll typically review this request in about 12 months time, at which point we’ll consider whether we need to alter its status. For the nearest future 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 There are commercial third party apps available, that may be useful in your context: Better Excel Plugin for Jira Active User Filter Admin Tools for Jira JExcel LITE - The Power of Excel in Jira 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
    • 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.

      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.

            [JRASERVER-23783] Easy User Export

            @ 4b15e6bf8ea7 

            Unfortunately, the plugin has disappeared from the marketplace

            Hannes Medwed added a comment - @ 4b15e6bf8ea7   Unfortunately, the plugin has disappeared from the marketplace

            It the same for us,  Jira User Export plugin is not available anymore and we need the possibility to export user accounts. It is very important for us.

            Karin Hiepe added a comment - It the same for us,  Jira User Export plugin is not available anymore and we need the possibility to export user accounts. It is very important for us.

            Romain T. added a comment -

            Same here : Jira User Export plugin is not available anymore => we need a replacement in Jira Datacenter.

             

            Romain T. added a comment - Same here : Jira User Export plugin is not available anymore => we need a replacement in Jira Datacenter.  

            Muddassir Quazi added a comment - - edited

            Hi,

            Jira User Export plugin is not available on Atlassian Marketplace anymore. This app has been archived. Now this becomes a need for us in Jira.

            Muddassir Quazi added a comment - - edited Hi, Jira User Export plugin is not available on Atlassian Marketplace anymore. This app has been archived. Now this becomes a need for us in Jira.

            Tien Tran added a comment -

            Hi all,

            I exported the list of user from User Management > Users as bellow but there're many users missing. They have created Jira tickets with us but they aren't in the exported csv. I am trying the app https://marketplace.atlassian.com/apps/1220535/jira-user-export?hosting=server&tab=overview but don't know how to import the Jira file to my Jira. I logged into my Jira as admin, I also cannot find the app in Marketplace apps > Find new apps. Please advice.

            Tien Tran added a comment - Hi all, I exported the list of user from User Management > Users as bellow but there're many users missing. They have created Jira tickets with us but they aren't in the exported csv. I am trying the app  https://marketplace.atlassian.com/apps/1220535/jira-user-export?hosting=server&tab=overview  but don't know how to import the Jira file to my Jira. I logged into my Jira as admin, I also cannot find the app in Marketplace apps > Find new apps. Please advice.

            RJ added a comment -

            Hello.

            Agree, this is just a basic functionality that should be included. In my case, I need to run a report on the inactive users. Running and exporting this should be very simple. Love the software but the inability to complete a simple task like this efficiently is frustrating. 

            RJ added a comment - Hello. Agree, this is just a basic functionality that should be included. In my case, I need to run a report on the inactive users. Running and exporting this should be very simple. Love the software but the inability to complete a simple task like this efficiently is frustrating. 

            Great that there is an app. This seems like some basic functionality that could be built in. I don't need more apps to test during upgrades.

            Kevin Mowrey added a comment - Great that there is an app. This seems like some basic functionality that could be built in. I don't need more apps to test during upgrades.

            Hi all,

            You can use the Jira User Export as Michael Fechter mentioned. It is free to use.

            You can get it via UPM or download it here: https://marketplace.atlassian.com/apps/1220535/jira-user-export?hosting=server&tab=overview

            I am the creator of this app so please let me know if you have any issues or questions regarding this app.

            Regards

            Lasse Langhorn

            Lasse Langhorn added a comment - Hi all, You can use the Jira User Export as Michael Fechter mentioned. It is free to use. You can get it via UPM or download it here:  https://marketplace.atlassian.com/apps/1220535/jira-user-export?hosting=server&tab=overview I am the creator of this app so please let me know if you have any issues or questions regarding this app. Regards Lasse Langhorn

            Michael Fechter added a comment - - edited

            Also facing this issue. Has anyone tried the following free supported add-on for server? Just after some feed-back of whether they had any issues? 

            https://marketplace.atlassian.com/apps/1220535/jira-user-export?hosting=server&tab=overview

            Michael Fechter added a comment - - edited Also facing this issue. Has anyone tried the following free supported add-on for server? Just after some feed-back of whether they had any issues?  https://marketplace.atlassian.com/apps/1220535/jira-user-export?hosting=server&tab=overview

            Since we are paying according to the user limit, the tool should provide an efficient way to see the information without jumping through hoops

            Michelle Clements added a comment - Since we are paying according to the user limit, the tool should provide an efficient way to see the information without jumping through hoops

            It really seems as if Atlassian does not WANT to implement this rather basic feature which we can see in every other tool.

            So far Jira is a one of the best tools for project management, but sadly user management seems rudimental. One of the most simplest use cases would be to filter a user group from the Jira user table, which then is shown in HTML. Why not use this same information to just export it? Of course it won't be as trivial as stated here, but on the other hand this shouldn't be rocket science, either.

            To get the info I need from my user data base I will now extract a few tables from SQL, then import it to Microsoft Access, make a small relational data base out of it and then make the extraction out of Access; the only good thing about that is that I can use this Access construct for future imports. Sadly I will always lose time over exporting users and their relative data when using Jira where other products normally offer a simple export function.

            So yes, please just consider this rather simple option for Jira administrators all around the world.

            Please do not repeat on March 6th, 2020, that you are still looking into stability and performance features and the like and having other things on your next 12 month roadmap while raising your prices astronomically. Thank you!

            brandung_admin added a comment - It really seems as if Atlassian does not WANT to implement this rather basic feature which we can see in every other tool. So far Jira is a one of the best tools for project management, but sadly user management seems rudimental. One of the most simplest use cases would be to filter a user group from the Jira user table, which then is shown in HTML. Why not use this same information to just export it? Of course it won't be as trivial as stated here, but on the other hand this shouldn't be rocket science, either. To get the info I need from my user data base I will now extract a few tables from SQL, then import it to Microsoft Access, make a small relational data base out of it and then make the extraction out of Access; the only good thing about that is that I can use this Access construct for future imports. Sadly I will always lose time over exporting users and their relative data when using Jira where other products normally offer a simple export function. So yes, please just consider this rather simple option for Jira administrators all around the world. Please do not repeat on March 6th, 2020, that you are still looking into stability and performance features and the like and having other things on your next 12 month roadmap while raising your prices astronomically. Thank you!

            Agreed

            Brett Farrell added a comment - Agreed

            all, this should be a Basic funktionality for a tool. It should not be so difficult as in confluence is realized. I vote for it!

            Sabine Bamboschek-Keller added a comment - all, this should be a Basic funktionality for a tool. It should not be so difficult as in confluence is realized. I vote for it!

            Artem Grotskyi added a comment - - edited

            Can't believe that it's not implemented yet.
            I can create it for you guys. It's just a 4-6 hours work to create new webwork action to export data to a file.

            Artem Grotskyi added a comment - - edited Can't believe that it's not implemented yet. I can create it for you guys. It's just a 4-6 hours work to create new webwork action to export data to a file.

            Dear,
            You are seeing that each new update of Jira we lose functionality, because pluggins or functions that previously worked without the need for extra licenses now have to be paid separately.
            While JIRA has been the basis of many of our projects, now with all these changes ServiceNow is passing the rag.
            They are adding new features without having to pay extra costs and each update version is more important.
            Thing that JIRA walks back, each new update we lose in functionality, now we are with the JIRA SERVER version (v7.1.0 # 71003-sha1: 2f3ef40) and we try to migrate to the latest version in the testing environment and we lost compatibility functionality and Plug-in-based workflows stopped working.

            So good, that's the feeling of the side of the customer experience, we worked with Jira since 2009 and since version 6.13.

            Each year it is more difficult to justify spending and above with less functionality.

            Thank you and I hope this comment will be useful.

            Greetings.
            Diego Cañete.

            Diego Cañete added a comment - Dear, You are seeing that each new update of Jira we lose functionality, because pluggins or functions that previously worked without the need for extra licenses now have to be paid separately. While JIRA has been the basis of many of our projects, now with all these changes ServiceNow is passing the rag. They are adding new features without having to pay extra costs and each update version is more important. Thing that JIRA walks back, each new update we lose in functionality, now we are with the JIRA SERVER version (v7.1.0 # 71003-sha1: 2f3ef40) and we try to migrate to the latest version in the testing environment and we lost compatibility functionality and Plug-in-based workflows stopped working. So good, that's the feeling of the side of the customer experience, we worked with Jira since 2009 and since version 6.13. Each year it is more difficult to justify spending and above with less functionality. Thank you and I hope this comment will be useful. Greetings. Diego Cañete.

            Gary Bates added a comment -

            Created in 2011... simple functionality still not deployed in 2018... really!??

            Gary Bates added a comment - Created in 2011... simple functionality still not deployed in 2018... really!??

            Can you guys include it in Jira/Confluence Server Edition?

            Bryan Bojorque added a comment - Can you guys include it in Jira/Confluence Server Edition?

            Perry Tancredi added a comment - - edited

            Edit - this comment is for Cloud, not Server, so not relevant here

            --------

            Am I missing something? It looks like this feature has already been deployed. I noticed it a few weeks ago.

            Perry Tancredi added a comment - - edited Edit - this comment is for Cloud, not Server, so not relevant here -------- Am I missing something? It looks like this feature has already been deployed. I noticed it a few weeks ago.

            eric wood added a comment -

            I installed Better Excel Plugin for Jira and it crashed my production system. Why not provide the capability as a native functionality

            eric wood added a comment - I installed Better Excel Plugin for Jira and it crashed my production system. Why not provide the capability as a native functionality

            Hi everyone,

            Thanks for your interest in this issue.
            This request is considered a potential addition to our longer-term roadmap.

            We'll typically review this request in about 12 months time, at which point we’ll consider whether we need to alter its status.

            For the nearest future 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

            There are commercial third party apps available, that may be useful in your context:

            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

            Kasia Derenda added a comment - Hi everyone, Thanks for your interest in this issue. This request is considered a potential addition to our longer-term roadmap. We'll typically review this request in about 12 months time, at which point we’ll consider whether we need to alter its status. For the nearest future 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 There are commercial third party apps available, that may be useful in your context: Better Excel Plugin for Jira Active User Filter Admin Tools for Jira JExcel LITE - The Power of Excel in Jira 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

            Any news on this for on-prem clients? Our clients are getting frustrated by not having this option.

            Arsham Mazaheri added a comment - Any news on this for on-prem clients? Our clients are getting frustrated by not having this option.

            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?

            We added this functionality to the Active User Filter add-on (https://marketplace.atlassian.com/plugins/cr.tin.ActiveUserFilter.active-user-filter/server/overview). You can now 1 click export from the user management page in the admin interface.

            Boris Berenberg - Atlas Authority added a comment - We added this functionality to the Active User Filter add-on ( https://marketplace.atlassian.com/plugins/cr.tin.ActiveUserFilter.active-user-filter/server/overview ). You can now 1 click export from the user management page in the admin interface.

            Ping for this...

            Gordon Andersen added a comment - Ping for this...

            Thanks for the response, Dave. I was mostly just curious about the rationale to leave it open, though I would use the feature if it were included in the product.

            Thanks for participating in the discussion even when you don't always have good news.

            Regards,
            Perry

            Perry Tancredi added a comment - Thanks for the response, Dave. I was mostly just curious about the rationale to leave it open, though I would use the feature if it were included in the product. Thanks for participating in the discussion even when you don't always have good news. Regards, Perry

            Hi tancredip346475353,

            I understand your frustration that we haven't been able to address this feature request yet. As a policy, we leave feature requests open unless they explicitly contradict our product strategy and we have a coherent rationale that we can express publicly for closing the request.

            Regards,
            Dave Meyer
            Senior Product Manager, JIRA

            Dave Meyer added a comment - Hi tancredip346475353 , I understand your frustration that we haven't been able to address this feature request yet. As a policy, we leave feature requests open unless they explicitly contradict our product strategy and we have a coherent rationale that we can express publicly for closing the request. Regards, Dave Meyer Senior Product Manager, JIRA

            @dmeyer, If you're not going to do do this, why leave the issue open?

            Perry Tancredi added a comment - @dmeyer, If you're not going to do do this, why leave the issue open?

            Dalectric added a comment -

            There's also JIRA Group Browser plugin, but again only available for Server installation.
            It does allow browsing of group members within JIRA

            Dalectric added a comment - There's also JIRA Group Browser plugin , but again only available for Server installation. It does allow browsing of group members within JIRA

            That't too bad. This would be really helpful in auditing users accounts quickly.

            Vinny Petrillo added a comment - That't too bad. This would be really helpful in auditing users accounts quickly.

            This is only for JIRA server not for the Cloud version.

            Madhavi Annapureddy added a comment - This is only for JIRA server not for the Cloud version.

            Mark Biro added a comment - - edited

            Hi there!

            With add-on JExcel, you can export your issues to CSV or Excel!

            It gives you an Excel-like interface and totally works like the issue navigator but you can inline edit everything!
            And its completely free!

            Download it from the marketplace:
            https://marketplace.atlassian.com/plugins/com.moresimp.jexcel/server/overview

            Hope it helps you.

            Cheers, Mark

            Mark Biro added a comment - - edited Hi there! With add-on JExcel , you can export your issues to CSV or Excel! It gives you an Excel-like interface and totally works like the issue navigator but you can inline edit everything ! And its completely free ! Download it from the marketplace: https://marketplace.atlassian.com/plugins/com.moresimp.jexcel/server/overview Hope it helps you. Cheers, Mark

            I wish I could say this was unexpected. I'm really beginning to wonder how much requests and feedback from users actually means to the Jira development team. I've seen too many requests and suggestions with many votes being closed with comments like these.

            Ronald Vallenduuk added a comment - I wish I could say this was unexpected. I'm really beginning to wonder how much requests and feedback from users actually means to the Jira development team. I've seen too many requests and suggestions with many votes being closed with comments like these.

            Dave Meyer added a comment -

            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

            Dave Meyer added a comment - 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

            Lacey Also added a comment -

            Ping for this...

            Lacey Also added a comment - Ping for this...

            Thanks for the update Dave.
            It took you guys 8 years to decide not to fix JRA-2364 and only 4 years to kill this request. I suppose that's an improvement....

            Ronald Vallenduuk added a comment - Thanks for the update Dave. It took you guys 8 years to decide not to fix JRA-2364 and only 4 years to kill this request. I suppose that's an improvement....

            Dalectric added a comment -

            I created an Excel macro that using cURL to get the data from JIRA and then the macro pulls this into a sheet.
            This is the form of the cURL command I use (vDQ = Chr(34))
            sCommand = "curl k -D -u " & vDQ & sUsername & ":" & sPassword & vDQ
            sCommand = sCommand & " " & vDQ & "https://" & sJIRAURL & "/rest/api/2/user/assignable/search?project=" & sPrjKey & "&maxResults=1000" & vDQ
            sCommand = sCommand & " > " & vDQ & sJIRAUsersJSONInputFilename & vDQ

            It's then a case of process the JSON output to get the info you want and copying it an Excel sheet in the workbook.

            Dalectric added a comment - I created an Excel macro that using cURL to get the data from JIRA and then the macro pulls this into a sheet. This is the form of the cURL command I use (vDQ = Chr(34)) sCommand = "curl k -D -u " & vDQ & sUsername & ":" & sPassword & vDQ sCommand = sCommand & " " & vDQ & "https://" & sJIRAURL & "/rest/api/2/user/assignable/search?project=" & sPrjKey & "&maxResults=1000" & vDQ sCommand = sCommand & " > " & vDQ & sJIRAUsersJSONInputFilename & vDQ It's then a case of process the JSON output to get the info you want and copying it an Excel sheet in the workbook.

            Rob Horan added a comment -

            CLI requires purchase - not an option.

            Rob Horan added a comment - CLI requires purchase - not an option.

            djjay0131 added a comment -

            djjay0131 added a comment - What about using the CLI? https://bobswift.atlassian.net/wiki/display/JCLI/Documentation

            Rob Horan added a comment -

            Silly is a nice way of putting it. This has been a real headache for me. Every time I have to try to get a list together there are a lot of steps that need to be taken.

            Rob Horan added a comment - Silly is a nice way of putting it. This has been a real headache for me. Every time I have to try to get a list together there are a lot of steps that need to be taken.

            I too am wanting some sort of functionality like this...

            You can export issues to excel but not the user list? seems pretty silly!

            thomas_webb added a comment - I too am wanting some sort of functionality like this... You can export issues to excel but not the user list? seems pretty silly!

            BernardH added a comment -

            Seems like this would be basic functionality to me. You can't even sort by any of the columns. I would love to just be able to see out of the 20 or so pages of users how many have never logged in so I can remove the account, or number of days since last activity. Something to be able to manage the user count.

            BernardH added a comment - Seems like this would be basic functionality to me. You can't even sort by any of the columns. I would love to just be able to see out of the 20 or so pages of users how many have never logged in so I can remove the account, or number of days since last activity. Something to be able to manage the user count.

            Midori added a comment -

            Better Excel Plugin solves this use case as pretty much any "export this and that from JIRA to a spreadsheet", due its flexibility.

            You should develop a Groovy script and execute it as part of your Excel export. The script should get the UserManager instance from JIRA's ComponentManager (or ComponentAccessor), then call this method, and return the result to the template Excel sheet:

            Set<User> getAllUsers();
            

            In the sheet, you can iterate the set using the forEach tag, and export any user property with easy to comprehend expressions.

            (I am happy to help with the script, if there is any interest. Just email me at ferenc.kiss@midori-global.com.)

            Midori added a comment - Better Excel Plugin solves this use case as pretty much any "export this and that from JIRA to a spreadsheet", due its flexibility. You should develop a Groovy script and execute it as part of your Excel export. The script should get the UserManager instance from JIRA's ComponentManager (or ComponentAccessor), then call this method, and return the result to the template Excel sheet: Set<User> getAllUsers(); In the sheet, you can iterate the set using the forEach tag , and export any user property with easy to comprehend expressions. (I am happy to help with the script, if there is any interest. Just email me at ferenc.kiss@midori-global.com.)

            Rob Horan added a comment -

            Thanks Piotr, but I can't justify a purchase order or the expense just for this.

            Rob Horan added a comment - Thanks Piotr, but I can't justify a purchase order or the expense just for this.

            there is a plugin which covers part of mentioned functionality - https://marketplace.atlassian.com/plugins/pl.com.tt.admintoolsforjira.AdminToolsForJira
            One of the plugin features is "Export informations about the users to Excel"

            Piotr Tokarski added a comment - there is a plugin which covers part of mentioned functionality - https://marketplace.atlassian.com/plugins/pl.com.tt.admintoolsforjira.AdminToolsForJira One of the plugin features is "Export informations about the users to Excel"

            I shouldn't have to be a developer to be able to export this list. "Use the REST API" is not a valid answer. Now if you created a plug-in or something that used the REST API to deliver this feature in JIRA and made it available to the community, then that would definitely be acceptable to me.

            Stephen Mason added a comment - I shouldn't have to be a developer to be able to export this list. "Use the REST API" is not a valid answer. Now if you created a plug-in or something that used the REST API to deliver this feature in JIRA and made it available to the community, then that would definitely be acceptable to me.

            It is fundamental to running a large complex system across a number of employed and contracted users to be able to audit who has access to what. The more difficult to make this, the more errors we will make in keeping our system secure and our access up to date.

            Not having this capability leads to security issues and the failure of system integrity.

            David Macfarlane added a comment - It is fundamental to running a large complex system across a number of employed and contracted users to be able to audit who has access to what. The more difficult to make this, the more errors we will make in keeping our system secure and our access up to date. Not having this capability leads to security issues and the failure of system integrity.

            When the Jira service has a problem the admnistrator needs to email users about the issue and its progress. You can't do this from Jira when Jira is down! Therefore the ability to export from the user interface a list of users and their email addresses (and whether they are active) would be useful, so at least a snapshot could be held on file of these users.

            David Nash (inactive) added a comment - When the Jira service has a problem the admnistrator needs to email users about the issue and its progress. You can't do this from Jira when Jira is down! Therefore the ability to export from the user interface a list of users and their email addresses (and whether they are active) would be useful, so at least a snapshot could be held on file of these users.

            I agree. This product provides a great solution but it's very odd and frustrating to be forced into an API calls in order to export admin related information.

            Ray Avakian added a comment - I agree. This product provides a great solution but it's very odd and frustrating to be forced into an API calls in order to export admin related information.

              Unassigned Unassigned
              2954a19bb3fc Tim Oey
              Votes:
              825 Vote for this issue
              Watchers:
              281 Start watching this issue

                Created:
                Updated: