can multiple workflows be linked, i.e. spawning one workflow from inside another and coming back?

[Norman Abramovitz · Accepted solution]

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.

https://jamieechlin.atlassian.net/wiki/display/GRV/Script+Runner

https://marketplace.atlassian.com/plugins/com.almworks.jira.structure

https://marketplace.atlassian.com/plugins/com.docminer.jira.issue-links

https://jamieechlin.atlassian.net/wiki/display/GRV/Built-In+Scripts#Built-InScripts-Createasub-task

https://jamieechlin.atlassian.net/wiki/display/GRV/Built-In+Scripts#Built-InScripts-Clonesanissueandlinks

https://jamieechlin.atlassian.net/wiki/display/GRV/Built-In+Scripts#Built-InScripts-Transitionparentwhenallsubtasksareresolved

[Daniela Deaconu]

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?

[Philippe Aubin]

Can you explain what you need to do exactly because it's possible for 2 workflows to share some information.

For exemple:

An issues that automaticly create subtask, then the subtask copy some fields in the parent when it is closed. 

[Norman Abramovitz]

Not that I am aware of.   Workflows are tied to issue types.   Whenever I needed to 'link' workflows I needed to build them monolithically