Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

When a cloned issue has status updated, update status of original issue


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)

  1. We have all incoming requests created as an issue on a main project board
  2. From there the issue would remain on the board and transition through your typical statuses (To Do, In Progress, On Hold, Done/Cancelled).
  3. I currently have automation setup so that when the original issue is triggered to status of "Assigned to Tech Team", the issue then cloned to the relevant project board based on the label. (IE: PDA goes to PDA project board, RPA goes to RPA project board, etc. etc.)

What I want to happen:

  • when cloned issue's status is transitioned, trigger status update on the original issue/story. (IE: so this would mean when the tech team completes their work, it would update the original request. Please note, that it is also possible that multiple tech teams need to be assigned)


Would appreciate any assistance!

Thank you.



1 answer

1 accepted

2 votes
Answer accepted

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:

Best regards,

Like Curt Holley likes this

Thanks @Ravi Sagar _Sparxsys_ @Bill Sheboy 

Apologies for the late response.

I'm aware of the need for global admin access to be able to make it work and the costs.

Is there any way around this somehow since I'm admin for all the boards that I need to apply automation to?



Hi, Donna.  My understanding is there are currently only two ways to change multiple projects' issues from a Jira automation rule:

  • Easy and license limits: use a global-scope rule
  • Difficult and fewer limits: call the REST API from a project-scope rule to change what you need in other projects
Like Donna Tang likes this

Thanks Bill.

Looks like the API route it is.

Appreciate the quick responses. Have a great day!



Donna, here is an article on calling the REST API from an automation rule.  I hope it helps if you try that route:

Best regards,

Like Donna Tang likes this

Hi all,


one question regarding this rule.

Do I get it right, that I have to have it running in both projects where I have the clones?


Thanks and best regards


Suggest an answer

Log in or Sign up to answer

Atlassian Community Events