Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Workflow Transition: Trigger a workflow trough a workflow in an other project

Brian March 5, 2021

Hello dear community,
I am currently working on a project and can't get any further...

We have over 30 Jira projects on our server and now we want two of these projects to work together.

So we have project A (Scrum development project for our app) and project B (ServiceDesk).
In project A we have a workflow with the statuses: To Do, In Progress, User Testing & Done.

In Project B we have a different workflow with the statuses: Request Under Review, In Development, In Progress, Review, User Testing, Reply to Customer & Closed.

  • When a request is made in Project B, Jira automatically clones that request and creates a task in Project A's backlog. (The two issues are linked)

Now we want that if the task in Project A changes to the status "User Testing", then also the linked request in Project B changes to the status "User Testing".

I have already tested all the workflow post functions and checked the automations but have not found any possibility. Now my question: Is there a way to realize this requirement? Can we trigger a specific issue with a different workflow in different project?

 

Thank you verry much!

1 answer

1 vote
Jack Brickey
Community Champion
March 5, 2021

you are going to need to leverage a scripting (e.g. Scriptrunner, Power Scripts, etc) or automation (e.g. Automation for Jira) addon app for this.

Brian March 5, 2021

Hi Jack. We have Automation for Jira but i couldn't find a way to manage this...

How can we do it?

Like Brian Trepto likes this
Jack Brickey
Community Champion
March 5, 2021

Disclaimer - I am on cloud so your options could be different.

where exactly are you stuck? what do you have in place at this moment. please share and I can provide more precise feedback. I would suggest you look to the Branching function in Automation and Related Issues. Please see this document - working-with-related-issues 

basically, i think you will be looking at something like this....

project A rule

trigger - issue transitioned

conditions - those that make sense for when you want the action to happen/not happen in Project B

Branch rule - for the linked issue

action - transition issue according to the trigger issue status

Suggest an answer

Log in or Sign up to answer