• Community
  • Questions
  • Agile board: how to change report setting to include sub-tasks data?

Agile board: how to change report setting to include sub-tasks data?


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?



4 answers

1 accepted

0 vote
Renjith Pillai Community Champion Jan 10, 2013

It ofcourse uses the estimates from the sub-tasks. What is the option you have selected that you have done in the 'Estimation' tab while configuring the board?

Hi Renjith,

Thank you for your quick respond.

I selected:

Estimate Statistic -- Original Time Estimate

Time Trancking -- Remaining Estimate and Time Spent


Renjith Pillai Community Champion Jan 10, 2013

Are you estimating the values at the story level as well? I just did a test based on a couple of stories and with sub-tasks with estimates and I am able to see the burndown summing up the sub-task estimates.

Which version of GH?

No, we don't estimate at story leve. We add estimation to sub-tasks only. We use story as a place holder.

GH version: Atlassian GreenHopper - 6.1-rc1

Renjith Pillai Community Champion Jan 10, 2013

Sorry for my earlier question, missed the fact that you are OnDemand. Can you post a screenshot of the burndown and a couple of sub-tasks, if possible?

I attached a screenshot of last sprint.

As you see, it listed only Story as completed issues. No sub-tasks.

Renjith Pillai Community Champion Jan 16, 2013

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

  • The story points are estimated at a story level for velocity and release planning
  • Sub-tasks are estimated by the team during sprint planning and the burndown monitored to check how they go with the sprint (again by the team, no managers involved :)
  • End of sprint, when the story is closed, the velocity will reflect the total of the story points.

I understand what story points are for. We are not using story points. I am not looking for getting velociy based in story points. I simply wanted to includ sub-tasks data in sprint release. I guess I cannot to configure to do that?

Renjith Pillai Community Champion Jan 16, 2013

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.

Be warned sub-tasks are not reflected in Epic reports or Release Reports

Suggest an answer

Log in or Join to answer
Community showcase
Jason Wong
Published Tuesday in Agility Beta

Welcome to agility

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  – ...

408 views 6 16
Read article

Atlassian User Groups

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!

Find my local user group

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

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot