Inconsistent database value for Request Type prevents "moving" issues to a different type and "editing"

Summary

In cases where the value for an request type is in a state unexpected by the database (eg: after imports/exports of data) then it is not possible to move an issue to change its type. An inconsistent value for a request type will present as "No Match" in the issue view (unfortunately this means it is indistinguishable from an empty Request Type without examining the database with the help of support).

If the Request Type field is in the Edit screen for that issue, you won't be able to save any edits in edit screen either.

Environment

JIRA Service Desk.

Steps to Reproduce

Moving problem:

• Modify the value of the customfield of an issue with a valid Request Type in the DB to something of the format "sometext/moretext".
• Attempt to move the issue to a new issue type.

Editing problem:

• Modify the value of the customfield of an issue with a valid Request Type in the DB to something of the format "sometext/moretext".
• Add Request Type to Edit Screen for that issue
• Edit the issue (not inline, click the 'Edit' button)
• Try to save it

Expected Results

"Move" and "Edit" processes complete successfully

Actual Results

"Move" gets stuck in the "Update Fields" step validating the Request type field (no error shown). "Edit" will keep refreshing as we click 'Update'

Workarounds

If the request type field says "No Matches" in the issue view, try setting it to a random value and then remove the value to clear out the invalid request type.