The Background: Under a single parent issue, we currently have a single "track" of subtasks that automatically occur sequentially (ex: closing "SubTask1" Auto Creates "SubTask2", close that and it Auto creates "SubTask3...") As each subtask closes it auto transitions the Parent Status (which is what actually triggers the creation of the next subtask in the sequence). This works Great
The Goal: We have 2-3 "tracks" of subtasks that need to occur simultaneously under a single parent Issue. So regardless of whats happening with SubTask 1,2,3 (track a) - SubTasks A,B,C (track b) needs to also be created automatically (ex: closing "SubTaskA" Auto Creates "SubTaskB", close that and it Auto creates "SubTaskC...").
The Problem: Currently Subtasks 1,2,3 are being auto created during a transition of the Parent Status. But since Subtask A,B,C can't also update the Parent status (since it must occur independently of 1,2,3) I need SubTaskB to be created under the parent as part of the 'close' post function on the SubTaskA Workflow.
Note: I'm currently using a combination of the Script Runner and MISC JIRA Workflow plugins.
I Found that the Bob Swift Plugin "Create on Transition" Works very well. It lets you assign a post function to a subtask workflow and that post function lets you create another subtask off of the parent when the original subtask is transitioned. It solved my issue.
Atlassian Summit is an excellent opportunity for in-person support, training, and networking.Learn more
Hi, everyone! Molly here from the Jira Service Desk Product Marketing Team :). In the spirit of this month's august-challenge, we're sourcing stories of Jira Service Desk activation fro...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs