You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
I have written a few Jira automation rules but have not been able to figure out a solution to what we need for our workflow.
Background: (Jira admin access on the project only, not global admin access)
What I want to happen:
Would appreciate any assistance!
Hi @Donna Tang
As long as there is a link between those issues then you can perform such actions. Issue clone adds the link for you.
For transition linked issue create a rule like this.
I hope it helps.
Hi @Donna Tang
Adding to what @Ravi Sagar _Sparxsys_ suggests, you note the original and cloned issues are in different projects. Is that correct?
If so, you will need a global/multi-project rule as a project-scope rule cannot update issues in another project using automation actions. And depending upon your Jira license level, there are limitations on the number of global/multi-project rule executions per month. Please look here for more information: https://www.atlassian.com/software/jira/pricing
Hi, Donna. My understanding is there are currently only two ways to change multiple projects' issues from a Jira automation rule:
Donna, here is an article on calling the REST API from an automation rule. I hope it helps if you try that route: