You might be able to do something with script runner and subtasks. I have found if you have a really well defined workflow this approach could work for you. There are restrictions though like subtasks cannot be broken down further.
There is a linking approach as well but you need a plugin to assist in maintaining your hierarchy like structure or links hierarchy.
For the general case, either method becomes dubious.
I would like to have a main workflow (like a release workflow) and, when development starts, I would like to be able to spawn as many mini-workflows (in lack of a better name) as the number of main components/services. After development for one component is completed, I would like that workflow to re-enter the main release workflow.
For example, in the main workflow I may have requirements gathering & the main architecture and design tasks. When all these release level tasks are done (main/release level workflow), the component level tasks (i.e. component level workflows, or mini-workflows) for detailed design and development need to start then complete for all the individual components identified in the solution architecture. The same solution could be applied for the QA process.
I would like to have the component level workflows re-enter the release level workflow when completed/done.
Is this functionality possible?
I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...
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