-
Suggestion
-
Resolution: Fixed
-
- Configure Rapid board with "Original Time Estimate" as the Estimation Statistic.
NOTE: This suggestion is for JIRA Software Server. Using JIRA Software Cloud? See the corresponding suggestion.
When adding sub-tasks with estimations, the Estimation field in the Plan and Work mode are not cumulative.
Steps:
1- Add a Story to back log.
2- Add a Sub Task with 8hrs estimate to that Story
3- Notice that on the Sprint Marker the "Estimate" field is not updated. Same for the Template view on the right side..
- If you open the Story outside of the Rapid Board then the time tracking is cumulative.
- Refer to attachment for a screenshot. The screenshot does not show the Original Estimation for the Sub Task, but it is set to 8hrs.
- is duplicated by
-
JSWSERVER-5679 Estimates of sub-tasks not cumulated on parent task
-
- Closed
-
- is related to
-
-
- Closed
-
- relates to
-
- Closed
-
- Gathering Interest
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JSWSERVER-5283] Time estimates for sub tasks are not added to the total estimate of a Story in the Plan and Work view.
Bojana Mandic
added a comment - Any solution for this request? Has anyone come up with a workaround using a plugin? If yes, what plugins would you recommend for Jira Server?
Bojana Mandic
added a comment - Any solution for this request? Has anyone come up with a workaround using a plugin? If yes, what plugins would you recommend for Jira Server? We just bumped into this as well. Will this ever be addressed?
If not, we'll have to abandon using sub-tasks (boo) to have velocity and estimating accurate in Jira.
Janene Hoffmann
added a comment - Agreed, as we mature our Agile environments, this is really needed.
-
- Support can you provide an update on this? Please and thank you!
Janene Hoffmann
added a comment - Agreed, as we mature our Agile environments, this is really needed.
Support can you provide an update on this? Please and thank you!
Brian Hayes
added a comment - This is still a very significant pain point for us in using this software. It is not possible to use this tool for load balancing during sprint planning. Could we get a comment as to if this is something that we can expect a fix for some day? Or can we assume we will never be able to use JIRA for all of our sprint planning work?
Brian Hayes
added a comment - This is still a very significant pain point for us in using this software. It is not possible to use this tool for load balancing during sprint planning. Could we get a comment as to if this is something that we can expect a fix for some day? Or can we assume we will never be able to use JIRA for all of our sprint planning work? Is there any update on this item? This is a huge problem for us. Not being able to see the total estimate on the plan board forces me to manually add up time which is very time consuming.
Joseph Narai
added a comment - Could someone from atlassian tell us if this is going to be fixed please?
The simple fact that when planning, the parent story has a blank estimate field makes it useless... it's particularly frustrating, since everywhere else in JIRA the estimated time for a story always includes it's subtasks.
Please make it consistent!
Joseph Narai
added a comment - Could someone from atlassian tell us if this is going to be fixed please?
The simple fact that when planning, the parent story has a blank estimate field makes it useless... it's particularly frustrating, since everywhere else in JIRA the estimated time for a story always includes it's subtasks.
Please make it consistent! 
Maxym Mykhalchuk
added a comment - Still in JIRA Agile 6.3.4 the sum of original estimates is not shown for each individual story.
The sum of original estimates is visible in a bar below, but not in each of the story.
Do you think it's a separate issue?
Or may you please reopen this one
Best,
Maxym
Maxym Mykhalchuk
added a comment - Still in JIRA Agile 6.3.4 the sum of original estimates is not shown for each individual story.
The sum of original estimates is visible in a bar below, but not in each of the story.
Do you think it's a separate issue?
Or may you please reopen this one
Best,
Maxym 
It's 2018 and this remains broken. Nice work