Issue Summary

When creating a JSM issue, the request type is automatically populated according to the issue type selection. It is changed after an upgrade.

Steps to Reproduce

1. Install any JSM version prior to version 10.7.3 and create a request-type and map it to existing issue-types
2. Click on the " create issue" button, select a JSM project and issue type, and notice that some request types are automatically populated.
3. Upgrade to any version on or above 10.7.4.
4. Click on the " create issue button, select the same JSM project and issue-type same as in step 2

Expected Results

The default request-Type should be same as before upgrade

Actual Results

The default request-Type selection might have changed.

Workaround

Workaround (to configure default RequestType for each IssueType):

The workaround here involves setting the desired default RequestType row in the "AO_54307E_VIEWPORTFORM" table to have the smallest "FORM_ORDER" value of all RequestTypes of the same IssueType.

There are two simple ways to achieve this:

1. Updating the RequestType "FORM_ORDER" value via the{{ /rest/servicedesk/1/project/

/request-type-groups/{groupId}/request-types/{id}}} PUT endpoint. The easiest way to achieve this would be:

• a. modify an existing RequestType (as project admin), with the developer console open

• b. copy the update request as curl

• c. modify the curl request to add the "order":-1 key:value pair

• d. execute the curl request

With this approach, there is no need to restart the instance, the requestType cache is invalidated by the update.

2. Updating the RequestType "FORM_ORDER" value directly in the database and modifying any RequestType to invalidate the cache (or restarting the instance):

SQL query similar to the following: UPDATE "AO_54307E_VIEWPORTFORM" SET "FORM_ORDER" = -1 WHERE "Id" = <Id>;

Before the change:

After the change: