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.

          Form Name

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

            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.

            We just upgraded to:  v8.13.19#813019-sha1:8e0e137

            and our Sprint Burndown Gadgets are now working, in Chrome Version 99.0.4844.74.

            Karen Hayden added a comment - We just upgraded to:  v8.13.19#813019-sha1:8e0e137 and our Sprint Burndown Gadgets are now working, in Chrome Version 99.0.4844.74.

            The reporter and assignee are inactive. Is this issue now in la-la land?

            Apryl Harris added a comment - The reporter and assignee are inactive. Is this issue now in la-la land?

            Ekaterina Smykova added a comment - - edited

            Hi! 

            Any SLA? Out customers can not use gadget in their dashboards or finding workarounds which are painful

            Note: Jira Version 8.20.0. Issue still there.

            Regards,
            Katja

            Ekaterina Smykova added a comment - - edited Hi!  Any SLA? Out customers can not use gadget in their dashboards or finding workarounds which are painful Note: Jira Version 8.20.0. Issue still there. Regards, Katja

            Paul Wardle added a comment - - edited

            This is an issue for us, Jira Server v8.8.0. We get the following error in the console

            (Google Chrome v93.0.4577.63, 64 bit)

            com.pyxis.greenhopper.jira:jira-agile-burndown-chart.js?locale=en-UK:201 Uncaught TypeError: Cannot read properties of undefined (reading 'getSelectedItem')
            at Object.k.renderUI (com.pyxis.greenhopper.jira:jira-agile-burndown-chart.js?locale=en-UK:201)
            at Object.k.showChart (com.pyxis.greenhopper.jira:jira-agile-burndown-chart.js?locale=en-UK:201)
            at Object.d.processChartData (com.pyxis.greenhopper.jira:jira-agile-burndown-chart.js?locale=en-UK:211)
            at c (com.atlassian.plugins.jquery:jquery.js:34)
            at Object.fireWith [as resolveWith] (com.atlassian.plugins.jquery:jquery.js:34)
            at Object.a.<computed> (com.atlassian.plugins.jquery:jquery.js:34)
            at c (com.atlassian.plugins.jquery:jquery.js:34)
            at Object.add [as done] (com.atlassian.plugins.jquery:jquery.js:34)
            at Object.<anonymous> (com.atlassian.plugins.jquery:jquery.js:34)
            at c (com.atlassian.plugins.jquery:jquery.js:34)

            Paul Wardle added a comment - - edited This is an issue for us, Jira Server v8.8.0. We get the following error in the console (Google Chrome v93.0.4577.63, 64 bit) com.pyxis.greenhopper.jira:jira-agile-burndown-chart.js?locale=en-UK:201 Uncaught TypeError: Cannot read properties of undefined (reading 'getSelectedItem') at Object.k.renderUI (com.pyxis.greenhopper.jira:jira-agile-burndown-chart.js?locale=en-UK:201) at Object.k.showChart (com.pyxis.greenhopper.jira:jira-agile-burndown-chart.js?locale=en-UK:201) at Object.d.processChartData (com.pyxis.greenhopper.jira:jira-agile-burndown-chart.js?locale=en-UK:211) at c (com.atlassian.plugins.jquery:jquery.js:34) at Object.fireWith [as resolveWith] (com.atlassian.plugins.jquery:jquery.js:34) at Object.a.<computed> (com.atlassian.plugins.jquery:jquery.js:34) at c (com.atlassian.plugins.jquery:jquery.js:34) at Object.add [as done] (com.atlassian.plugins.jquery:jquery.js:34) at Object.<anonymous> (com.atlassian.plugins.jquery:jquery.js:34) at c (com.atlassian.plugins.jquery:jquery.js:34)

            nidhis added a comment -

            Could you please let us know the SLA of the issue? it has been there since long but not resolved yet.

             

            Users are getting impacted by this issue.

            nidhis added a comment - Could you please let us know the SLA of the issue? it has been there since long but not resolved yet.   Users are getting impacted by this issue.

            Del (Inactive) added a comment - https://getsupport.atlassian.com/browse/SDS-59764

            Vladimir added a comment -

            One note more. It is still happening today but the mentioned bug in Chromium is fixed just long time ago!

            Vladimir added a comment - One note more. It is still happening today but the mentioned bug in Chromium is fixed just long time ago!

            Vladimir added a comment -

            We also see the same problem. We use Structure gadgets. Put there about 6 and more such gadgets plus some Pie gadgets. When we refresh whole page in Chrome by pressing F5 it sometimes helps to show all gadgets. But if we open the page by SHIFT+F5 then it nearly every time does not work. 

            In Firefox it is working but I cannot garantie because it is happen after some time not immediately.

            Please take into considaration it and say if you can reproduce the same behaviour if yes then speak with Chromium or firefox developers and try find out the solution. It is much better if you will do it by as a big company then particular customers.

            Vladimir added a comment - We also see the same problem. We use Structure gadgets. Put there about 6 and more such gadgets plus some Pie gadgets. When we refresh whole page in Chrome by pressing F5 it sometimes helps to show all gadgets. But if we open the page by SHIFT+F5 then it nearly every time does not work.  In Firefox it is working but I cannot garantie because it is happen after some time not immediately. Please take into considaration it and say if you can reproduce the same behaviour if yes then speak with Chromium or firefox developers and try find out the solution. It is much better if you will do it by as a big company then particular customers.

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

                Created:
                Updated:
                Resolved: