Uploaded image for project: 'Atlassian Product Integrations'
  1. Atlassian Product Integrations
  2. API-474

Timeout errors when exporting search results to Excel

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Low Low
    • None
    • 1.0
    • Jira Cloud for Excel
    • None
    • Severity 3 - Minor

      Issue Summary

      Exporting search results with a high number of fields to Excel will often result in errors and timeouts.

      Steps to Reproduce

      1. Create a search that returns a high number of issues (~1k tickets should work)
      2. Add multiple columns to the search results. If possible, add SLA fields, as they seem to have a higher impact.
      3. Export the results by clicking on "Open on Microsoft Excel".

      Expected Results

      The query results will open on Excel or the file will be successfully downloaded.

      Actual Results

      An error will happen:

      Workaround

      • Use the "Open in Google sheets" instead. (The bug doesn't seem to affect the Google sheets export)
      • Export fewer fields and combine the two files later.
        • Example: Export the Issue Key and the SLA fields apart from the rest of the fields.

        1. image-2021-10-19-09-41-17-839.png
          image-2021-10-19-09-41-17-839.png
          11 kB
        2. image-2021-10-19-09-42-31-770.png
          image-2021-10-19-09-42-31-770.png
          34 kB

            [API-474] Timeout errors when exporting search results to Excel

            Samyak Mehta added a comment -

            Hi all,

            We have made some significant improvements in our architecture to better handle the load of the ever increasing demand for the Issue imports. We see that the errors have gone down by 95% after the changes have been rolled out. If you face import issues, try the following:

            1. Retry the import because it may have been an intermittent rate limit imposition by Google or Jira.
            2. Try dividing your imports into multiple chunks if larger imports fail.
            3. If possible, increase the duration of your scheduled imports as frequent large imports tend to utilise the capacity of your instance much faster.

            Feel free to reach out in case you face persistent issues. Thank you!

            Samyak Mehta added a comment - Hi all, We have made some significant improvements in our architecture to better handle the load of the ever increasing demand for the Issue imports. We see that the errors have gone down by 95% after the changes have been rolled out. If you face import issues, try the following: Retry the import because it may have been an intermittent rate limit imposition by Google or Jira. Try dividing your imports into multiple chunks if larger imports fail. If possible, increase the duration of your scheduled imports as frequent large imports tend to utilise the capacity of your instance much faster. Feel free to reach out in case you face persistent issues. Thank you!

            Paula Hidalgo added a comment -

            @Vitalii Saienko - What is the status of this bug fix?  We have experienced intermittent issues with the Excel import over the past 6 months.  We use this functionality for reporting to Senior Leadership on our large programs.

            Paula Hidalgo added a comment - @Vitalii Saienko - What is the status of this bug fix?  We have experienced intermittent issues with the Excel import over the past 6 months.  We use this functionality for reporting to Senior Leadership on our large programs.

              vsaienko Vitalii Saienko (Inactive)
              pjunior Paulo Junior (Inactive)
              Affected customers:
              9 This affects my team
              Watchers:
              20 Start watching this issue

                Created:
                Updated:
                Resolved: