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

Why is my custom field not showing up in field selection when creating an automation?

Brittany Montgomery

I am creating a new automation for my project that involves a field titled "Forms". We've used this field in other automations without issue. However, when I was creating a new automation using this field, the field is not populating when selecting "choose fields to set". The field is assigned to the project as shown in the screenshots. Does anyone have a solution or a possible workaround for the component "Then: Edit work item fields"?

Screenshot 2026-02-17 160912.png Screenshot 2026-02-17 160949.png

Accepted answers

Bill Sheboy

Hi @Brittany Montgomery

There is an existing smart value named forms to support JSM data, and thus your rule may be colliding on the values. I recommend not using field names which are the same as built-in fields or smart values for this same reason.

Kind regards,
Bill

All comments

Bill Sheboy

Hi @Brittany Montgomery

Kind regards,
Bill

Brittany Montgomery

Hi Bill,

Thanks for your reply. We've had this field for over a year and haven't had any issues until now. It's a people field and is used by other projects as well. The field is "Forms" with a capital "F" and it appears the forms you referenced is lowercase. Is there a workaround to allow this field to be selected in automation rule creation? Thanks!

Bill Sheboy

First, sorry I missed this is a People type field in the question; those are a bit "weird" and only used in Team-managed projects / spaces, and they have a few challenges with automation rules:

Each People field used is configured for each individual space
Even when it is configured as single-selection, it is behaves as if it is multiple-selection, user-picker field behind the scenes (i.e., the JSON uses array syntax)
And, the email address attribute is not available for People fields to a rule

To use the People field in a rule for an edit, you may use a JSON expression in the advanced edit section of the action, and you will need to add / remove people from that type of field using their account ID values and the custom field ID.

First, use the { } at the right of a field or this how-to article to identify the correct custom field ID: https://support.atlassian.com/cloud-automation/docs/find-the-smart-value-for-a-field/

Then to build your JSON expression, please see this information: https://support.atlassian.com/cloud-automation/docs/advanced-field-editing-using-json/#Multi-user-picker-custom-field

Please let me know if you need help with the JSON, perhaps describing what you want to do the to field: set the value, add a person, remove a person, etc. Thanks!

Brittany Montgomery

Hi Bill! I took a screenshot of the automation I am working on to help with what I'm asking it to do. On the highlighted component for editing work item fields, this would specify that if the previous components are true, then edit field Forms to fill in to user ID 5cf977af623cba0f42e00fd1. If you wouldn't mind, could you help me with the JSON needed for the advanced section of this highlighted component? Thank you! Screenshot 2026-02-18 142302.png

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-cloud