-
Suggestion
-
Resolution: Unresolved
-
None
-
None
-
2
-
8
-
We only add estimates to subtasks, and not to both subtasks and parent tasks (stories.) This helps us avoid double counting of issue totals on Jira reports and pages. Unfortunately, there isn't a good way to group changes outside of an issue type such as epics or subtasks.
The Jira issue page has an option to include subtasks when seeing the original estimate. This would be helpful on the Details View while using the Agile boards. My stories with subtask estimates are showing 0 under the Estimate field; however, they are showing xx hours under the Remaining field. So, it's misleading that the "Estimate" field only shows the estimate for the main task or story; however, the "Remaining" shows the total remaining for subtasks as well.
- duplicates
-
JSWSERVER-5471 Parent issue without estimate should provide its subtasks estimates in rapid board plan mode
- Gathering Interest
- is related to
-
JSWSERVER-11225 JIRA Agile should add the original time estimate of the subtasks included in a parent issue
- Closed
Form Name |
---|
I am a new user to Jira and find it very frustrating that I cannot have my subtasks burn down. For instance, if I have an issue worth 10 points and I have development time of 3 points and Dev QA of 1 point that are complete, I should be able to see that time burned down. The original point value should burn down as subtasks are completed. The timeline will still reflect the number of points started with and also the accurate burndown. In this instance there are 4 points yet to go but they are not related to the initial coding or qa efforts. My burndowns are not an accurate reflection of what my team is working on or has completed. It seems that this has been a problem for a long time and it would be nice if it could be resolved. Right now I have to have every step in the process designated as an issue if I am to have an accurate burndown,. Needless to say, that makes my backlog look HUGE! Not to mention unreadable.