Issue Summary

Attempting to view certain issues return back an error 'We couldn't connect to that issue'.  

JQL filters that return results with these certain issues return back Internal Server Error.

Steps to Reproduce

1. Browse directly to the issue or search for the issue in JQL filter.
2. Issue view 'We couldn't connect to that issue', or JQL filter returns back Internal Server Error.

Expected Results

Should be able to view the issue or search for the issue directly.

Actual Results

The browser console shows during the issue view loading, the graphQL POST API receives a response of 200 OK but a JSON payload that shows a 500 error with no message detail.

Request URL: https://examplesite.atlassian.net/rest/graphql/1/
Request Method: POST
Status Code: 200 

{
   "errors":
    [
        {
            "path":
            [
                "issue"
            ],
            "errorMessages":
            [
                null
            ],
            "message": "null",
            "statusCode": 500
        }
    ]
}

We've found that this only happens in the New Issue View, when viewing the same issue in Old Issue View the issue displays properly, with the following warning displayed:

After reviewing this in the Jira DB, the certain issues that can't be viewed all have this in common, the issue link types do not exist in the database.

This has been identified by the responsible dev team on an internal ticket.

Workaround

For any issues that cannot be viewed because of this bug, you can still view them in old issue view:

• Browse to the issue URL and add ?oldIssueView=true at the end of the URL, for example:
  • Change the original URL:

    https://examplesite.atlassian.net/browse/JSW-123
    

• • To the new URL:

    https://examplesite.atlassian.net/browse/JSW-123?oldIssueView=true
    

There currently is no workaround for JQL filter searches not returning these issues.