Issue Summary

When using Global and Multi-project scope rules, Automation for Jira can set the request type field when the default locked field is represented with the name "Request type". However, it doesn't work when the field is represented with the name "Customer Request Type".


Steps to Reproduce

 1. In an instance that uses the "Customer Request Type" field, create a Global or Multi-project scope rule
 2. Select the desired trigger and, if necessary, a condition > Add a New Action > Edit Request Type > Search for a request type in the drop-down menu

Expected Results

Request Types should appear in the drop-down menu, as shown when using a single-project scope rule or in instances that use the Request type field.


Actual Results

No Request Type appears.


Additional information

When trying to search for a request type in a Single-project rule, the search uses the below endpoint:

https://<instance>.atlassian.net/rest/servicedeskapi/servicedesk/7/requesttype?searchQuery=

When trying to search for a request type in a Global and Multi-project scope rule, the search uses the following endpoint:

https://<instance>.atlassian.net/rest/api/2/jql/autocompletedata/suggestions?fieldName=Request%20Type&fieldValue=

Workaround

1. Create a Single-project rule for each service project;
2. Use the Advanced edit action of the Edit issue action with the below value, where customfield_1000X is the ID of the Customer Request Type field on your instance and you can fill in the ID of the desired Customer Request Type:

{
    "fields": {
       "customfield_1000X": "XXXXXX"
    }
}

• You can get the field ID by going to: Settings > Issues > Custom field > Locate the field > Click on three dots icon (•••) > View field information > See the URL.
• You can get the request type ID from the URL when you try to edit the request type.