nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

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

Kyra Mayock_0byfvv

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)

automation rule using component only.PNG Automation rule using branch.PNG

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)

Accepted answers

Bill Sheboy

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

All comments

Bill Sheboy

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.

Kind regards,
Bill

Kyra Mayock_0byfvv

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_0byfvv

Rule details.PNG

Link issue rule settings.PNG Create issue rule settings.PNG Audit log.PNG

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud

automation