Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

We want to create a “Quick Filters” that show’s subtasks assigned to a current user. Edited

Hello Team,

We want to create a “Quick Filters” that show’s subtasks assigned to a current user in Project.

We are trying to create quick filter shown below in board configuration but it doesn't work

issuetype = Sub-task AND assignee = currentUser()


issuetype in subTaskIssueTypes() AND assignee = currentUser()

Please let me know how to apply this filter on the scrum board or any other changes need to be done in board configuration? 







2 answers


I think I found a way to filter in backlog view  according to sub-task assignee, I've used:  or issueFunction in parentsOf("assignee = IRINA") and saw dev stories in backlog view where IRINA is an assignee of a sub-task and not necessarily assignee of the dev story.

Not sure if that is exactly what was required in your question.

0 votes

Your second JQL line is correct, so you should be able to simply go to board configuration -> quick filters and add it into a new line.

If you've done that and it "does not work", then you will need to explain what you mean by "does not work" - what do you expect it to do, and what does it actually do?  (As your JQL is correct, I suspect the problem will be a misunderstanding of what quick filters are for rather than a filter that does not return the right results)

Thanks for the reply Nic!

I tried the second JQL & it works fine only in the active sprint. In the backlog view I am unable to see the subtask within the story which are assigned to current user.

Please elaborate why those subtask are invisible in backlog view on the scrum board?


Subtasks are irrelevant in the backlog, it's complete nonsense to rank them outside their stories.   So to keep your view of the backlog easier to read and work with during ranking/grooming, Jira hides them from the backlog.

Thank you very much :)

@Nic Brough _Adaptavist_ 

What i realy dont like and dont get is why you believe you can determine what should be relevant or usefull for a user, that just claims a lack of usefulness in the software.

what would be the pain for atlassian to just allow that by a user that wants to see it?

why you are resticting that even if someone is making the effort to write a jql for it?

I also want to create a quick-fliter, where i can see in the Backlog:
- Storys i am the primar or secondary assignee
- Subtasks i am assigned to

And here is the reason why:
- if you believe it or not, people miss-use JIRA an create in the backlog several sprints upfront to plan there project in advance. And yes, this miss-use is highly connected with normal people thinking and some not so uncommon scaled agile frameworks
- so yes, i want to have a look on all the work that i assigned or that someone assigned to me, with no regard if it is signed on the story or subtask level
Question: Would you still tell me, that it is not usefull?

What can i do, that Atlassian will take away the restriction, that subtasks are not shown in the backlog? Do i need to buy the company or become the CEO?  Or can you just get into a more customer workflow oriented mindset?

Sorry to beeing not so nice, but you just act like a lot of the community admins. I think you are told to teach people how to use Jira properly, but you seem to sell a bad functionality as a good one. Thats just useless for the user.

I am not determining anything, I'm explaining why subtasks are not on the backlog - it's not the right place to manage them.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Agile

Join us LIVE: Atlassian & Experts Talk Research & Insights @ Scale

Hello all! What have you learned from your customers lately? Our live-streamed series continues by exploring CX, UX, and the power of research & insights at scale with Leisa Reichelt, Head of R...

249 views 3 6
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you