Summary

      Sprint Burndown gadget does not load any data on the dashboard.
      Sometimes it's possible to make it load, but it's intermittent and doesn't seems to have anything else related.

      It could be caused by the chromium bug. What causes some of the requests could not be performed by the web browser. It is because of insufficient resources.

      To see the fix make sure to run jira-software-application using 

      -Datlassian.dev.mode=false

      Environment

      • JIRA 7.11.0

      Steps to Reproduce

      1. Add couple(6 or more) Sprint Burndown gadget to the dashboard,
      2. In gadget's configuration, select the board with the current active Sprint and refresh interval is 15 minutes, Save,
      3. Enable developer console 
      4. Refresh the page

      Expected Results

      The gadget should load the data

      Actual Results

      The gadget does not load any data (blank)

      In the console log and developer tools you can find this error:

      net::ERR_INSUFFICIENT_RESOURCES

       

      Workaround

      1. If you are the owner of the Dashboard: Click Edit -> Cancel on the gadget configuration.
      2. If you are not, you can either:
        • Copy that dashboard and then click Edit -> Cancel button Or
        • Ask the owner of the board to change the Refresh Interval of the gadget to 15 minutes, the data will be loaded after 15 minutes.
      3. Decrease the number of gadgets on the board,
      4. Switch to another web browser like Firefox

      Notes:
      This happens mainly on Google Chrome, also verified in Safari and IE.
      Note that the issue has also been observed on Firefox by customers, so switching to Firefox is not guaranteed to resolve the issue.

            [JSWSERVER-16791] Sprint burn down gadget doesn't display any data

            Andy Rusnak made changes -
            Remote Link Original: This issue links to "BJBR-18 (Bulldog)" [ 628507 ] New: This issue links to "BJBR-18 (JIRA Server (Bulldog))" [ 628507 ]

            SKAdmin added a comment - - edited

            Hello - Any chance this will be added to the LTS versions. We are still seeing this problem in Jira v8.20.14 in Chrome Version 108.0.5359.125. Same problem with the Version report and rate limiting isn't on, which was logged as the other reason for the blank gadgets. 

            SKAdmin added a comment - - edited Hello - Any chance this will be added to the LTS versions. We are still seeing this problem in Jira v8.20.14 in Chrome Version 108.0.5359.125. Same problem with the Version report and rate limiting isn't on, which was logged as the other reason for the blank gadgets. 

            Found root cause: If a board has stories of 2 sprints e.g. by having a testing story of another team (other sprint naming), the setting'Next Sprint Due' is unable to select the intended sprint name. Selecting manually the 

            intended sprint does work.

            Suzanne Lemm added a comment - Found root cause: If a board has stories of 2 sprints e.g. by having a testing story of another team (other sprint naming), the setting'Next Sprint Due' is unable to select the intended sprint name. Selecting manually the  intended sprint does work.
            Mateusz Beczek made changes -
            Resolution New: Fixed [ 1 ]
            Status Original: Waiting for Release [ 12075 ] New: Closed [ 6 ]
            SET Analytics Bot made changes -
            Support reference count Original: 54 New: 55
            Sylwia Mikołajczuk made changes -
            Fix Version/s Original: 9.0.1 [ 100190 ]
            Fix Version/s New: 9.0.0 [ 97892 ]
            SET Analytics Bot made changes -
            UIS Original: 230 New: 222
            SET Analytics Bot made changes -
            UIS Original: 204 New: 230
            SET Analytics Bot made changes -
            UIS Original: 230 New: 204
            SET Analytics Bot made changes -
            UIS Original: 231 New: 230

              afb6234f8e80 Mark Patterson (Inactive)
              estorch Eric Storch (Inactive)
              Affected customers:
              81 This affects my team
              Watchers:
              88 Start watching this issue

                Created:
                Updated:
                Resolved: