• 6,361
    • 549
    • 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.

      Atlassian Update - September 2024

      Hi everyone,

      Thank you for taking the time to share your feature request with us. Your input is greatly appreciated, and we understand the effort and dedication it takes to provide us with your thoughts and ideas.

      We are actively looking into and considering a solution for this feature request. Our team is committed to thoroughly investigating the best way to address this need, and we will keep you informed as if we get closer towards a release date.

      Thank you to every person who provided feedback on this issue. We will update you as soon as we have more concrete information to share. 

      Joe Nguyen
      Product Manager- Jira Cloud
      jnguyen2@atlassian.com

       

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

      Problem Definition

      Currently, when exporting Search Results the user interface by default only allows a user to export a maximum of 1000 issues to an excel spreadsheet. This applies to all other exports as well (CSV).

      Suggested Solution

      Consider slightly increasing the limit, provided the Cloud Server can handle the increase

      Workaround

      Please consult the KB article at Cloud - Export More than 1000 issues to Excel from Issue Navigator
      or
      https://confluence.atlassian.com/jirakb/export-over-1000-results-to-excel-from-jira-cloud-779160833.html

          Form Name

            [JRACLOUD-25493] Export to Excel is limited to a maximum of 1000 issues

            Even though there is a work around, we need a better solution. The work around is taking longer time to get the full result and if folks are not that technical in nature, will miss the full execution and wasting their time.

             

            If realtime fetch is taking longer time and causing performance issues, please add a batch mode to get the results , so that system can choose , how to run without impacting the performance.

             

            Thomas Titty (FCA) added a comment - Even though there is a work around, we need a better solution. The work around is taking longer time to get the full result and if folks are not that technical in nature, will miss the full execution and wasting their time.   If realtime fetch is taking longer time and causing performance issues, please add a batch mode to get the results , so that system can choose , how to run without impacting the performance.  

            KC Wong added a comment -

            Completely reasonable and much needed feature request, that lasted 14 whole years just to be about to be considered for implementation.

            Bravo, Atlassian. You'd think they'd have won some kind of Guinness world records by now. 

            A PowerShell script I wrote

            Basically it invokes the REST API for you, pulls issue data and write the result as a CSV file. 
            Uses Get-Credential to protect your API token. 
            Caveat: I haven't done text formatting for all types of fields. Update the ParseFieldValue function if you want to support the more complex field types. 

            To see help message: 
            >Get-Help .\GenerateReport.ps1

            To use interactive mode: 
            >.\GemerateReport.ps1

            KC Wong added a comment - Completely reasonable and much needed feature request, that lasted 14 whole years just to be about to be considered for implementation. Bravo, Atlassian. You'd think they'd have won some kind of Guinness world records by now.  A PowerShell script I wrote Basically it invokes the REST API for you, pulls issue data and write the result as a CSV file.  Uses Get-Credential to protect your API token.  Caveat: I haven't done text formatting for all types of fields. Update the ParseFieldValue function if you want to support the more complex field types.  To see help message:  >Get-Help .\GenerateReport.ps1 To use interactive mode:  >.\GemerateReport.ps1

            Thanks, I have used Excel to get Jira data.

            Arpan Mishra added a comment - Thanks, I have used Excel to get Jira data.

            CHILUMKURU added a comment -

            Hi 11968eb17a86 ,

            You can download in chunks of 1000 records at once using below process.

            You can use workaround below.

            a) Right-click the URL for export (either "All Fields" or "Current Fields") and select Copy Link Location. The URL should be similar to:

            http://localhost:8080/sr/jira.issueviews:searchrequest-excel-current-fields/temp/SearchRequest.xls?query=ER%5C+&summary=true&description=true&tempMax=1000

            b). Paste that URL into a different browser tab.

            c). Append the &pager/start=1000 at the end of the URL string to instruct JIRA to export from index 1001 and above (1000 rows). And click on Enter

            http://localhost:8080/sr/jira.issueviews:searchrequest-excel-current-fields/temp/SearchRequest.xls?query=ER%5C+&summary=true&description=true&tempMax=1000&pager/start=1000

             d. Next export should append the &pager/start=2000 (change from &pager/start=1000 to &pager/start=2000) at the end of the URL string to instruct JIRA to export from index 2001 and above (1000 rows).

            e. Repeat the above steps by incrementing Start=$000 based on your ticket volume

            like start=1000 (for 1001 to 2000)

            , start=2000  (for 2001 to 3000)

            , start=3000  (for 3001 to 4000)

            so on 

            CHILUMKURU added a comment - Hi 11968eb17a86 , You can download in chunks of 1000 records at once using below process. You can use workaround below. a) Right-click the URL for export (either "All Fields" or "Current Fields") and select Copy Link Location. The URL should be similar to: http://localhost:8080/sr/jira.issueviews:searchrequest-excel-current-fields/temp/SearchRequest.xls?query=ER%5C+&summary=true&description=true&tempMax=1000 b). Paste that URL into a different browser tab. c). Append the &pager/start=1000 at the end of the URL string to instruct JIRA to export from index 1001 and above (1000 rows). And click on Enter http://localhost:8080/sr/jira.issueviews:searchrequest-excel-current-fields/temp/SearchRequest.xls?query=ER%5C+&summary=true&description=true&tempMax=1000&pager/start=1000  d. Next export should append the &pager/start=2000 (change from &pager/start=1000 to &pager/start=2000) at the end of the URL string to instruct JIRA to export from index 2001 and above (1000 rows). e. Repeat the above steps by incrementing Start= $ 000 based on your ticket volume like start=1000 (for 1001 to 2000) , start=2000  (for 2001 to 3000) , start=3000  (for 3001 to 4000) so on 

            While exporting the Jira issues in CSV format from a Project, its only showing/exporting 1000 records. i can see there are 4000+ records in system. What is the easier solution/option to export all the issues including all fields from Jira?

            Arpan Mishra added a comment - While exporting the Jira issues in CSV format from a Project, its only showing/exporting 1000 records. i can see there are 4000+ records in system. What is the easier solution/option to export all the issues including all fields from Jira?

            Please bring back this functionality, it's essential! Thanks!

            Stefano Mei - QIAGEN added a comment - Please bring back this functionality, it's essential! Thanks!

            This is most disappointing. 

            Kevin Mifsud added a comment - This is most disappointing. 

            Amit Singh added a comment -

            This is essential feature and need to be released as early as possible. 

            Amit Singh added a comment - This is essential feature and need to be released as early as possible. 

            Andy Zhou added a comment -

            Need to get this bug fixed, please.

            Andy Zhou added a comment - Need to get this bug fixed, please.

            jtang added a comment -

            It's so stupid that we cannot export more than 1000 issues easily.  Resolved it as soon as possible.

            jtang added a comment - It's so stupid that we cannot export more than 1000 issues easily.  Resolved it as soon as possible.

              6d9c235ccde3 Shilpa Airi
              23f818962e19 vinod Eppa
              Votes:
              418 Vote for this issue
              Watchers:
              342 Start watching this issue

                Created:
                Updated: