Issue populating a LOCKED Field Category

[Joe Tobey]

I have reviewed the Community answer on this, but I am not using the API, I am using the automation tool in JSM.

My goal is to populate the CATEGORY (LOCKED) field with a {{userInputs.<key>}} value.  I keep getting the following error:

"We excluded the configured field from this action as it couldn't be found: Category"

The parameter I am passing is {{userInputs.BuildID}} where BuildID is a value that already exists in the Category drop down.

What am I missing here?

[Trudy Claspill · Accepted solution]

Hello @Joe Tobey 

Please provide a screen image showing your entire rule and the details of the step where you are trying to populate the field.

Is the field included in the issue's Field Layout? Can you set it if you execute the same action manually?

[Joe Tobey]

I can manually Set it for an edit or new screen.

This is the section of the automation where I am applying the user input

The input value for {{userInputs.BuildID}} is "build 2501".  Manually I can see the value (and others)

The exact error is:

[Trudy Claspill]

It is possible that there is more than one custom field named "Category" across your instance and the Automation rule is unclear which one you are trying to reference.

Follow the guidance on this page to get the field ID associated with the Category field in the issues you are targeting.

https://support.atlassian.com/cloud-automation/docs/find-the-smart-value-for-a-field/

Then use the More Options section of the action to set the field using JSON.

https://support.atlassian.com/cloud-automation/docs/advanced-field-editing-using-json/

To set a single select list field you would need to use code such as the following:

EDITED:

{
  "fields": {
    "customfield_11449" : { "value": "{{userInputs.BuildID}}" }
  }
}

[Bill Sheboy]

Hi @Trudy Claspill 

The end of the user input smart value is missing the closing double-curly brackets.

Kind regards,
Bill

[Trudy Claspill]

Thank you @Bill Sheboy ! I fixed it.

[Joe Tobey]

Thank you Both!

[Trudy Claspill]

You're welcome, @Joe Tobey 

Did using advanced editing with JSON solve your issue?