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; } } }

Creating a filtered view that shows ALL issues in active sprint including subtasks.

Xenia Chilkowich

I've gone round and round on this. No matter what filters I apply to a list view, I cannot create a comprehensive filter that includes ALL issue types (including subtasks) in active sprints. I do not want to rely on the board because in order to see subtasks, I have to group by subtask and then I cannot see items by assignee. I have argued with Rovo for 30 minutes now and still see no solution to this. Rovo kept suggesting features that do not exist and are not available for me. I am in a team managed space. I don't not want to see this on a board, I want a filter that I can view with the team and export as needed. Why are subtasks not considered more consequential in all of this?

Accepted answers

All comments

Arkadiusz Wroblewski

Hello

probably that apply to this limitation

https://jira.atlassian.com/browse/JRACLOUD-81069

best,

Arek 🤠

Gabriela - LeanZero

Hi Xenia,

The ticket Arek linked is the reason you've been going in circles, and it isn't anything you're doing wrong. In a team-managed space the subtasks show the parent's sprint on the issue, but sprint JQL doesn't match on that value, so sprint in openSprints() only returns the parents. I reproduced it on a test site today, and the same query in a company-managed space did return the subtasks. That also explains why a lot of the advice you'll find doesn't fit your setup.

What I'd try, in this order. The exact option is project = KEY AND (sprint in openSprints() OR parent in (KEY-1, KEY-2, KEY-3)) with your space key and the parent keys from the current sprint, which gives you the stories and all their subtasks in one filter you can save and export, though you'll have to update the keys each sprint. The one people post on the ticket, project = KEY AND (sprint in openSprints() OR issuetype in subTaskIssueTypes()), needs no upkeep but also pulls in subtasks of backlog items that aren't in any sprint. Others on the ticket use an automation rule that copies the parent's sprint into a label or field on each subtask and filter on that, which I haven't tested myself.

Atlassian's last note says there are no immediate plans to fix it, so a vote on JRACLOUD-81069 still helps. Would the parent-key version work for how often your sprints change?

Wali Khan

Thanks for breaking this down. The parent-key approach could work for now, though updating the keys every sprint would get a bit tedious.

Gabriela - LeanZero

Hey @Wali Khan, yes, the keys are the annoying part, and I'd feel the same after a couple of sprints.

The automation route is the one that takes that upkeep away, because you'd label the work instead of listing it. Two rules, set up once. You'd set up one rule on Sprint started that branches over the stories in the sprint and then over their subtasks, adding a fixed label such as active-sprint, and a second rule on Sprint completed that removes the same label again. That way the filter stays the same from sprint to sprint: project = KEY AND (sprint in openSprints() OR labels = active-sprint).

I haven't built this pair on a team-managed space myself, so I'd try it on one small sprint first and check that the label really lands on the subtasks before you rely on it. Would that fit how your team starts and closes sprints?

Josh

You’re running into a native JQL limitation rather than a bad filter. In team-managed projects, the Sprint value on a sub-task is inherited from its parent, but sprint JQL commonly returns the parent work items—not a flat sub-task result (see JRACLOUD-90898).

For the parent list/export, use something like:
project = ABC AND sprint in openSprints() AND issuetype in standardWorkTypes()

Jira does not support a subquery that feeds those parent keys into a second `parent in (...)` clause. If you need a flat sub-task export, run the parent filter first, copy the returned keys, then query `parent in (ABC-1, ABC-2, ...)` (or expand the parents/subtasks in the CSV/REST export). The board’s nesting is the native convenient view, but it cannot produce that flat List result automatically.

Is the project team-managed in the same way as the question, and do you need a flat sub-task list or a parent-plus-subtask export?

Ivan Manolov _Appfire_

Hi @Xenia Chilkowich,

No filter you tried could have worked. In team-managed spaces a sub-task inherits its parent's sprint, but sprint in openSprints() doesn't match that inherited value, so every workaround has to mark the sub-tasks some other way. For what you describe (one filter, viewed by assignee, shared with the team, exportable), I'd put the pieces together like this:

Set up the automation pair @Gabriela Perdum outlined, so sub-tasks get a label such as active-sprint when the sprint starts and lose it when it completes. Try it on one sprint first.
Save this search as a filter:
project = KEY AND (sprint in openSprints() OR labels = active-sprint) ORDER BY assignee ASC
Sorting by assignee keeps each person's work together without relying on the board.
Share the filter with your space or a group from the Filters page, so the team opens the same view.
Export from the search results (••• > Export > Excel CSV) whenever you need a copy.

If automation isn't an option, this version needs no upkeep at all:

project = KEY AND (sprint in openSprints() OR workType in subtaskWorkTypes()) AND statusCategory != Done

The trade-off is that it also pulls in open sub-tasks of backlog items that aren't in the sprint.

Hope that helps,
Ivan

Ivan Manolov _Appfire_

@Xenia Chilkowich, in case the label rules turn out to be more upkeep than they're worth, there's also a route with no automation at all.

If you're open to using an app from the Atlassian Marketplace, JXL for Jira can help with this. Specifically, filtering on its Sprint column picks up sub-tasks by the sprint they inherit from their parent, in team-managed spaces too. One sheet scoped to your space then covers everything in the active sprint, and you can:

group the rows by assignee, or switch on the hierarchy to see each sub-task under its story
share the sheet with your team
export it whenever you need a copy

Sub-task sprints in a team-managed space in JXL

Full disclosure, I work on the team behind JXL.

All the best,
Ivan

Danut M _StonikByte_

Hi @Xenia Chilkowich,

Unfortunately, it is currently not possible to filter sub-tasks from team-managed projects by sprint due to this Jira bug/limitation: JRACLOUD-81069. Please consider voting for this issue in the hope that Atlassian will address it soon.

As an alternative, you can use Jira’s Sprint Report to view all issues included in a sprint, including sub-tasks.

Another option is to use an app from the Atlassian Marketplace. If you’re open to trying one, you can visualize the issues from a sprint directly on a Jira dashboard using some of the gadgets provided by our Great Gadgets app:

Work Breakdown Structure (WBS) gadget can display the issues from a sprint, along with the sub-tasks, in a tree structure list view like this. All you have to do is to select the sprint as the Data Source.

Team Wallboard gadget - can display the issues from a sprint in a board style view. In this example, stories are in green-color and sub-tasks in yellow color. The colors can be customized

The gadget supports swimlanes by multiple criteria: by epic, by story, by priority, by assignee, etc.

Danut.

Welcome!

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

Quick Links

Find more posts tagged with

subtasks