Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Automation - Unable to clone issues within the Epic to another company managed Jira Project

Atlassian Software Consulting (ASC)
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
May 30, 2023

Hi,

I have created two company managed Kanban Jira projects.

On Project (1) - Verify automation 2 -Project name, I have created Epics & two child issues inside that Epic.

I have configured automation rule to clone epic & its child issues from Verify automation 2 to Verify Automation (Another Kanban Company managed project)

Untitled.png

1 answer

0 votes
Trudy Claspill
Community Champion
May 30, 2023

Hello @Atlassian Software Consulting (ASC) 

Welcome to the Atlassian community.

In what way is the rule not working for you?

Is the rule being successfully triggered?

What does the rule's Audit Log show for details for execution of the rule?

Because the rule is being triggered in one project and you are trying to use the Clone action to clone issues to another project, I believe that you will have to set the rule as a multi-project scoped rule, naming both the source and destination projects in the Scope on the Rule Details. That can be done only from the Global Automation page accessible to Jira Admins from the System option under the cog icon next to your Avatar.

When you make the rule a multi-project scope rule you will need to add conditions after the trigger to limit the actions to happen only when triggered from your intended source project.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
FREE
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events