Fields from issue A are not copied over to issue B

[Anthony Ellerbrock]

RULE. Create a new issue in project B, when issue in project A transitions to "DONE".

The new issue is getting created, however the description, acceptance criteria, ect are not getting copied to new issue even though they're defined in the "Create a new" component.

[Clara Belin-Brosseau · Accepted solution]

Hello @Anthony Ellerbrock

If you're willing to use a third-party application, I can suggest trying our Elements Copy & Sync app that allows you to copy issues with all their content (summary, description, custom fields, comments, attachments, etc.) and their child issues.

You’ll be able to automatically copy all your issue data into the new project once the source issue status is updated.  

Don't hesitate to try our app, it's free during 30 days and stays free under 10 users.

Let me know if you have any questions.

Kind regards,

Clara

[Anthony Ellerbrock]

Thank you all, problem solved.

[Luka Hummel - codefortynine]

Hi @Anthony Ellerbrock and welcome to the community!

If you are willing to use a third-party app, you can try our Deep Clone for Jira. You can trigger Deep Clone via a Jira automation. Deep Clone will clone the issue, including its custom field values and app data of other third-party apps.

[Wojciech Wardaszko _HeroCoders_]

Hi @Anthony Ellerbrock

Please check the Audit log of your automation that is supposed to copy the fields to the new issue.

It should tell you what went wrong. Often times they fields we try to copy are not on the create issue screen in the other project. Fields not present on that screen cannot be set during issue creation.

You can either add those fields to the create issue screen in that Project B or change your automation to edit the fields on the created issue (branch) after it is created.

Hope this helps. Cheers!

[Kalyan Sattaluri]

Hello @Anthony Ellerbrock 

You probably are not using the correct syntax for smart values.

Please share screen shot of your rule where you are creating this new issue in project B.