-
Bug
-
Resolution: Timed out
-
Low (View bug fix roadmap)
-
None
-
6.3.4
-
None
-
6.03
-
Severity 3 - Minor
-
We are using rapid board (SCRUM option) to control our sprints.
Instead of using story points, we've decided to use original estimate as the base (effort) for our burndown. However, the original estimate is not directly defined on the stories. Instead of that, we detail our stories in subtasks, we inform the original estimate (effort) for all the subtasks and, after that, JIRA just INDIRECTLY accumulates the sum of its subtasks as the story's original estimate.
The problem is (please see screenshots attached):
- Scrum Board (Plan mode) does not show the sum of estimated hours on the respective spot.
- Due that, Scrum Board (Report mode) - Velocity Chart - also does not show the chart with the information registered. The bar chart demonstrates no information, because it does not recognize the amount of hours (remaining / registered) on subtasks.
After a quick test, I've discovered:
- The features mentioned above ONLY WORKS if the hour estimates (original time estimate) were informed DIRECTLY on the stories. It means, a story WITH NO subtasks.
In short, this situation does not fit for us. We really need to decompose our stories in subtasks and, after that, simply let the scrum rapid board (no matter the mode [plan | work | report]) do its job.
Finally, if you need more information, please just let a comment.
Thanks!
- duplicates
-
-
- Closed
-
- is cloned from
-
-
- Closed
-
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JSWSERVER-10174] Scrum Board does not show sum of Estimated Hours when Stories have sub-tasks
This bug is still relevant to my needs.
Honestly, I don't understand how people use sub-tasks without it. Or rather, I imagine they use them a lot like I do: manually totaling up a bunch of sub-issues, or eschewing them altogether for epics.
This is such a basic feature that I was expecting this would be solved already. Without it, issues with a breakdown (sub-tasks) will not display the issue estimate when displayed in a board.
@JIRA, which alternative do you propose?
@ALL, please comment - see Hoand Dong comment above.
I still need this. I was assuming it would be a natural feature that would be added.
Many thanks for raising this bug. Since there has not been any customer activity on this issue in over a year, we’re closing it as Timed out.
If you feel that the bug is still relevant to your needs, please leave a comment and we'll reassess it.
Kind regards,
Dong Hoang
JIRA Software
Hey Rene, thanks a lot for the information. I'll check it out and verify if it fits for my needs.
Thanks again. Best,
Michel
Rene Rath
added a comment - Michel, I had a similar challenge and found a solution, which didn't exactly fit what I needed, but seems to fit perfectly for your use case:
https://answers.atlassian.com/questions/84349/rapid-board-time-estimates-with-sub-tasks?sort=votes&page=2
here - rather towards the end of the page - Ubisoft posted a neat little script, which adds a button to the agile board in order to see the sum of the time estimates of sub-tasks. Hope it helps.
Rene Rath
added a comment - Michel, I had a similar challenge and found a solution, which didn't exactly fit what I needed, but seems to fit perfectly for your use case:
https://answers.atlassian.com/questions/84349/rapid-board-time-estimates-with-sub-tasks?sort=votes&page=2
here - rather towards the end of the page - Ubisoft posted a neat little script, which adds a button to the agile board in order to see the sum of the time estimates of sub-tasks. Hope it helps. 
Michel Barros
added a comment - I've cloned this issue because I didn't agree with the previous qualification from Atlassian.
Please consider, at least to move the issue (registered as a BUG) to a Story. But please don't set the issue as resolved.
Thanks,
Michel
Michel Barros
added a comment - I've cloned this issue because I didn't agree with the previous qualification from Atlassian.
Please consider, at least to move the issue (registered as a BUG) to a Story. But please don't set the issue as resolved.
Thanks,
Michel 
Still relevant for me too!