Forums

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

Cross project issue cloning, unable to transition cloned issue status based on trigger issue

Nathan Yam
Contributor
November 13, 2024

I have the following rule set up to clone an issue from one project to another via a manual trigger. 

Screenshot_2024-11-13_at_16_09_03.png

All the conditions are successfully carried out by the automation except for the last branch condition, below is the audit log. How can I resolve this? 

Screenshot_2024-11-13_at_16_09_23.png

2 answers

2 votes
Florian Bonniec
Community Champion
November 13, 2024

Hi @Nathan Yam 

 

Are you sure the status from FSD project are also available in CISD project ?

 

Regards

Nathan Yam
Contributor
November 13, 2024

Hi @Florian Bonniec correct, it is. 

Florian Bonniec
Community Champion
November 13, 2024

And you have a transition available from the first status of your workflow to the target status ? If you go on CISD-40, you have as user a transition to do it manually ? If it's not available, automation should not be able to reach the status either.

 

Regards

0 votes
Clara Belin-Brosseau_Elements
Atlassian Partner
November 21, 2024

Hello @Nathan Yam

 As an alternative to Automation (that can be complex sometimes), I would suggest trying our app Elements Copy & Sync to manually clone issues to another project.

 It allows you to clone Jira issues with all their content (summary, description, custom fields, comments, attachments…). You can even sync the clone and source issue if needed.

You can check the guide here.

The app is for free during 30 days (and it stays free under 10 users).

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
TAGS
AUG Leaders

Atlassian Community Events