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

Epic Report does not show the correct values at the graph depending on how the epic link was created

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Low Low (View bug fix roadmap)
    • None
    • 8.5.1, 8.5.3
    • Reports
    • None

      Issue Summary

      While the Summary of the issues does show the correct values for Total, completed, unestimated issues, and the total of Story Points and done points, the graph does not show the represent the same values.

      Note: Issue was not reproduced using Jira 7.13.8

      Steps to Reproduce

      a) Create a new project SCRUM
      b) Create a new Epic, Epic8393
      c) Create a new Story using the Create button, called Story 8395 and add a link to the Epic8393;
      d) repeat for Story8396, Story8397, Story8398, Story8399, Story8507, Story8508
      e) Create a new Story 5200 using the Create button, but do not add a link to the Epic8393
      f) Open the Backlog board - you will see the Epic8393 with 7 stories
      g) Click over each story to open the quick edition at the right side and estimate the stories:
      story5200 - 3
      story8395 - 8
      story8396 - 5
      story8397 - 8
      story8398 - 13
      story8399 - 8
      story8507 - 8
      j) Edit story5200, search for the field "Epic Link", select the field, add the link to Epic8393, transition the issue to "done"
      k) Edit story8396 and transition the issue to "done"
      l) Open the Epic Report.

      Expected Results


      Actual Results

      Workaround

      Currently, there is no known workaround for this behavior. A workaround will be added here when available

            [JSWSERVER-20620] Epic Report does not show the correct values at the graph depending on how the epic link was created

            Sławomir Zaraziński made changes -
            Resolution New: Duplicate [ 3 ]
            Status Original: Needs Triage [ 10030 ] New: Closed [ 6 ]
            Bugfix Automation Bot made changes -
            Support reference count Original: 2 New: 3
            SET Analytics Bot made changes -
            UIS New: 1
            Bugfix Automation Bot made changes -
            Support reference count Original: 1 New: 2
            Stasiu made changes -
            Remote Link New: This issue links to "FLASH-2468 (Current JIRA)" [ 494685 ]
            Bugfix Automation Bot made changes -
            Introduced in Version New: 8.05
            Murakami [Atlassian Support] made changes -
            Description Original: h3. Issue Summary

            While the Summary of the issues does show the correct values for Total, completed, unestimated issues, and the total of Story Points and done points, the graph does not show the represent the same values.

            h3. Steps to Reproduce

            a) Create a new project SCRUM
             b) Create a new Epic, Epic8393
             c) Create a new Story using the Create button, called Story 8395 and add a link to the Epic8393;
             d) repeat for Story8396, Story8397, Story8398, Story8399, Story8507, Story8508
             e) Create a new Story 5200 using the Create button, but do not add a link to the Epic8393
             f) Open the Backlog board - you will see the Epic8393 with 7 stories
             g) Click over each story to open the quick edition at the right side and estimate the stories:
             story5200 - 3
             story8395 - 8
             story8396 - 5
             story8397 - 8
             story8398 - 13
             story8399 - 8
             story8507 - 8
             j) Edit story5200, search for the field "Epic Link", select the field, add the link to Epic8393, transition the issue to "done"
             k) Edit story8396 and transition the issue to "done"
             l) Open the Epic Report.
            h3. Expected Results

            !Screen Shot 2020-05-15 at 15.09.45.png|width=579,height=188!
            !Screen Shot 2020-05-15 at 15.43.35.png|width=557,height=188!
            h3. Actual Results

            !Screen Shot 2020-07-02 at 19.33.26.png|width=579,height=311!

            !Screen Shot 2020-07-02 at 19.33.38.png|width=573,height=308!
            h3. Workaround

            Currently, there is no known workaround for this behavior. A workaround will be added here when available
            New: h3. Issue Summary

            While the Summary of the issues does show the correct values for Total, completed, unestimated issues, and the total of Story Points and done points, the graph does not show the represent the same values.

            Note: Issue was not reproduced using Jira 7.13.8


            h3. Steps to Reproduce

            a) Create a new project SCRUM
             b) Create a new Epic, Epic8393
             c) Create a new Story using the Create button, called Story 8395 and add a link to the Epic8393;
             d) repeat for Story8396, Story8397, Story8398, Story8399, Story8507, Story8508
             e) Create a new Story 5200 using the Create button, but do not add a link to the Epic8393
             f) Open the Backlog board - you will see the Epic8393 with 7 stories
             g) Click over each story to open the quick edition at the right side and estimate the stories:
             story5200 - 3
             story8395 - 8
             story8396 - 5
             story8397 - 8
             story8398 - 13
             story8399 - 8
             story8507 - 8
             j) Edit story5200, search for the field "Epic Link", select the field, add the link to Epic8393, transition the issue to "done"
             k) Edit story8396 and transition the issue to "done"
             l) Open the Epic Report.
            h3. Expected Results

            !Screen Shot 2020-05-15 at 15.09.45.png|width=579,height=188!
            !Screen Shot 2020-05-15 at 15.43.35.png|width=557,height=188!
            h3. Actual Results

            !Screen Shot 2020-07-02 at 19.33.26.png|width=579,height=311!

            !Screen Shot 2020-07-02 at 19.33.38.png|width=573,height=308!
            h3. Workaround

            Currently, there is no known workaround for this behavior. A workaround will be added here when available
            Murakami [Atlassian Support] made changes -
            Introduced in Version Original: 8.05
            Bugfix Automation Bot made changes -
            Support reference count New: 1
            Bugfix Automation Bot made changes -
            Introduced in Version New: 8.05

              Unassigned Unassigned
              imurakami@atlassian.com Murakami [Atlassian Support]
              Affected customers:
              0 This affects my team
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: