Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Automation rule not copying custom dropdown field when cloning between projects

Denilson Cardoso
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
July 31, 2025

Hi everyone,

I'm trying to build an automation rule in Jira (Company-managed projects) that clones a work item from project A to project B when the status changes to "Done". Most fields are being copied successfully — like date and priority — but a custom dropdown field (single select) is not being copied.

Here's what I’ve done:

  • Both projects are Company-managed.

  • The custom field “Departamento Solicitante” (customfield_10113) is available and has the same options in both projects (Dep1, Dep2, etc.).

  • The field is present on the edit and create screens for both projects.

  • I'm using the Edit issue action to set the field like this:
    {{triggerIssue.customfield_10113.value}}

  • I also tried adding JSON to the “Additional fields” section:

{
"fields": {
"customfield_10113": {
"value": "{{triggerIssue.customfield_10113.value}}"
}
}
}

 

But the dropdown field is always empty in the cloned issue.
Any ideas on what I might be missing?

Thanks in advance!

3 answers

1 vote
Evgenii
Community Champion
July 31, 2025

Hi, @Denilson Cardoso

Welcome to the Atlassian Community!

First, check the custom field contexts — it's possible that the field is only available in a limited list of projects. If so, it won't appear in issues outside those projects.

Also, have you tried adding a log action to your rule and including the smart value for the custom field?
This way, you can verify whether the field has a value and confirm that the source data exists.

This can help pinpoint whether the issue is with data availability or rule configuration.

Evgenii
Community Champion
July 31, 2025

One more suggestion: if you're using the "Edit Work Item" action and want to apply changes to the newly cloned issue, make sure to use a Branch action first, and select "Most recently created work item".

Then, place the "Edit Work Item" action inside that branch. This ensures the edit is applied to the correct (cloned) issue, not the original one.

chrome_310725_080.png

0 votes
Priyanka Khare
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
July 31, 2025

Hello @Denilson Cardoso 

Try using the option ID instead of the value. In your JSON, set:

{
"fields": {
"customfield\_10113": {
"id": "{{triggerIssue.customfield\_10113.id}}"
}
}
}

 

Hope this helps!

0 votes
arielei
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
July 31, 2025

Hey @Denilson Cardoso 

Yes, use "Edit work-item" action and set the target field by clicking the 3 dots in the smart-value line and then select "COPY", after that click on it and it will allow you to change from which work-item to copy, for example -> triggered work-item.

arielei
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
August 2, 2025

Hello @Denilson Cardoso 

Were you able to resolve your issue?

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
FREE
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events