Issue Summary

When a custom field has a context configured with specific issue types (rather than with all issue types), the field cannot be updated within Automation rule action and error appears instead of possible field values.

Steps to Reproduce

1. Create a custom field
2. On Custom fields page > find the field > click Configure
3. Edit Configuration > select some issue type (make sure it is not "Any issue type") > select Modify
4. Go to Jira project settings > Automation > edit (or create) a rule
5. In THEN block, click "Add action" > Edit issue > Add > search for and select newly created field

Expected Results

Available field values are displayed OR user gets a message that there is no context applicable for this project (therefore, user should not be able to select this field).

Actual Results

The following error gets displayed in Jira:

At the same time, the following gets logged:

019-08-14 12:54:03,998 http-nio-8240-exec-11 WARN admin 774x1027x1 ijrev8 172.29.89.30 /rest/servicedesk/automation/servicedeskmodules/1/then/edit-issue/10000/field [c.atlassian.ozymandias.SafePluginPointAccess] Unable to run plugin code because of 'com.atlassian.jira.util.dbc.Assertions$NullArgumentException - config should not be null!

Workaround

Potential workaround could be to define a new context for the project where Automation rule will be defined. However, the context needs to be applied to "Any issue type":

Then, the Automation action won't display any error:

This workaround is not applicable if the project requires to have this field context applied to a certain issue type.