Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Is it possible to copy a Radio Button's value in Automation?

dave_segreto February 28, 2024

I have an automated Link set up to happen upon creation.
The link-event triggers a another Automation that attempts to copy some fields.

The automation looks like this:

 

For: Linked Issues

  Then: Edit issue fields [Advanced]

{ 
"fields": {
"customfield_1": "{{issue.issuelinks.inwardIssue.customfield_1}}",
"customfield_2": "{{issue.issuelinks.inwardIssue.customfield_12}}",
"customfield_3": "{{issue.issuelinks.inwardIssue.customfield_13}}",
"customfield_4": "{{issue.issuelinks.inwardIssue.customfield_4}}"
}

 3 our of the 4 work.

 

The one that fails is a Radio Button. It fails like this:

TCKT-3903 (Specify a valid 'id' or 'name' for FieldName (customfield_4))

If I use customfield_4.name, I get this:

Additional fields contains invalid field(s) in 'update' or 'fields' section. customfield_4.name

Do we know if there is a way to assign the value of a Radio Button field from one ticket to another? It is, in this case, the same custom field.

2 answers

1 accepted

1 vote
Answer accepted
dave_segreto February 29, 2024

That did not work, but it did lead me to the answer.

"id" seems to fail, but "value" works! I also changed it from inwardIssue to destinationIssue for the sake of ease in the future.

 

{ 
"fields": {
"customfield_1": "{{destinationIssue.customfield_1}}",
"customfield_2": "{{destinationIssue.customfield_12}}",
"customfield_3": "{{destinationIssue.customfield_13}}",
"customfield_4": { "value": "{{destinationIssue.customfield_4.value}}" }
}
}

 

0 votes
Kalyan Sattaluri
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.
February 28, 2024

Hello @dave_segreto 

 

Please try

{
"fields": {
"customfield_1": "{{issue.issuelinks.inwardIssue.customfield_1}}",
"customfield_2": "{{issue.issuelinks.inwardIssue.customfield_12}}",
"customfield_3": "{{issue.issuelinks.inwardIssue.customfield_13}}",
"customfield_4": { "id": {{issue.issuelinks.inwardIssue.customfield_4.id}}}
}
}

 

Let us know if it does not work and we can check next steps.

reference: https://support.atlassian.com/cloud-automation/docs/advanced-field-editing-using-json/#:~:text=%22customfield_11444%22%20%3A%20664-,Radio%20button%20custom%20field,-Select%20a%20single

Kalyan Sattaluri
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.
March 1, 2024

Just FYI for others reference who run into this post, not sure what @dave_segreto  tried as he hasn't shared anything but ID should also work. Its in the documentation itself.

dave_segreto March 1, 2024

Agreed. Try using "id". It didn't work for me, giving this same error:

TCKT-3903 (Specify a valid 'id' or 'name' for FieldName (customfield_4))

However, if it fails, try using "value" in its place. 

Suggest an answer

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

Atlassian Community Events