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
    • 13
    • 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

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

            Jordi Beltran added a comment -

            Any progress on that? It's not a minor issue

            Jordi Beltran added a comment - Any progress on that? It's not a minor issue

            Aswin Pola added a comment -

            The link provided in the Steps to Repro - https://confluence.atlassian.com/jirakb/how-to-change-the-default-ajax-timeout-in-jira-server-824345485.html for Ajax timeout does not work anymore and looks like dead. Can you please update?

            Aswin Pola added a comment - The link provided in the Steps to Repro - https://confluence.atlassian.com/jirakb/how-to-change-the-default-ajax-timeout-in-jira-server-824345485.html for Ajax timeout does not work anymore and looks like dead. Can you please update?

            John Roberts-Davies added a comment -

            This is affecting my users as well. Please confirm the plan to fix this.

            John Roberts-Davies added a comment - This is affecting my users as well. Please confirm the plan to fix this.

            Cedric Lavoie added a comment -

            ddudziak , thank you for the update.

            It literally just happened to me again, 3 minutes ago:

            Cedric Lavoie added a comment - ddudziak , thank you for the update. It literally just happened to me again, 3 minutes ago:

            Stasiu added a comment -

            Hello 0a53cb671019,
            I am really sorry for the inconvenience, my team is trying to escalate the issue internally to clarify steps to reproduce. I have changed the status of the bug once again, and right now it is opened in proper state. When we finish the triage process, I will make an update once again.

            Best regards
            Daniel Dudziak
            Jira DC Developer

            Stasiu added a comment - Hello 0a53cb671019 , I am really sorry for the inconvenience, my team is trying to escalate the issue internally to clarify steps to reproduce. I have changed the status of the bug once again, and right now it is opened in proper state. When we finish the triage process, I will make an update once again. Best regards Daniel Dudziak Jira DC Developer

            Cedric Lavoie added a comment -

            How was this CLOSED as CANNOT REPRODUCE?! This is still VERY ACTIVE on 9.4.23!

            mkwidzinski ?!

            Cedric Lavoie added a comment - How was this CLOSED as CANNOT REPRODUCE?! This is still VERY ACTIVE on 9.4.23! mkwidzinski ?!

            Maciej Kwidziński (Inactive) added a comment - - edited

            jcurry I cannot reproduce this step:

            Use remote fields, other customizations, or poor performance that results in bulk editing these issues to take longer than 60 seconds

            Could you provide specific steps to repro?
            We missed that during triage. I'm closing as "cannot reproduce". Feel free to reopen when repro steps are updated.

            WRT the "Expected Results", do we actually expect just a different timeout error message? My gut tells me DFTC: avoid the timeout. Either by speeding up the operation or adding a progress bar.

            Maciej Kwidziński (Inactive) added a comment - - edited jcurry I cannot reproduce this step: Use remote fields, other customizations, or poor performance that results in bulk editing these issues to take longer than 60 seconds Could you provide specific steps to repro? We missed that during triage. I'm closing as "cannot reproduce". Feel free to reopen when repro steps are updated. WRT the "Expected Results", do we actually expect just a different timeout error message? My gut tells me DFTC: avoid the timeout. Either by speeding up the operation or adding a progress bar.

            sai kumar added a comment -

            4555db5a5f8f the sprint has 2 issues or 20 issues the behavior is same time-out issues. I have uploaded the profiling logs to ticket PSSRV-127031

            sai kumar added a comment - 4555db5a5f8f the sprint has 2 issues or 20 issues the behavior is same time-out issues. I have uploaded the profiling logs to ticket PSSRV-127031

            Gonchik Tsymzhitov added a comment -

            Maybe someone will share profiling log?
            which can help to easier detect an issue?
            77db90677e1d how many tickets were in that sprint?

            Gonchik Tsymzhitov added a comment - Maybe someone will share profiling log? which can help to easier detect an issue? 77db90677e1d how many tickets were in that sprint?

            sai kumar added a comment -
            • 9.12.8 also have this issue, even with only 1 or 2 issues in the sprint we are getting similar issue.

            sai kumar added a comment - 9.12.8 also have this issue, even with only 1 or 2 issues in the sprint we are getting similar issue.

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

                Created:
                Updated: