Forums

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

Can't copy components from trigger issue to match in newly created issue.

Greg Mihailides
Contributor
March 19, 2024

Hello all, 

I have an automation that has been working well that, when triggered, creates a similar issue within another project and I have many of the fields from the trigger issue mapping to the new issue that runs well, with the exception of 'Components'.

All of the other fields I chose to set are copied from the trigger issue and map well in the new issue. For some reason, 'Components' won't copy over. I initially set it up like I did for the rest of the fields where it was just copied from the trigger issue. Then I found this article which showed that I needed to do it a different way: https://confluence.atlassian.com/automationkb/how-to-copy-components-from-source-issue-to-destination-when-cloning-via-automation-rule-1319572671.html

But that doesn't work either. 

Here is the message I get in the audit log:

Screenshot 2024-03-19 at 2.10.27 PM.png

Any ideas? Thanks for your help! 

2 answers

0 votes
Dexter de Vera
Community Champion
March 19, 2024

Make sure that the components for both project are the same and the components field are is in create issue screen.

0 votes
Benjamin
Community Champion
March 19, 2024

Hi @Greg Mihailides ,

 

Is the Components field part of your screens for both the source and destination create issue? Usually this message shows up because it can't find the field to set in the creation screen for the destination issue. 

 

Hope this helps.

Greg Mihailides
Contributor
March 19, 2024

Yes, we recently added it to the destination project. 

Suggest an answer

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

Atlassian Community Events