nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

How to include sub-task in Jira sprint report?

Dror Bernstein

Hi,

I'm working with sprint report in order to analyze our preformances and work ration.

I noticed that sub-tasks are not included in this report.

Most of our developement tasks are actually sub tasks and it's super important to include them in my report.

How can I add them to the sprint report?

Thanks!

Accepted answers

All comments

Walter Buggenhout

Hi @Dror Bernstein,

You can't, unfortunately. Tracking work in JIRA is based on standard tasks (issues) and not subtasks. There is a lot of questions and discussion around this topic on the community, e.g. this thread has some interesting background reading around the topic.

A common scenario is to use Epics and Stories / Tasks rather than tasks and subtasks.

Dror Bernstein

Thanks Walter!

Is there aggreegation of subtasks estimations into tasks?

I want to investigate our prodactivity level by comparing sprint estimations vs. actual. Since we are breaking the tasks into sub tasks I want to make sure I can get all my team spent time somehow.

unknown

The problem is that one must MANUALLY associate "Tasks" to Stories.

If Jira is going to carry around SubTask as the auto-association unit, then in the Burn-down/Burn-Up reports rather than just Stories, and Issues, it should also include "Sub-Tasks", because if one MANUALLY associates "Task" to "Story" and shows the Burn-up (for example), and switches to "Issues" it shows the resultant completed work items.

This is what everyone is trying to achieve. If Jira would simply DITCH this wonky association and recognize that

SUB-TASK <==> TASK

Then a lot more humans would be happier.

Anyone at Atlassian actually listening to these threads?

Artem Drobotenko

UP!
That is still a 100500% valid concern!
Why on Earth sub-tasks exist, if they are not counted in as issues and pieces of work that have time spent on them?!
Angry...

Perkuto Tech

I agree 100%. Stories end up being too big of a chunk and all get moved to "done" in the last week of our sprints.

We ended up breaking it down into subtasks so we can see/track progress on a daily and weekly basis.

I was very disappointed to see how "loose" the integration between tasks and subtasks have been developed - ignoring subtask points in planning and reporting.

Jira is useless when it comes to tracking progress of our sprints.

Roberts Čāčus - eazyBI

Hi @Dror Bernstein ,

I suspect the problem is tied to the fact that sub-tasks themselves are not tied to the Sprints. Instead, they get the connection through their parent issues.

While I can't suggest a solution for the default Jira Sprint reports, you may want to look at third-party options. For example, the eazyBI Sprint reports will also take into account work logged in sub-tasks. You can observe one such example in a Sprint burn-down report from our Demo account - https://eazybi.com/accounts/1000/cubes/Issues/reports/144076-time-tracking-burndown-in-selected-sprint. Adding the Issue Type dimension to the report pages and selecting the "Sub-task" type will reveal work logged for some Sprints.

See other Sprint related reports here - https://eazybi.com/accounts/1000/dashboards/5956-sprints-overview.

Best,

Roberts // support@eazybi.com

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

sub-task

sprint-report