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

Epic Burndown report does not display the chart depending on how the Epic Link was created.

XMLWordPrintable

      Issue Summary

      Epic Burndown report does not display the chart depending on how the Epic Link was created.

      Steps to Reproduce

      The Epic Burndown report does not display the chart when using sequence 1 and 2 below to create the Epic Link:

      Sequence 1:

      • New Scrum Project Area
      • Create button, new issue Epic; Epic Name 1, unassigned, SCRUM7-1
      • Create button, new issue Story 1, Assigned to "user1", Epic link to "Epic Name 1 - (SCRUM7-1)"
      • Create button, new issue Story 2, Assigned to "user1", Epic link to "Epic Name 1 - (SCRUM7-1)"
      • Open Epic Burndown report: It shows: 
        This chart cannot be displayed
There are no estimated issues in this epic.
Estimate issues in the Backlog
      • Click the button "Estimate issues in the Backlog"
      • Click each story and assign an Estimative at the quick edit: Story 1, Estimate 5 pts; Story 2, Estimate 3pts;
      • Open Epic Burndown report: same results.

      Sequence 2

      • New Scrum Project Area
      • Create button, new issue Epic; Epic Name 1, unassigned, SCRUM8-1
      • Open backlog, Epic panel and expand the Epic information
      • Use the link "Create an issue in Epic" to create a new issue
      • Create Story 1, Assigned to "user1"
      • Create Story 2, Assigned to "user1"
      • Open Epic Burndown report: It shows 
        This chart cannot be displayed
There are no estimated issues in this epic.
Estimate issues in the Backlog
      • Click the "Estimate issues in the Backlog"
      • Click each story and assign an Estimative, like Story 1, Estimate 5 pts
      • Open Epic Burndown report: same results.

      Sequence 3

      • New Scrum Project Area
      • Create button, new issue Epic; Epic Name 1, unassigned, SCRUM9-1
      • Create Story 1
      • Create Story 2
      • Edit Story 1 created, search for the field "Epic Link"
      • At the Epic link field - type "SCRUM9..." - It will show the "Epic Name 1 - (SCRUM9-1)" at the suggestions - Select it and confirm
      • Edit Story 2 created, search for the field "Epic Link"
      • At the Epic link field - type "SCRUM9..." - It will show the "Epic Name 1 - (SCRUM9-1)" at the suggestions - Select it and confirm
      • Open the backlog
      • Click each story and assign an Estimative, like Story 1, Estimate 5 pts; Story 2, Estimate 3pts;
      • Open Epic Burndown report: it will show correctly the graph, as expected.

      Expected Results

      The graph is presented for all three sequences of steps.

      Actual Results

      The graph is not presented for sequence 1 and 2:

      This chart cannot be displayed
There are no estimated issues in this epic.
Estimate issues in the Backlog

      The team can not keep track of the work that was done or to be done at the Epic.

      Workaround

      Currently, there is no known workaround to fix the already incorrect Epic/Issues.

      The overall recommendation is to create the issue first, and then, edit the issue adding the Epic Link.

      Note: Issue was not reproduced using Jira 7.13.8

            [JSWSERVER-20617] Epic Burndown report does not display the chart depending on how the Epic Link was created.

            Evgenii added a comment -

            I tested next workaround. It works:

            When creating issues do not link the Epic to the ticket. Once the issue has been created, linking the Epic should result in issues being reported OR, if you have issue where Epic was added at creation step, you can delete Epic link and then add it again.

            It should be noted that for any issues that had their Epic linked during creation, they will not show up. 

            Evgenii added a comment - I tested next workaround. It works: When creating issues do not link the Epic to the ticket. Once the issue has been created, linking the Epic should result in issues being reported OR, if you have issue where Epic was added at creation step, you can delete Epic link and then add it again. It should be noted that for any issues that had their Epic linked during creation, they will not show up. 

            Sivarama Krishna K added a comment -

            Thank you for the update.

             

            I tried the options suggested earlier. Agree that only estimated issues will come in the list. 

            My board is depends on Time Estimation. And the estimated issues added to EPIC after creation appear in the list.

            Only issues linked to EPIC  while creation are not working.

             

            I also tried to move all existing issues to new EPIC. It works fine.

             

            Most of the times we use CSV import facility to upload bulk issues and EPIC link also will be added.

             

            In test machine, I used the same backup and observed with 8.9.0 version.

            The behaviors is same like existing system.

             

             

            Sivarama Krishna K added a comment - Thank you for the update.   I tried the options suggested earlier. Agree that only estimated issues will come in the list.  My board is depends on Time Estimation. And the estimated issues added to EPIC after creation appear in the list. Only issues linked to EPIC  while creation are not working.   I also tried to move all existing issues to new EPIC. It works fine.   Most of the times we use CSV import facility to upload bulk issues and EPIC link also will be added.   In test machine, I used the same backup and observed with 8.9.0 version. The behaviors is same like existing system.    

              szarazinski Sławomir Zaraziński
              imurakami@atlassian.com Murakami
              Affected customers:
              3 This affects my team
              Watchers:
              14 Start watching this issue

                Created:
                Updated:
                Resolved: