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

Sum estimates from sub-tasks in user stories


    • 64
    • 193
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      NOTE: This suggestion is for JIRA Software Cloud. Using JIRA Software Server? See the corresponding suggestion.

      Atlassian status as of February 2021

      Hello all,

      Thank you for watching, voting, and commenting on this issue. We understand this has been a long long long running request. We also understand this has caused a lot of frustration so I don't want to ignore that fact, but I do want to strike a chord of optimism with this update.

      As John mentions in the comment below - the automation team have been busily building out an amazing library of automation rules which cover a massive range of use cases.
      Summing estimates from subtasks to stories is one of these rules and here is the link to how to create this rule...
      Please note there is no limit to the number of rules that you can execute within a single project.

      We do have plans to bring more of these rules from the public library into the in-product automations library, but for now you must replicate the rules manually.

      We're really interested to get your feedback on the success / gaps of this solution so please let us, as well as all other interested users, know here.

      Thank you,
      Product Manager


      As a Greenhopper Scrum product owner, I want story estimates to automatically total to the sum of the estimates for all sub-tasks IF and ONLY IF subtasks are entered (else I want story estimates to be manual entry) so that I can view on the scrum board the original estimate against the remaining time.

      Definition of Done:
      1) When no sub-tasks exist for a story, the estimate field for the story allows entry of a value manually
      2) When one or more sub-tasks exist for a story, the estimate field for the story is calculated as the sum of the estimates for all sub-tasks for that story


      I'm finding a feature in Greenhopper to NOT operate as I would have expected. The feature is in estimating where the estimation on the scrum board is configured for original time estimates. What I would like is:
      1) when no sub-tasks are created for a story, the estimation and remaining fields are editable within the story
      2) when sub-tasks have been created, the story estimate and remaining fields are calculated as the sum of the estimate and remaining fields for the sub-tasks

      What's currently happening is that the story estimate field is not calculated from the sum of the sub-tasks but the story remaining field is. Worse, if you enter a value in the story estimate field when sub-tasks have been added and estimated, the value entered into the story estimate field is added to the story remaining field, which already has the sum of the sub-tasks. Thus, if, as a work around, you try to manually enter a story estimate that equals the sum of the sub-task estimates, the story remaining field value doubles. There's no work around for this. This feature seems poorly defined. I understand what the product team was trying to accomplish... the ability to estimate and view remaining values for stories that have no sub-tasks or prior to sub-tasks being added. What they missed is that the field could serve both functions - manual entry when no sub-tasks exist and calculated value when sub-tasks do exist. I strongly urge the product team to consider this feature at their earliest opportunity as the inability to see from the scrum board the original estimate against the remaining value in plan and work mode is a problem.

      Steps to reproduce
      1. Configure Scrum board to use "Original Time Estimate" for Estimation Statistic
      2. Configure Scrum board to use "Remaining Estimate and Time Spent" for Time Tracking
      3. Create an issue with issue type Story, without specifying any Original Estimate and Remaining Estimate
      4. Create 2 sub-tasks for this issue.
        • Sub-task 1 has Remaining Estimate of 4 hours
        • Sub-task 2 has Remaining Estimate of 2 hours
      5. Checking parent of sub-tasks in Issue View, Original Estimate and Remaining Estimate is now shown as 6 hours
      6. Navigate back to Scrum board, open Issue Detail View, and Original Estimate for parent issue is Unestimated

        1. Automatic Story Estimation.png
          20 kB
        2. Bildschirmfoto 2015-05-07 um 11.33.21.png
          29 kB
        3. image-2016-08-17-09-10-06-185.png
          42 kB
        4. Not on board.png
          5 kB
        5. ScreenHunter_02 Oct. 07 09.30.gif
          4 kB
        6. screenshot-1.png
          41 kB
        7. screenshot-2.png
          190 kB
        8. Screen Shot 2017-07-10 at 09.55.11.png
          177 kB
        9. screenshot-3.png
          190 kB
        10. screenshot-4.png
          190 kB
        11. sprint-plan.png
          29 kB
        12. sprint-report.png
          66 kB
        13. Stupid Scrum Board.png
          119 kB
        14. top voted JSW issues.png
          138 kB
        15. values.PNG
          40 kB
        16. velocity.png
          6 kB

            Unassigned Unassigned
            85b1a6453a93 Michael Manzo
            1735 Vote for this issue
            759 Start watching this issue