-
Suggestion
-
Resolution: Answered
-
OnDemand
-
64
-
193
-
NOTE: This suggestion is for JIRA Software Cloud. Using JIRA Software Server? See the corresponding suggestion.
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...
https://www.atlassian.com/software/jira/automation-template-library/sum-up-story-points
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,
Eoin
Product Manager
Summary
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
Context:
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
- Configure Scrum board to use "Original Time Estimate" for Estimation Statistic
- Configure Scrum board to use "Remaining Estimate and Time Spent" for Time Tracking
- Create an issue with issue type Story, without specifying any Original Estimate and Remaining Estimate
- 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
- Checking parent of sub-tasks in Issue View, Original Estimate and Remaining Estimate is now shown as 6 hours
- Navigate back to Scrum board, open Issue Detail View, and Original Estimate for parent issue is Unestimated
- details
-
JSWCLOUD-6754 As an Atlassian (enterprise) customer I request that Rapid Board fulfills some MUST HAVE requirements
- Closed
- incorporates
-
JSWCLOUD-16199 There isn't consistency for the Original and Remaining Time estimate fields on Time Tracking gadget and the Board backlog
- Closed
-
JSWCLOUD-16215 Have consistency for the Original and Remaining Time estimate fields on Time Tracking gadget and the Board backlog
- Gathering Interest
- is duplicated by
-
JSWCLOUD-11353 Summing up amount of hours incorrectly around all the application (sprint-scrum))
- Closed
-
JRACLOUD-70975 The sum of the sub-tasks' time estimate is missing from the parent task
- Closed
-
JSWCLOUD-9315 Estimate in detail view for parent jira with sub-tasks
- Closed
-
JSWCLOUD-11306 As a user, I would like to show the User Story's remaining hours as a summation of the subtasks remaining hours on the scrum board so I can quickly see at a glance the remaining hours for a story.
- Closed
-
JSWCLOUD-11563 Sum up of sub-task story points
- Closed
-
JSWCLOUD-13138 Sum estimates from sub-tasks in user stories
- Closed
-
JSWCLOUD-11184 Show total estimate time including subtasks on card
- Closed
- is related to
-
JSWCLOUD-7719 Sum of remaining estimate on sub-tasks not displayed on user story in agile boards
- Closed
-
JSWCLOUD-9113 How do we configure estimation and time tracking
- Closed
-
JSWCLOUD-5614 Would like to see sub-tasks estimation in the main task on the Plan Mode of the Rapid Board
- Gathering Interest
-
JSWSERVER-9167 Provide ability to automatically sum estimates from sub-tasks in user stories
- Future Consideration
-
JSWCLOUD-8726 Sum story points or hour estimates for any epic links
- Not Being Considered
- relates to
-
JSWCLOUD-5653 Original time estimate on the rapidboard is not sum by sub-task
- Closed
-
JSWCLOUD-13505 As a user, I would like to be able to view subtask in backlog
- Closed
-
JSWCLOUD-17275 Display sum of children issues story points and time logged for an Epic
- Gathering Interest
- was cloned as
-
JSWCLOUD-13138 Sum estimates from sub-tasks in user stories
- Closed
- derives
-
SW-5042 Loading...
- mentioned in
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...
-
Page Loading...