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

Burnup Chart unavailable in reports

XMLWordPrintable

      Issue Summary

      Burnup Chart report is unavailable in board reports after upgrading to Jira 8.22.1.

      This is reproducible on Data Center: Yes

      Steps to Reproduce

      1. Upgrade to Jira 8.22.1     *There are also affected other versions in the LTS releases.
      2. Access a Scrum board.
      3. Access report page of the board.

      Expected Results

      Burnup Chart is available on the report page:

      Actual Results

      Burnup Chart is missing from the report page:

      Workaround

      To restore the burnup chart please add the dark feature setting

      com.atlassian.jira.agile.darkfeature.burnupchart.enabled

      as outlined in How to manage dark features in Jira to the instance.

      Accessing <Jira URL>/secure/RapidBoard.jspa?projectKey=<project key>&rapidView=1&view=reporting&chart=burnupChart URL just redirect users to Burndown Chart report

        1. 8220.png
          8220.png
          168 kB
        2. 8221.png
          8221.png
          161 kB

          Form Name

            [JSWSERVER-21297] Burnup Chart unavailable in reports

            Olivia Margina added a comment - - edited

            Known issue to me

            Olivia Margina added a comment - - edited Known issue to me

            Andriy Yakovlev [Atlassian] added a comment - - edited

            Hey folks 20ba0eacffe5/b4db5e5eb853

            Our team double-checked the code and confirmed that the Burnup chart is now visible in the report page .

            However, please note that there is a related problem: when chosen, Burnup Chart redirects to Burndown Chart (JSWSERVER-21344). Our team is working to fix the latter problem right now.

            Please contact our support team if you need further help, they will investigate this problem together with you.

            Hope it helps.
            Thanks.

            Best regards,
            Andriy | SET

            Andriy Yakovlev [Atlassian] added a comment - - edited Hey folks 20ba0eacffe5 / b4db5e5eb853 Our team double-checked the code and confirmed that the Burnup chart is now visible in the report page . However, please note that there is a related problem: when chosen, Burnup Chart redirects to Burndown Chart ( JSWSERVER-21344 ). Our team is working to fix the latter problem right now. Please contact our support team if you need further help, they will investigate this problem together with you. Hope it helps. Thanks. Best regards, Andriy | SET

            John Hayes added a comment -

            Can confirm, not fixed in 8.22.2

            John Hayes added a comment - Can confirm, not fixed in 8.22.2

            VP IT Support added a comment -

            Upgraded to 8.22.2 yesterday to fix a vulnerability.  Burnup chart is not available.  Had to enable it via dark feature.

            VP IT Support added a comment - Upgraded to 8.22.2 yesterday to fix a vulnerability.  Burnup chart is not available.  Had to enable it via dark feature.

            Alex [Atlassian,PSE] added a comment - - edited

            Validated problem occur when upgrading Jira 8.20.6 to 8.20.7. Issue not present in 8.20.6.

            Bumped severity to Major - whole parts of the plugin is unavailable. Regression on LTS release.

            agile-sprint-burnup, jira-agile-sprint-burnup-report, jira-agile-burnup-chart are all present and enabled modules of Jira Agile plugin in the affected versions.

            Alex [Atlassian,PSE] added a comment - - edited Validated problem occur when upgrading Jira 8.20.6 to 8.20.7. Issue not present in 8.20.6. Bumped severity to Major - whole parts of the plugin is unavailable. Regression on LTS release. agile-sprint-burnup, jira-agile-sprint-burnup-report, jira-agile-burnup-chart are all present and enabled modules of Jira Agile plugin in the affected versions.

              15609d8ba305 Filip Nowak
              vshanmugam Vicknesh Shanmugam (Inactive)
              Affected customers:
              19 This affects my team
              Watchers:
              40 Start watching this issue

                Created:
                Updated:
                Resolved: