Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Issue filter "Sprint" filters all subtask issues

On the issue navigator > advanced issue search i can filter by different fields. 

Filtering by status (e.g. 'in progress') returns all issues in said status. Correct

Filtering by Sprint, returns only all non subtask issues, regardless whether i also filter for issue type and include all kinds of tasks. And yes, the subtasks are also assigned the same sprint.

(for the sake of completion: the second bug issue in the screenshot a does not have a sprint assigned, so that's fine)

1. Is there a way i can actually filter by sprint and not also filtering subtasks? 
2. Why does the sprint filter do that? 

Thanks in advance. 



Without "sprint" filter



With "sprint" filter



2 answers

Our sub-tasks do have a 'sprint' field. And that particular sub task i am missing, when using filter as mentioned above, has this field, and the correct sprint selected. 

That's why i am confused.  (; 

I actually believe this is a bug, since i can see all of the issues in this list, including the one i was missing when setting the filter. Once i apply the filter, it's gone. 

0 votes
Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Jun 09, 2022

This happens because sprints are handled by having a sprint field on the issues.

Sub-tasks are not sprint items themselves, they are a piece of their parent issue.  Because of that, they do not have a sprint field.

There's an argument that you don't care what sub-tasks are on issues when you're reporting on a sprint, but I'm not convinced.

This is a flaw in the reporting in Jira, I think you should be able to search for issues by sprint, although the sprint field in a sub-task would have to be a lookup to what sprint(s) the parent issue is in.  That's how I do it with scripted fields anyway.

Thanks for the reply. 
Put this aside at first, and tried to manage without the filtering. Managing the management tool. 

Anyways, the sub-tasks do have a sprint field.

I agree.
And i honestly don't care what needs to happen in the background for jira to get all issues, regardless of type (lookups).
I expect a filter to be self-explanatory, and not filtering more than the name would suggest. Let the user decide by adding more filters like `Type`, which actually exists... 
(Same goes for the board view: "Group by: `None`" -> all the subtasks are gone.. )

I hoped being able to avoid wasting time to get into SQL JQL, but since i don't see any movement also on other issues from Atlassian, i don't think there's another choice. 

Thanks again! 

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events