Custom field not copying over with automation on TMP projects

[Valentina Migliore]

Hello,

I have set up an automation through 2 boards to create an issue on board B when the original ticket on board A has moved to a specific status.

I am trying to copy all of the fields including the custom ones over to the new ticket but I have 2 that just don't want to copy over.

The error I get is 

Found multiple fields with the same name and type: .

Technical Notes (com.atlassian.jira.plugin.system.customfieldtypes:textarea)

Can someone help me understand what I am doing wrong? 

I have set in the Create Issue action to Copy these fields from the trigger and the names match correctly.

Thank you!

[Luka Hummel - codefortynine]

Hi @Valentina Migliore

As the others have already pointed out, it needs a bit more work and/or preparation to copy field values out of team-managed projects. Additionally, your Automation will probably easily break and difficult to adapt to use in another project.

If you are willing to use a third-party app, our app Deep Clone for Jira can clone issues between team-managed and company-managed projects. It will match custom fields as long as there is an identically named custom field in the target project, enabling you to copy these field values.

You can also use Jira automations to trigger the clone.

[Trudy Claspill]

In Team Managed projects it is possible to add to the Team Managed project custom fields that were defined for Company Managed project, when those Custom Fields have a Global Context. In that case the field would be the same field, within the underlying database, between the two Team Managed projects.

Or for the others that are successfully copying you may be referencing System defined fields, like Description, Summary, and Priority.

It is possible that you have two custom fields with the same name that were created locally within each Team Managed project.

As suggested by @Bill Sheboy you need to find the custom field IDs for the fields you are having trouble copying. You need to find those IDs by using the below how-to article and looking at an example issue from the source project and an example issue from the destination project to see what the ID is in each project.

https://support.atlassian.com/cloud-automation/docs/find-the-smart-value-for-a-field/

[Bill Sheboy]

Hi @Valentina Migliore 

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...

As these are team-managed projects, you may need to use advanced edit with JSON and specify the custom field id values, rather than use the field dropdown lists.

To find the custom field id values, please use this how-to article: https://support.atlassian.com/cloud-automation/docs/find-the-smart-value-for-a-field/

Kind regards,
Bill

[Valentina Migliore]

Hi @Bill Sheboy ,

thank you for your answer. Here are the screenshots:

Technical Notes and Testing Notes are the only fields I can't figure out why they don't copy over.

I have done the same with bugs and on those I have 3 custom fields and they all copy with no problems...

[Bill Sheboy]

That seems to confirm the fields are sometimes "confused" and sometimes not in the rules.  I recommend checking some of those Bug issues types to confirm the fields actually copied as you needed, or if they have null values.

For this rule, please try setting just those fields using their custom field ids and advanced edit with JSON: https://support.atlassian.com/cloud-automation/docs/advanced-field-editing-using-json/

[Valentina Migliore]

@Bill Sheboy thank you, I will give it a try!

[Marc - Devoteam]

Hi @Valentina Migliore 

This can't be done in relation to Team Managed projects.

Team managed projects are siloed, so any created custom field in a TMP is project bound, so if you create a new field in 2 TMP projects, with the same name this is not the same field.

To achieve want you want in relation of usage to the same field in both projects, you need to use company managed projects.

[Valentina Migliore]

Hi Marc,

Thank you for your answer. However, I have other custom fields across the same projects that are copied over correctly through the automation, which makes me think that this can work on my TMPs.

These 2 only are giving me an issue.

Thanks!

[Marc - Devoteam]

Hi,

are both fields the same type of field?

[Valentina Migliore]

Yes, they are both text area fields