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

 

4 answers

1 accepted

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

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

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. 

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?

Suggest an answer

Log in or Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

3,253 views 14 20
Join discussion

Atlassian User Groups

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!

Find my local user group

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

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot