nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Edit issue with additional fields in jira automation failed recently

Hi community,

Anyone know why edit issue with additional fields failed recently?

{ "update": { "Approvers" : 
[ { "set": { "id":"xxxx" } } ] } }

The purpose is to overwrite the existing Approvers field value with "xxx", but add additional approvers.

Thanks,

YY Bro

Accepted answers

How did it fail? Would you please show an image of the audit log details, or did it fail when you were trying to create the rule?

And...is the Approvers field for issues or something else? Perhaps check to confirm you have the correct smart value, or try the custom field id: https://support.atlassian.com/cloud-automation/docs/find-the-smart-value-for-a-field/

Finally, although I haven't seen an open defect with update / set for this field, I wonder if using the "fields" syntax with the JSON will help as you want to overwrite the value.

Kind regards,
Bill

All comments

Hi YY,

Do you want to override or add?

To add, follow this format though it is for a group picker field.

{
"update": {
"Approver groups": [{
"add": { "name": "{{triggerIssue.Group Single Picker}}" }
}]
}
}

Hi John, I want to override the existing approver.

How did it fail? Would you please show an image of the audit log details, or did it fail when you were trying to create the rule?

And...is the Approvers field for issues or something else? Perhaps check to confirm you have the correct smart value, or try the custom field id: https://support.atlassian.com/cloud-automation/docs/find-the-smart-value-for-a-field/

Finally, although I haven't seen an open defect with update / set for this field, I wonder if using the "fields" syntax with the JSON will help as you want to overwrite the value.

Kind regards,
Bill

Hi @Bill Sheboy @John Funk ,

Thanks for your help. Below are the screenshots about the rule and log:

It worked before, but failed recently. It's for JSM Change Enablement scenario with approval. The related field is Approvers.

Thanks,

Yong

I am unclear how that could have worked if the field was always a multiple-select, user field, and now has suddenly stopped working with no rule changes.

Let's try the fields syntax to set the field in one step:

{
  "fields": {
    "Approvers" : [
      { "id":"xxxx" }
    ] 
  }
}

I used Edit issue with Approvers field directly to make it go ahead.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-service-management-cloud

jira-service-management