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

JQL Filter for sprint not working for next gen subtasks

What I want to do:

Have scrum board in next gen project to show the stories of the current sprint in correct priority order with "group by subtasks" option activated.

First insight:

There is a bug saying this is currently not working:
As a workaround it is suggested to create a Classic board and edit its filter to return the next-gen issues.

Workaround - still not working: 

I created a classic board and set the filter to “project = my_project AND Sprint = current_sprint”. Stories and bugs are correctly shown, but the subtasks do not show up. If I filter for “project = my_project", stories, bugs and subtasks are shown. The current_sprint is correctly set in the subtasks.


JQL query “project = my_project" correctly filters stories, bugs and subtasks

JQL query “project = my_project AND sprint = current_sprint" (my_project being a next gen project) correctly filters stories and bugs but does NOT show any subtasks altough subtasks are correctly assigned to the sprint. 

Why is that and what can I do to fix it?
See "What I want to do" section for what I really trying to achieve, so if there is other ways to get there I am also happy.





9 answers

@Ivan Teong  - is there an ETA on the above?

I am becoming extremely disillusioned with the next gen projects. The product is not ready for production release. There are so many simple basic bugs that just don't work.

Like # people like this

I'm having a similar problem. The moment I use 'Sprint' in my JQL query no subtasks show up anymore, even though they have a sprint assigned.

Im having the same issue.  Is there a suggested workaround or any indication when it will be resolved?

Agreed. Turning on the Sprint filter immediately causes all subtasks to not appear if querying a NextGen project.

Like Nathanael Kevin likes this

Having the same issue. Any workaround?

Yes facing same issue. It will be really helpful if there is any way to have sprint and subtask filter combination work in ISSUES section. 

Even am facing issue for the next gen project.

If the project is classic and if we filter by Sprint, we do get Sub Tasks in it. But not with next gen project.


One way to use the filter for tracking is to export as csv or excel and then use it further for filtering manually.

Confirmed, same issue here too. 

Same issue here! Please fix your product Atlassian!

We are having the same issue. No subtaks show up when filtered on current sprint. Really disappointing. 

Like Bilal.Shuja likes this

Same issue here. I've created a support ticket. 

I'm facing a lot of backlash with project managers in regards to this exact problem after having setup using Next Gen...

Please can we get an update and fix for this issue, as it's very problematic!

This is really frustrating and is happening for me too.. so annoying as our group uses subtasks for each developer and I use another tool to total all the sub tasks BUT it relies on the jql query to work.. which it's not.. seriously annoying

C'mon guys, I migrated the entire org to nextgen and keep discovering really simple stuff that seems to have been missed out! Can atlassian let us know if the filter for sub tasks via sprint value is going to be added to the nextgen issue filter or not?

Atlassian it's been years now since this was reported and still, it's not fixed.

This is not the service we were expecting from you :(

Now, I agree with my company's move "Octane" from Jira.

any update for this bug ???

0 votes
Yi Jie Chuah
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
Apr 04, 2023

A "maybe" workaround is to use the created at/ updated at dates I guess. However, this is pretty unreliable and does not always work.

I don't understand why it's difficult to even give an UPDATE on this issue. If the bug is difficult to fix, at least give an ETA or SOME kind of announcement. There is NOTHING in this thread from the Atlassian team.

There is nothing "next-gen" about these projects, they are chalk full of bugs and I am EXTREMELY dissatisfied with this service.

Should've listened to my team and went for notion instead. That platform isn't even really build for project management primarily but at least that it has filters that work and a team that cares about its userbase :))))

Same as above "any update for this bug ???"

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events