It seems that reports in Agile boards do not contain any sub-tasks. My Scrum team uses Story and Sub-tasks, and I would like to include data of Sub-tasks in the Sprint Report and burndown chart. Where can I change the setting?
OMG, story points are not used for sub-tasks. It is conceptually wrong, AFAIK.
Story points is always with a 'Story'. If you want to track the burn down of sub-tasks, use the time tracking in board configuration.
So it goes like this, IMHO
Did I sound a bit rude in my previous comment? If yes, sorry!
If you are looking at including sub-tasks data estimated as story points I guess the answer answer is No, you can't do it.
If you are looking at including sub-tasks based on time estimation the answer is Yes, it can be done.
I too am finding sub-tasks AMAZING to use during a sprint, but VERY VERY hard to report on. I'm not sure why JIRA makes it so hard!!
Our team switched from Story Points to Time Estimation so that sub-tasks would burn down.
As you can see, the burn down chart DOES works with sub-tasks (it's the only report that does):
SS 2016-08-08 at 6.15.17 PM.png
Notice it says, "112h" at the top of the burn down.
Then, if you switch the Velocity Chart, it says the total Committed was only 3d 5h??
SS 2016-08-08 at 6.14.45 PM.png
When Sprint planning, the Workload report DOES NOT include sub-tasks, even though I'm telling JIRA to:
SS 2016-08-08 at 6.20.53 PM.png
Is there some magic setting in JIRA to just make all reports work with sub-tasks?
We really like sub-tasks because they stay attached to the story as you move the story around.
We have thought about changing to just using TASKS and linking to stories.... This would fix the reports, but then actually keeping track of all those tasks would be impossible.
How do other people do this? This seems so broken to me! Has anyone fixed this?
I would also like to understand how I can have sub-tasks included in all of my reports.
Currently it seems that no reports will include data located in sub entitites such as stories in an Epic or sub-tasks in a Story.
This of course results in a reporting machinery that is next to unusable by me and my organization.
We have rough estimates in Stories while they are in the backlog and once they are handled on a sprint palnning meeting and brooken down into sub-task (with sub-tasks given an estimate) the top story is ZEROED out.
Every team in the world is unique, and so Atlassian believes that each and every team's best way of working needs to be molded to their unique circumstances – ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot