Steps to reproduce:
1. Create an issue type (through JIRA global settings)
2. Add it to an issue type scheme.
3. Create a project with the issue type scheme above.
4. Create a request type with the issue type.
5. Remove the issue type from the scheme for the project.
6. Delete the issue type (through JIRA global settings).
7. Go to the portal.

Expected Behaviour
Users would see an error when deleting the issue type or the request type would be removed/hidden.
An error would be displayed when viewing the request types under project settings.

Actual Behaviour
'Undefined' request types will appear beneath the other request types.
No request types are loaded in the project settings page due to an error caused by the missing issue type.

Workaround
For customer: currently no workaround.
For support with access to DB: deleting the incorrect requestTypes and GroupToRequestype rows from the database