Sub-tasks don't show on reports

[raconceicao]

Why don't sub-tasks show up on reports? it would be useful since there are teams that use more sub-tasks than others, and if their not included, it's harder to do a good comparisson between projects for example. Also, it would give a more exact tracking of the project.

[Nic Brough -Adaptavist- · Accepted solution]

They will, where they are appropriate.

Which reports are you finding them missing from?  What are the reports for and why would sub-tasks be useful to include?

[raconceicao]

For example, in the sprint report they might be helpful. But even then, it would be helpful to know clearly when they are being counted or not. For example, I know that they are counted in the cumulative chart because supposedly they are, and someone said it in a forum. But it's not transparent enough.

I think in general the reports could have more info and be more flexible, like say the exact number of completed issues in a specific date, instead of you needing to go with the mouse and put it on top of a tiny circle (example of the created vs resolved).

In general it could be better, more flexible and more transparent, but we work with what we have ahaha.

[Nic Brough -Adaptavist-]

Ok, you need to be clear on what a sub-task is - it is a part of its parent issue, not an issue its own right.

They do not appear in sprint reports because they are not sprintable items, they are irrelevant.  The sprint items are the stories you commit too, not fragments (sub-tasks) of a story.

The cumulative flow charts do include them because they're looking at numbers, not sprint estimates.

[raconceicao]

Hm ok, still they should be relevant. If tasks are relevant, sub tasks (that are very similar to tasks) should also be relevant and included. I see subtasks as tasks that are easily associated to a story.

[Nic Brough -Adaptavist-]

They are relevant, when you're looking at the story of which they are part.

Sub-tasks are not relevant to a sprint, they are not sprintable items, they are a part of their parent story.  It's nonsense to do sprint or velocity reporting on them as anything other than as a part of the story.

[raconceicao]

But makes sense to track that a portion of the parent Story has been complete.
Also, can't sub tasks be deliverables?

[Nic Brough -Adaptavist-]

No, it does not, not in terms of the sprint.

Again, you commit to doing a whole story, not bits of it.  That's what all the sprint reports are looking at - commitment vs delivery.

Sub-tasks certainly are deliverable.  They're a deliverable part of a story.  If you want to look at them and measure their progress, that's fine, but it doesn't make sense to do so outside their parent.

So, sub-tasks are utterly irrelevant to the sprint, as only the stories matter to the sprint.  So there's no reason to bother reporting anything on them in sprint reports.

[raconceicao]

Thanks Nic :D
It makes sense now

[Suvradip Paul]

Hi @raconceicao ,

Thanks for posting and welcome to the community.

Could you please share the report you are looking in this case?

Cheers

Suvradip

[raconceicao]

Same as I wrote Nic.

Do you know which ones include sub tasks and which don't ?
If you do, I'd ask you to share with us. I think it could be helpful for other members of the community that are not sure about this matter.

[Suvradip Paul]

@raconceicao  - I would suggest you go through this Sprint Report Documentation - https://support.atlassian.com/jira-software-cloud/docs/view-and-understand-the-sprint-report/ which helps you to understand whether a team is committing more or there are scope creeps.

I would suggest go through the Understanding Report in the above documentation.

Please let me know if that helps or you are looking for anything else.