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

Importing issue in Excel results in error and never finish

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Low Low
    • None
    • None
    • Jira Cloud for Excel
    • Minor

      Issue Summary

      When trying to import some number of issues (e.g. 5000), it doesn't work and results in "Oops... Something went wrong. Try importing again" error. Lowering the issue limit to 2500 resolve the problem

      Steps to Reproduce

      1. Open Excel and Jira Cloud for Excel add-in.
      2. Go to "Fields" tab and select fields which can contain a lot of text data.
      3. Set maximum issues to 5000 (in some cases the limit might be higher or lower, depends on the issue data volume).
      4. Click "Refresh data" and observe the error.

      Expected Results

      All issues are imported.

      Actual Results

      It doesn't import all issues.

      Workaround

      There are two options:

      • Find the "Max rows" value that works and use it
      • Deselect fields in the "Fields" tab which potentially can contain a lot of text data (e.g. description).

       

            [API-468] Importing issue in Excel results in error and never finish

            Samyak Mehta made changes -
            Resolution New: Fixed [ 1 ]
            Status Original: In Progress [ 3 ] New: Closed [ 6 ]

            Hi all,

            We have made some 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 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!

            I was able to by-pass this issue to a certain extent by removing the "Key" field from the request.

            I believe this field was causing the timeout because it also contains the URL to access the ticket (an ideal fix might be decouple these two pieces of data), which drastically increases the size of the response being returned, which causes the timeout.

            Christian Allard added a comment - I was able to by-pass this issue to a certain extent by removing the "Key" field from the request. I believe this field was causing the timeout because it also contains the URL to access the ticket (an ideal fix might be decouple these two pieces of data), which drastically increases the size of the response being returned, which causes the timeout.

            Any update to this issue? Recently had to switch over from Google to Microsoft 365 and now running into this with every import attempt which is a major blocker for me currently.

            Benjamin Proctor added a comment - Any update to this issue? Recently had to switch over from Google to Microsoft 365 and now running into this with every import attempt which is a major blocker for me currently.
            Max made changes -
            Remote Link Original: This issue links to "PNL-1093 (Jira)" [ 581224 ] New: This issue links to "JCSS-386 (pi-dev-sandbox.atlassian.net)" [ 581224 ]

            I had been able to use the Excel add-on from September 2022 until early this year, regularly updating a file with about 11,000 records and 25 fields. Reducing scope (# records exported or # fields) doesn't resolve the issue. The only workaround is to keep running filters in Jira, then exporting to Excel. That feels like a huge step backwards to me. 

            From my last comment to Atlassian Support:

            I agree that the workaround is functional - though it’s suboptimal from a workflow and execution standpoint.
            I realize that intermittent defects are difficult to reproduce, but I do believe this is a defect somewhere in the add-on.
            I further believe that a company that can produce a SaaS product that runs at scale should be able to deliver and add-on that runs at scale. The only other alternative is better reporting built into the product itself. 
            
            

            Support thread: (https://support.atlassian.com/requests/PCS-156626/). 

            Joel Bredahl added a comment - I had been able to use the Excel add-on from September 2022 until early this year, regularly updating a file with about 11,000 records and 25 fields. Reducing scope (# records exported or # fields) doesn't resolve the issue. The only workaround is to keep running filters in Jira, then exporting to Excel. That feels like a huge step backwards to me.  From my last comment to Atlassian Support: I agree that the workaround is functional - though it’s suboptimal from a workflow and execution standpoint. I realize that intermittent defects are difficult to reproduce, but I do believe this is a defect somewhere in the add-on. I further believe that a company that can produce a SaaS product that runs at scale should be able to deliver and add-on that runs at scale. The only other alternative is better reporting built into the product itself. Support thread: ( https://support.atlassian.com/requests/PCS-156626/ ). 
            Abhishek Singh made changes -
            Labels New: jsm-s16

            same issue... anything new on resolving it?

            Jasna Gasparič added a comment - same issue... anything new on resolving it?
            RS Dela Peña made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 603962 ]
            Diptajeet Datta made changes -
            Attachment Original: image-1.png [ 411027 ]

              Unassigned Unassigned
              vsaienko Vitalii Saienko (Inactive)
              Affected customers:
              12 This affects my team
              Watchers:
              27 Start watching this issue

                Created:
                Updated:
                Resolved: