You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Hello, I am having a minor issue where I created an automation rule to create subtasks based on specific criteria. In this case, the automation rule works but I was hoping there was a way to not show subtasks as "Open Tickets" As these subtasks fall under a Service Request.
Attached is a photo for reference.
You need to edit the queue's jql filter. Make sure you are doing an advanced search and put "... And issuetype not in (sub-task)
This will remove the subtasks from showing up.
Regards
Yep, @Fabian Lim is spot-on - you need to drop the sub-tasks by adjusting the filter.
But "issuetype not in (sub-task)" might not be the best approach for everyone. If your admins add a new sub-task type, you're going to need to edit the filter to add the new one.
I prefer using a function for this, either
and issuetype not in subtaskissuetypes()
and issuetype in standardissuetypes()
They will continue to work, whatever your admins do to your issue type list! (Epics are considered to be "standard" issue types by those functions). I'm quite fond of using them in board quickfilters and some types of report as well as in general searches.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you everyone for your help
"and issuetype not in subtaskissuetypes()" worked out for me
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.