Issue Summary

As of Jira 8.19, the Screens administration page uses the REST API to paginate and load the list of screens according to JRASERVER-67331: View Screens page load slow when there are many screens and workflows.
When there is a workflow imported that contains a screen that doesn't exist, loading the Screen Administration page <baseurl>/secure/admin/ViewFieldScreens.jspa ends up with an HTTP 500 error.
The corresponding log entry mentions a missing screen java.lang.IllegalArgumentException: Cannot find Screen with id '<screenid>'.

Steps to Reproduce

1. Step 1 Import a workflow that contains a screen that doesn't exist on the Jira instance
2. Step 2 Load the screens administration page <baseurl>/secure/admin/ViewFieldScreens.jspa

Expected Results

A paginated view of the screens will show up, as well as the workflows that use the screens.

Actual Results

When there is a workflow imported that contains a screen that doesn't exist, loading the Screen Administration page <baseurl>/secure/admin/ViewFieldScreens.jspa fails with the message below

The corresponding HAR file shows that an HTTP 500 error occured.
Tracking the session to the atlassian-jira.log file shows the exception:

java.lang.IllegalArgumentException: Cannot find Screen with id '<screenid>'.

Workaround

• For adding a new screen:
  Access this URL directly to add a screen: <Jira base URL>/secure/admin/AddNewFieldScreen.jspa

• To solve the missing screen id:
  The KBs below show steps on how to solve the missing screen id. However, when another new workflow that contains invalid screen ids is imported, the screen admin page issue will reappear.
  Screens are not showing Workflow Association and can not delete unused screens in Jira
  IllegalArgumentException when searching for issues with specific statuses, or when loading the Workflows page in Jira server