Error - automation to clone issue.

[Karla Garcia]

Hi!

I am trying to:

- Once an issue is created in Project A -> Clone to project B.

Project A and B are both company managed;

Error: Failed to fetch fields for project/issue type;

When I try to clone to a team-managed project, works perfectly.

Thanks in advance for any support :)

[Derek Shore]

I just ran into this exact same issue. For me the problem was that I was setting the issue type to an old issue type that was no longer available in the destination project. Might double check that.

[Bill Sheboy]

Hi @Karla Garcia -- Welcome to the Atlassian Community!

Without seeing your complete rule, I hypothesize it uses the Issue Created trigger.

If so, one possible cause of that symptom is a timing problem: the Issue Created trigger can fire so quickly some data may not be available to the rule yet.  This can cause missing information, and occasionally rule errors.

The fix is to always add the Re-fetch Issue action immediately after the Issue Created trigger, and before any other rule steps.  Please try adding that and re-test the rule.

Kind regards,
Bill

[Trudy Claspill]

Hello @Karla Garcia 

Welcome to the Atlassian community.

Can you please provide images showing your entire Automation Rule, and the details from the rule execution audit log for the execution that failed?

What are the project types for A and B when the rule fails? Get that information from the Type column on the View All Projects page under the Projects menu.

[Mark Higgins]

Hi @Karla Garcia 

I've just come across the same error, and it was indeed that the 'Issue Type' of Service Request from an older project, was different then the project I was cloning to of '[System] - Service Request.

Cheers

mark

[Luka Hummel - codefortynine]

Hi @Karla Garcia and welcome to the community!

For your automation to clone issues from Project A to Project B, consider using our app Deep Clone for Jira. Deep Clone allows you to clone issues, including attachments, comments, and custom fields, across projects with full customization. It ensures seamless cloning even between different project types. This might help avoid the “Failed to fetch fields” error by offering a more robust cloning solution.

You can also try adding a delay or re-fetching the issue, as suggested by others.

[Clara Belin-Brosseau_Elements]

Hello @Karla Garcia

Another way to automatically clone issues is to use our app Elements Copy & Sync.

It allows you to clone and sync a full hierarchy of issues with all their content (summary, description, custom fields, comments, attachments, etc).

You can check the guide here.

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