I'm trying to use automation to create subtasks when an issue of a certain type is created, but I'd rather it doesn't inflate the ticket counter and I definitely don't want the tasks to muddle the look of the overall queue and bury the parent issues in a mountain of sub-tasks.
What would be the best way to fix it? If there's no way around the ticket counter that's fine.
You can create a separate queue just for the sub-tasks and then in your other queue just update the filter to exclude subtasks by adding this to it:
issuetype != Sub-task
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Taylor Chappell ,
if you don't want subtasks within your queues, then you simply need to edit the queues to exclude subtasks. You can simply add AND type != subtask. I would also recommend ensuring that any SLAs do not consider subtasks. Although I'm not exactly sure how you're using subtasks within your JSM project.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The subtasks are basically the broken-down components of the grander task. Something akin to "Build a deck" is the parent task and subtasks would be "Buy wood, buy nails, charge tool batteries" and so on that will eventually culminate in the parent task being entirely done.
But if you're building a lot of decks, all of a sudden you have 40+ tasks but only 4 parent tasks and it's annoying.
I'm trying to find where I edit the queues, but I can't seem to track it down.
EDIT: Locked it down. Sorry. Recently had the world of Jira opened up to 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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.