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

Agile Sprint Health Gadget not counting sub-tasks

XMLWordPrintable

    • 4
    • 9
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      As a scrum team member, I want the Agile Sprint Health Gadget on dashboard to reflect, not only the stories / main tasks, but also the subs (optional setting)

      Details:
      So, the new nice Agile Sprint Health Gadget does not count sub-tasks.

      Since we are completing a lot of our total stories in the end of a sprint, this is a problem, the gadget does not reflect the actual progress in terms of total issues.

      Eg. 8 stories are in a sprint, they have 5 sub-tasks each, the gadget only shows the 8, not the total 40, or 48 if you would count the Stories.

            [JSWSERVER-9905] Agile Sprint Health Gadget not counting sub-tasks

            Manoj Mathew added a comment -

            Absolute pain and the reports are of no use

            Manoj Mathew added a comment - Absolute pain and the reports are of no use

            Niranjan Vedavyas added a comment -

            We use Jira Project and Scrum Boards. We have User Stories and Subtasks. For estimation we used “Original Estimates” in Hours and Days.

            We usually estimate efforts in subtasks under the User Stories which get accumulated to Story estimates.

            Burndowns are working fine. But we are seeing issues in following scenarios where the subtask estimates are not flowing to User Stories. Following reports are impacted.

            1. Sprint Velocity
            2. Sprint Health Gadget
            3. In the Sprint Backlog when clicking on 3 dots (View summary of assigned work)

             

            Business Impacts: Sprint reports are not accurate, and Business is not happy with report as they are unable to see Sprint velocity as well as Sprint health. Also during Sprint planning as a Scrum Master I as well as PO  having hard time finding the allocated work.

            It is essential for Proper reporting!!!

            Niranjan Vedavyas added a comment - We use Jira Project and Scrum Boards. We have User Stories and Subtasks. For estimation we used “Original Estimates” in Hours and Days. We usually estimate efforts in subtasks under the User Stories which get accumulated to Story estimates. Burndowns are working fine. But we are seeing issues in following scenarios where the subtask estimates are not flowing to User Stories. Following reports are impacted. Sprint Velocity Sprint Health Gadget In the Sprint Backlog when clicking on 3 dots (View summary of assigned work)   Business Impacts: Sprint reports are not accurate, and Business is not happy with report as they are unable to see Sprint velocity as well as Sprint health. Also during Sprint planning as a Scrum Master I as well as PO  having hard time finding the allocated work. It is essential for Proper reporting!!!

            Sankar Nuti added a comment -

            This is a real need for all the scrum masters and the project managers to view the sprint health at a granular level. We can not add all the work as either Story or Task. Also you should consider an option to calculate the story points from child issues like how you are doing for Time Tracking.

            Sankar Nuti added a comment - This is a real need for all the scrum masters and the project managers to view the sprint health at a granular level. We can not add all the work as either Story or Task. Also you should consider an option to calculate the story points from child issues like how you are doing for Time Tracking.

            Florian Knirsch added a comment -

            any update by when this feature / bug is solved?

            sub-task should be counted as well.

            Florian Knirsch added a comment - any update by when this feature / bug is solved? sub-task should be counted as well.

            Matthias Nickel added a comment -

            We really need this. I actually thought, this should be a no brainer.

            Matthias Nickel added a comment - We really need this. I actually thought, this should be a no brainer.

            Kathy Barton added a comment -

            This isn't a suggestion, it's a BUG. The filter query it's based on includes sub-tasks. If they are returned in the Issue Navigator view, it's broken that they aren't represented in the bar graph. SEVEN years is long enough to "gather interest". Does anyone from the product team even look at these tickets? 

            Kathy Barton added a comment - This isn't a suggestion, it's a BUG. The filter query it's based on includes sub-tasks. If they are returned in the Issue Navigator view, it's broken that they aren't represented in the bar graph. SEVEN years is long enough to "gather interest". Does anyone from the product team even look at these tickets? 

            Sabyasachi Samal added a comment -

            It is really required. This suggestion is provided on 2013 and still not taken care.

            Sabyasachi Samal added a comment - It is really required. This suggestion is provided on 2013 and still not taken care.

            walid.jaouadi added a comment -

            Very needed indeed

            +1

            walid.jaouadi added a comment - Very needed indeed +1

            Aditya Sastry added a comment -

            Very needed indeed

            Aditya Sastry added a comment - Very needed indeed

            Adam V added a comment -

            +1

             

            Adam V added a comment - +1  

              Unassigned Unassigned
              61919ed9a012 Jakob Rödström
              Votes:
              85 Vote for this issue
              Watchers:
              65 Start watching this issue

                Created:
                Updated: