Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-16329

Timeout errors can occur when completing sprints in Scrum boards

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: High High (View bug fix roadmap)
    • None
    • 7.3.8, 7.4.5, 7.2.12, 7.5.3, 7.6.3, 7.7.1, 8.5.0, 8.5.1, 8.13.0, 8.22.2, 8.20.15, 9.4.11, 9.12.13
    • AgileBoard
    • 7.02
    • 77
    • Severity 3 - Minor
    • 20
    • Hide
      Atlassian Update – 1 October 2024

      Dear Customers,

      Thank you for taking the time to file and comment on this issue. We realize it still occurs and impacts your organization. We are now working on multiple customer requests and on new features, so we have to postpone our resolution of this issue. We’ve decided to move this issue to our long-term backlog.

      Please continue watching this ticket for future updates and changes in the timeline that impacts your work.

      Best regards
      Daniel Dudziak
      Jira DC Developer

      Show
      Atlassian Update – 1 October 2024 Dear Customers, Thank you for taking the time to file and comment on this issue. We realize it still occurs and impacts your organization. We are now working on multiple customer requests and on new features, so we have to postpone our resolution of this issue. We’ve decided to move this issue to our long-term backlog. Please continue watching this ticket for future updates and changes in the timeline that impacts your work. Best regards Daniel Dudziak Jira DC Developer

      Summary

      If completing a sprint takes longer than 60 seconds one will experience a timeout message similar to the following:

      Environment

      • Bulk editing large amount of issues ( 200+ ) takes longer than 60 seconds

      Steps to Reproduce

      1. To reproduce artificially, lower the AJAX timeout to something like 10 seconds and do a sprint release on 3,000 issues
      2. Have a large number of issues in a sprint ( 200+ )
      3. Use remote fields, other customizations, or poor performance that results in bulk editing these issues to take longer than 60 seconds
      4. Attempt to complete sprint, receive error message

      Expected Results

      A more descriptive error message is displayed like the one we implemented for Kanban boards, https://jira.atlassian.com/browse/JSWSERVER-11775

      Actual Results

      A generic timeout error is displayed

      Notes

      Even though a timeout error is displayed the process does continue and issues within the sprint are completed successfully

        1. release_timeout.png
          release_timeout.png
          16 kB

          Form Name

            [JSWSERVER-16329] Timeout errors can occur when completing sprints in Scrum boards

            SET Analytics Bot made changes -
            UIS Original: 19 New: 20
            SET Analytics Bot made changes -
            UIS Original: 26 New: 19
            Marcin Sasinowski made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 1002573 ]
            SET Analytics Bot made changes -
            UIS Original: 33 New: 26
            SET Analytics Bot made changes -
            UIS Original: 32 New: 33
            SET Analytics Bot made changes -
            UIS Original: 39 New: 32
            SET Analytics Bot made changes -
            Support reference count Original: 76 New: 77
            SET Analytics Bot made changes -
            UIS Original: 33 New: 39
            SET Analytics Bot made changes -
            UIS Original: 39 New: 33
            Stasiu made changes -
            Remote Link New: This issue links to "Page (Confluence)" [ 994476 ]

              Unassigned Unassigned
              jcurry Jeff Curry
              Affected customers:
              122 This affects my team
              Watchers:
              117 Start watching this issue

                Created:
                Updated: