How can I set up a multi-step automation rule to create a new ticket AND link the tickets together?

[Kyra Mayock]

Hi there - looking for some guidance on how to set up a multi-step automation rule for a couple different scenarios in Jira Cloud. I tried to follow the automation guidelines in the Atlassian documentation but I can't seem to make it work.

1. When a ticket is created in a software project, upon manual trigger, a new ticket will be created in a service project AND the 2 tickets will be linked together using the "relates to" link type. (I have attached the 2 different ways I tried to accomplish this as screenshots)

2. When a ticket is created in a service project, automatically create the same ticket in a software project, then have any status and comments updated in the software ticket translate back to the service project's ticket (not sure if this is even possible but it is an ask we received)

[Bill Sheboy · Accepted solution]

Hi @Kyra Mayock -- Welcome to the Atlassian Community!

FYI that for the rule images you posted, one does what you describe and the other (with branch on Current Issue) seems to try to link to back to itself.

For your question #2, that would be possible to trigger the rule on the status/comments in the software project issue to update the linked one.  You would branch to the linked issue to make the updates from the trigger issue.  Please note: This would need to be a global/multi-project scope rule, and depending upon your license level could be impacted by monthly rule execution limits.  Please discuss this with your site admin to learn about such limits.

Kind regards,
Bill

[Kyra Mayock]

Hi Bill! 

Thanks for replying. I thought my first screenshot, without the branch, should accomplish what I wanted too. However, it doesn't seem to do anything when the rule is run :( 

For Scenario #2 - Do you happen to know the steps to make your suggestion work? Since I'm having trouble even linking newly auto created tickets, I don't think I'll be able to set the rules properly to execute these functions.

[Bill Sheboy]

Can you please show the details of your rule's edit and link components, and and image of the audit log details showing what happens when the rule runs?

I know that "clone" cannot link issues in one automation step, but I thought the Issue Create action could do so.  Perhaps this rule also needs multi-project scope.

[Kyra Mayock]

[Kyra Mayock]

The log says the rule runs successfully, and it does indeed create the new ticket - it just ignores the Link part. 

[Kyra Mayock]

I actually think I figured it out - I had to add the action of create rule, then create a branch and select "most recently created" then add the action of Link Issue! 

Still not sure the correct order of operations and which rules to apply for scenario #2 though - if anyone has suggestions!

[Bill Sheboy]

Well done!  That is what I thought was happening with the missing branch to the created issue.

Regarding your second scenario, please see my first comment as that would require a different rule with global/multi-project scope to sync the issue information.

[John Funk]

@Kyra Mayock I am marking this as Answer Accepted to close it out. Let us know if you need anything else.