Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Automation failure when cloning an issue to another project

Hi, I am using automation to clone issue for one project to another basis some conditions. The clone occurs successfully on all projects except one.

The automation flow is:

Screenshot 2021-04-23 at 09.31.36.png

The audit log reads:

Screenshot 2021-04-23 at 09.33.01.png

The step in detail:

Screenshot 2021-04-23 at 09.33.45.png

Both the projects have "Bug" as type and both have appropriate create issue permissions


Not sure what is happening here, can you help?

3 answers

0 votes
Flavien Gache Community Leader Apr 23, 2021

Hi Aditi.

Could you tell me what the perimeter of your rule is ? Is it a global rule ? If no, you could try to copy the rule and put one rule with the perimeter Project 1 and the other one with the perimeter Project 2.

Do both issues types have the same fields/screens on both projects ?

@Aditi Sodhi Is there maybe a required field in the DMG project for Bugs? If there is, the required fields will need to be given a value on creation.

One other thing to check is that the Project Role atlassian-addons-project-access has the Create issue permission in the project's permission scheme.

It looks like there is definitely a difference between the two Bugs in the two projects, so I would try to work out what the difference is, e.g. there may be a difference in the

  • Fields - some may be required/not required, are there any field contexts specific to one project but not the other?
  • Create screens
  • Permission schemes
  • Issue type - they may both be the same issue type, but are there any differences in the config?

Hi @Aditi Sodhi  -- Welcome to the Atlassian Community!

For this global-scope rule, what is the type of the two projects: the triggering-issue one and the clone-into one?

Are they both company-managed (classic), both team-managed (next-gen) or one of each type?

Best regards,


Hi @Bill Sheboy , the types of the two projects are different. The rule is defined in the classic project, while the issue is being cloned in a "Next Gen" project

Hi @Aditi Sodhi 

This seems related to this defect for changing the project with the clone action for a Team-Managed project (next-gen), although your use case is slightly different:

I recommend asking your site admin to submit a ticket to Atlassian for this one.  Support can take a look at your instance can confirm if it is the same defect.

Once you hear back from Support, please post what you learn so the whole community can benefit.  Thanks!

Like Aditi Sodhi likes this

Suggest an answer

Log in or Sign up to answer

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you