Automation throws "Unknown Fields" error after cloning.

[Luyang Zhang]

In an automation rule I set an action of "clone issue".

It throws "Unknown fields set during clone, they may be unavailable for the project/type. Check your custom field configuration. Fields ignored - Labels (labels)". The automation can still finish the clone process but shows "Some Error" in the audit log.

To solve this issue, I have tried these attempts but didn't work:

• Added "Labels" to the associated screen, and I can see "Labels" in the ticket side bar.
• Set "Labels" to "Global context".
• Set this automation rule actor to myself who is a Jira global admin role.
• Checked the "Labels" value and there is no illegal value. 

Does anyone know how to solve this error? Thanks in advance.

[Bill Sheboy · Accepted solution]

Hi @Luyang Zhang -- Welcome to the Atlassian Community!

For a question like this, please post an image of your complete automation rule, images of any relevant actions / conditions / branches, an image of the audit log details showing the rule execution, and explain what is not working as expected.  Those will provide context for the community to offer ideas.  Thanks!

Until we see those...

Is the rule trying to clone an issue into a different project or the same project?

What types of projects are involved for the source and clone-to issues: company-managed, team-managed, or one of each?

Do you have only the built-in Labels field with that name, or has someone added another field with the same name?

Kind regards,
Bill

[Luyang Zhang]

Hello Bill,

Thank you for your reply and warm welcome!

Your questions actually help me! I found there is another legacy "Labels" custom field exists, and this error is gone once I deleted the duplicated "Labels" and relinked scheme.

Thanks again for your help!