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

Moving (Cloning) an Issue Within Sandbox Projects


Alright, so what I am trying to do is to test a bit of automation in our sandbox before I move it to production. The automation I am testing is cloning an issue from project A once it is created to another project called "project B". So far, I am fairly successful within that automation. Except, the cloned issue that was "moved" from project A to project B will not trigger a separate automation within project B. I have that automation attempting to change the request type of that cloned issue in project B.

I have attempted to use the automation triggers "When an issue is moved" and "When an issue is created". Neither have been triggered when this cloned issue was created. Is there a limitation to the sandbox? Or am I misunderstanding how the automation triggers work?

Below are screenshots of the automation I have created:


This is the automation in project A that is cloning the initial issue. This works.


This is the automation in project B that is attempting to set the request type of the cloned issue. This is not triggering.

1 answer

1 accepted

2 votes
Answer accepted
Trudy Claspill
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 05, 2023

Hello @Alex Thousand 

In the automation set up in Project B on the Rule Details page there is a checkbox to allow/disallow the rule to be triggered by actions executed in other rules. That needs to be unchecked for the rule to be triggered by actions from other rules.

Screen Shot 2023-05-05 at 9.48.45 AM.png

Also, I think you should be using the Issue Created trigger.

That worked! Thank you! 

Like Trudy Claspill likes this

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events