Problem Definition

Currently, a field being Hidden in the Field configuration makes it to where Project automation can't see and act on it. Sometimes, it is desired to have a field set to Hidden in the UI via the Field configuration, but still have Project automation see and act on the field.

This also applies to the scenario below:

, e.g. show hidden Request Types in Issue fields conditions

When comparing the issue field Request Type, the initial results in the dropdown show the last 50 Request Types updated, but when you start to type to execute a search, the results don't bring hidden Request Types.

Suggested Solution

Allow Automation rules to act on hidden fields.

Example - Show Hidden Request Types in search results.  (or) using calculated hidden fields in an IF condition for automation to act on, based on the value.

Why this is important

When the user has more than 50 Request Types, it is impossible to use the Issue fields conditions since there is a chance of the hidden Request Types won't appear in the initial results. The only solution is to use the workarounds below, which may be more complex for some users than others, depending on their actual scenario.

Workarounds - workarounds provided are specific to request types example. For accessing hidden fields, there is no workaround available.

• Temporarily unhide the Request Type to add it to the condition.
• Create an Automation from Global scope

• Use the JQL condition querying the Request Type:

  "Request Type" in ("Request Type Name")

• Use the Advanced compare condition, using the first value as

  {{issue.Request Type.requestType.name}}