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.
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}}" }
}
}
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.