-
Bug
-
Resolution: Duplicate
-
Low (View bug fix roadmap)
-
None
-
None
-
None
-
None
Our Product Owner at Widespace usually looks at the Burndown Chart to keep track of the progress of the sprint. When we have few but large Stories or Issues, it becomes hard to see the progress being made, since the values are only decremented when the whole task is completed.
We try to split the tasks up with several sub-tasks, and complete those as we make progress. However, these sub-tasks don't contribute to the red line on the Burndown Chart. Shouldn't they? If not, how do you recommend we structure our issues to better keep track of their progress through the Burndown Chart?
(As an aside, it was really hard to report this issue. I have an account through the company, but I couldn't seem to report an issue from there. I had to create a new account, just to do that.)
- is duplicated by
-
JSWSERVER-6007 Burndown chart doesn't take under consideration the sub-tasks estimation
- Gathering Interest
Hi oskar.segersvard,
Unfortunately this is only supported with time based statistics by enabling 'Time Tracking' in the estimation configuration for the board. You might like to try using Time Tracking but having 1 hour = 1 point, this will achieve what you're looking for.
Other option, is instead of using Story and Sub-tasks, you could try mapping the parent issue to an Epic issue type and the smaller tasks to Stories. This way you can also get reports to even track the progress of the Epic.
Regards,
JIRA Agile Team.