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; } } }

Invalid field error in global rule for custom field

Phil Bustin

Inconveniently, the error doesn't appear until I click the exclamation point in the rule summary, or edit the rule, after publishing the rule. The JSON is:

{
"fields": {
"Business Analyst Signoff": { "id": "{{initiator.accountId}}" }
}
}

The error is:

Additional fields contains invalid field(s) in 'update' or 'fields' section: Business Analyst Signoff

Accepted answers

Bill Sheboy

Hi @Phil Bustin

Smart values are case and spacing-sensitive, so did you confirm you have the correct name for that field? You can check that using an example issue with the field and this how-to: https://support.atlassian.com/cloud-automation/docs/find-the-smart-value-for-a-field/

You could also try using the custom field ID name for the field.

Next...you do not show your entire rule for context, so I wonder if the {{issue}} at that location in the rule it has that field? For example, if you are inside of a branch perhaps it could be referencing a different issue type.

Kind regards,
Bill

All comments

Bill Sheboy

Hi @Phil Bustin

You could also try using the custom field ID name for the field.

Kind regards,
Bill

Phil Bustin

I'm sure the field name is correct.

So far, I don't understand what to do with the information provided when I click the link.

I don't know how to use the custom field ID name.

The field appears in the issue.

Here is the entire rule:

Rule error.jpg

Bill Sheboy

I'll try to clarify...

Using your Jira URL in a browser and an example issue, you can find all of the supported fields/smart values for your issue. For example:

myJiraCloudUrl/rest/api/2/issue/myIssueKey?expand=names

Search in the results on the page for your field name to confirm the spelling, capitalization, and spacing of the smart value's name.

If that looks the same as what you already tried, you can also find the custom field ID on the page and use that in the JSON, as described here.

{
  "fields": {
    "customfield_12345": { "id": "{{initiator.accountId}}" }
  }
}

Phil Bustin

The rule was accepted using customfield (why not field name?), but the rule execution log showed:

Action details:
Edit issue
Error editing issues
ASTWFR-8 (data was not an array (customfield_10062))

Again, Business Analyst Signoff is a User Picker (single user) field. Is { "id": "{{initiator.accountId}}" } the name of the user who selected the transition?

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud

automation