Uploaded image for project: 'Jira Platform Cloud'
  1. Jira Platform Cloud
  2. JRACLOUD-90183

Classic: Epic & Release burndown reports do not respect time tracking settings

      Please fix the Epic burndown and release reports to make them respect time tracking settings.

      Epic burndown and release reports do not consider the time tracking setting in classic board settings:

      Given an issue with an original time estimate and some time tracked against it:
       

      We can see this issue is correctly reflected in the sprint burndown report:
       

      But this is not reflected in the epic burndown report:
       

      Only once the issue is transitioned to done does it show up:
       
       

        1. 1.png
          1.png
          109 kB
        2. 2.png
          2.png
          13 kB
        3. 3.png
          3.png
          88 kB
        4. 4.png
          4.png
          30 kB
        5. 5.png
          5.png
          32 kB

            [JRACLOUD-90183] Classic: Epic & Release burndown reports do not respect time tracking settings

            Dylan added a comment -

            Hi all,

            Thank you for raising this bug and bringing it to our attention.

            Within our company roadmap and work capacity, we try to address or review each bug request but admit that not each one will be resolved.

            To continue the culture of being honest and open, we are closing this bug to focus on our upcoming roadmap for all Jira users.

            Dylan added a comment - Hi all, Thank you for raising this bug and bringing it to our attention. Within our company roadmap and work capacity, we try to address or review each bug request but admit that not each one will be resolved. To continue the culture of being honest and open, we are closing this bug to focus on our upcoming roadmap for all Jira users.

              Unassigned Unassigned
              aschneider@atlassian.com Adalberto Schneider
              Affected customers:
              0 This affects my team
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: