Jira Service Automation (Clone to Work Management Project)

[Lynda Kho]

Hi! I need a little help here. I have set up an automation that it can auto-clone an issue from Jira service to a dedicated board that I have created at work management.

All description, reporter, attachment were able to clone over except my custom fields.

These are my custom fields:

Product type <single dropdown selection>

{{issue.fields.customfield_10143}}

Short text field <single line text field>
{{issue.fields.customfield_10141}}

Artwork Type <single dropdown selection>

{{issue.fields.customfield_10144}}

I'm not so sure where it went wrong but I got message stated:
"Unknown fields set during clone, they may be unavailable for the project/type. Check your custom field configuration."

I'm not a developer so I am not familiar with JSON but will appreciate if anyonw can assist me in any possible method.

Thank you!!

[Patrik Korovsky]

Hello @Lynda Kho ,

Could you confirm that your custom field exists in the project where you are copying it? You might need to create fields of the same type in the Work Management project.

[Lynda Kho]

Hi @Patrik Korovsky  I already have these fields in the work management projects. Are these sufficient? The fields are there, however, it just wouldn't clone from the jira service projects. 

I also checked the custom fields, it's currently under 2 of my projects.

Thanks!

[Patrik Korovsky]

Hi @Lynda Kho

Here is what I recommend:

1. Field Configuration Check: Make sure that the custom fields (Product type, Short text field, Artwork Type) are present in both the source (Jira service) and target (Work Management) projects.
2. Field Type: Ensure that the field types in the target project match those in the source. For instance, if 'Product type' is a single dropdown selection in Jira service, it should be the same in Work Management.
3. Field Context: Custom fields in Jira can have a 'context', which means they might be available for specific projects or issue types. Make sure that the custom fields' context includes the Work Management project and the issue type you are cloning.

If the custom fields are already present in both the projects, then the next step would be to adjust the cloning automation.

Here's a step-by-step approach:

1. Automation Rule: Navigate to the automation rule you have set up for cloning.
2. Clone Issue Action: Within the rule, find the 'Clone issue' action.
3. Set Fields Manually: Instead of letting the automation auto-detect the fields to clone, manually select the custom fields you want to clone.
   1. Under the 'Fields to Set' section, choose each custom field (like Product type, Short text field, Artwork Type).
   2. Specify that the field's value should be copied from the triggering issue.
      By explicitly defining the fields you want to clone, you can often avoid issues related to auto-detection or mismatches between projects.

I hope this helps. If you still encounter issues, please share the audit log so we can dive deeper into the problem.

[Lynda Kho]

Hi @Patrik Korovsky , thanks for the guidance. I have tried your suggested method and many other possible ways that I found from the community, however, it didn't work still.

Method 1:
Copy from the triggering issue.

Method 2:
Use different smart values for possible outcomes

Method 3:
I tried to type these into JSON (a suggestion I found from other users)

{

"fields":

{

"customfield_10143": "{{issue.customfield_10143}}",

"customfield_10141": "{{issue.customfield_10141}}",

"customfield_10144”: "{{issue.customfield_10144}}"

}

}

I have also counter-checked with the configuration to make sure that the customs fields are enabled in the destination projects.

None of the methods work for now.

[Luka Hummel - codefortynine]

Hi @Lynda Kho

If you are willing to try a third-party tool, our app Deep Clone for Jira can help you in cloning issues with their custom fields.

You can also trigger a Deep Clone in a Jira automation with a looping transition.