Issue Summary

Adding an unsupported field as required will cause it to display a stuck warning message on the Request Type field configuration page, even after marking it not required again with the following warning message and the remove option is not available:

 This field type cannot be shown - you must provide a preset value

This is similar to a fixed bug for the deleted custom fields: JSDSERVER-6143

Steps to Reproduce

1. Install Jira Service Management
2. Create a Service Management project
3. Access the Project Settings
4. Fields
5. Edit the Field Configuration (Pencil icon)
6. Make an unsupported field required, for example: Organizations
7. Access the Request type page;
   1. Project Settings > Request Type > Edit
8. We will see the warning about "This field type cannot be shown"
9. Remove the "required" from the unsupported field (e.g: Organizations);
10. Refresh the Request Type fields page. 
11. The field will still be listed in the Hidden section with the "This field type cannot be shown - you must provide a preset value" warning.

Expected Results

When marking the field as not required again, the warning message will disappear. 

Actual Results

The warning message will be stuck in the Request Type configuration page even if the field is no longer required.

Workaround

This seems to be a visual issue, so we can ignore the warning message (Recommended ), or we could use one of the workarounds:

1. Creating a new request type will remove the warning message.
2. We can remove the unsupported field from the Request type directly from the database. ( Make sure to test it in a staging instance first.)

PostgreSQL queries:

1. Stop Jira;
2. Create a backup of the Jira database.
3. Run below SQL to list all the fields in the request type affected (You should be able to see the affected field as "Unsupported").

   SELECT * FROM "AO_54307E_VIEWPORTFIELD" where "FORM_ID" = REQUEST_TYPE_ID;
   

   You can find the FORM_ID on the top URL while accessing the affected request type: /servicedesk/admin/PROJECTKEY/request-types/request-type/REQUEST_TYPE_ID

4. Run the following SQL to list all the affected request types;

   SELECT * FROM "AO_54307E_VIEWPORTFIELD" where "FIELD_ID" = 'customfield_XXXXX';
   

    Replace XXXXX with the custom field ID: Check the URL in the custom fields list

5. Update the Unsupported customfield value and set the required value to 'false' 

   UPDATE "AO_54307E_VIEWPORTFIELD" SET "REQUIRED" = 'false' where "FIELD_ID" ='customfield_10002'';
   

   1. Or, we can also choose to delete the field from the affected request types - This will eliminate the last step (to remove the field via UI) - ( However, use this with caution, make sure that the field ID is correct)

      DELETE FROM "AO_54307E_VIEWPORTFIELD" where "FIELD_ID" = 'customfield_XXXX';
      

6. Start Jira
7. Remove the field in the Request Type configuration page.