Transition an issue from another project using an automation

[Nicolas Gomez]

Hi all! Previously I made an automation that clones an issue (ISSUE-1) from project "A" to project "B" when the aforementioned issue is transitioned to a particular status. So I have:

• PROJECT A -> ISSUE 1
• PROJECT B -> CLONE - ISSUE1

Well, now I need to create another automation to transition that cloned issue (CLONE - ISSUE1) to another status when the ISSUE1 is transitioned. Both destination status have different names. I tried with the "Transition Issue" task but this is not useful for me.

Is this possible? How?

Thanks

[John Funk]

Hi Nicolas - Welcome to the Atlassian Community!

Does your first automation rule link the two issues after the second one is cloned? And if so, what is the link type? 

[Nicolas Gomez]

Yes! At the moment of cloning the ticket I set the field "Linked Issues" with the Values "Cloned by" and "Trigger Issue". This actions links both tickets. So the link is performed at the moment of cloning the ticket

[John Funk]

Can you post what you have for the second rule so far? 

[Stefan Salzl]

Hi @Nicolas Gomez and welcome to the community,

Could you please share a screenshot of your rule? I´m not quite sure if I can follow correctly especially when we talk about "transition" which is a main part of workflows and status.

As far as I understood correctly it´s about the name of the issue after the clone.

Please corret me if I´m wrong and if possible please provide some screenshots that describe your problem.

Best
Stefan

[Nicolas Gomez]

This is the first automation. Only in charge of cloning an linking the tickets

Now, I want to create another automation to "sync" the status between this cloned tickets (Different projects, transitions and statuses). For instance, if the cloned ticket is moved (transitioned) to the status X of that project, I want this action triggers a status change in the original ticket (To the status Y, remember that both projects have different structures)

[Stefan Salzl]

Hi @Nicolas Gomez 

The following rule is an example of what I guess your requirement is about. 

In my case the previous rule cloned an issue from project JT to project CC and setting the issue link (like in your screenshot).

Whenever (in my case issue type bug) issue in project JT is transitioned from "selected to development" to "Done" the branch checks if there is a linked issue of type "clones" in the trigger issue. If so the transition for that linked issue will be done.

Hope this was helpful. Please let us know if you have any further questions.

Best
Stefan

[Domi]

Hi Stefan,

I'm currently trying to set the rule you have suggested here so that when an issue is transitioned in one project, it also transitions the linked issue in the other project.

It's not working at the moment, and I wanted to pick your brain on what might be the reason:

• In your screenshot there are 2 different projects under "Rules restricted to projects". I'm unable to add the second project there, it's not letting me do it. Would the problem be that the automation rule is set between 2 different team-managed projects (one of them is a software project and the other a business project).
• The issue to be transitioned in the receiving project has a "strict" workflow built in. Could it be causing issues when this automation rule is trying to run? And, the workflow in the sending and receiving projects aren't exactly the same. Is that a problem?

Thanks in advance for your help,

Domi