Uploaded image for project: 'Jira Cloud'
  1. Jira Cloud
  2. JSWCLOUD-15944

Epic burndown chart report not displaying issues when linked during issue creation

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Highest Highest
    • None

      Summary

      Epic burndown chart is not displaying information for tickets with time estimation matching board configuration without JIRA Software. This problem appears to occur specifically when the issue is added to the Epic during issue creation, as opposed to being added after the issue is already created.

      Environment

      JIRA v1000.35.2
      JIRA Agile v1000.0.4-D20160607T123719

      Steps to Reproduce

      1. Create a new Agile board
      2. Configure the board estimation to be based on Original Time Estimate
      3. Create a new Epic within an Agile board
      4. Create a new issue within that Epic
      5. Give the new issue Original Time Estimate points and Time Remaining points
      6. Create a new sprint within the Agile board
      7. Add the new ticket to the sprint
      8. Start the sprint
      9. View the Epic burndown chart report

      Expected Results

      Report should display ticket information for the one ticket you added to the Epic

      Actual Results

      No issues are displayed
      Instead the Epic burndown chart report displays a message stating you have no issues with estimations

      Workaround

      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.

      It should be noted that for any issues that had their Epic linked during creation, they will not show up. There is currently no work around to fix these issues.

            [JSWCLOUD-15944] Epic burndown chart report not displaying issues when linked during issue creation

            Closing as a duplicate of JSW-13750.

            Matthew Hunter added a comment - Closing as a duplicate of JSW-13750 .

            Added the work around as I tested this and it does in fact result in issues showing up in the Epic burndown report

            mlavender (Inactive) added a comment - Added the work around as I tested this and it does in fact result in issues showing up in the Epic burndown report

              Unassigned Unassigned
              mlavender mlavender (Inactive)
              Affected customers:
              0 This affects my team
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: