Summary

The project key default pattern is the following:

[A-Z][A-Z0-9]+ 

If this pattern is not respected the following error will show up in the UI:

 We couldn't connect to that issue Make sure that this issue actually exists in that project. If it does, try again in a few minutes. If you still can't link to the issue, contact your Jira admin.  

And the following error is thrown on the dev tool:

  sentFrom: "jira.frontend.issue.fetch.issue-fetch-epic",…}

...

buildKey: "JF-PROD-9526"
event: {message: "No project could be found with key ...  

... 

message: "FETCH_ISSUE_REQUEST: Failed to fetch issue data"
sentFrom: "jira.frontend.issue.fetch.issue-fetch-epic" 

Note: This pattern can be modified in the server environment.

Steps to Reproduce

1. Try to restore a backup from a Jira server instance in which the project key pattern is not respected.
2. Try to access the Jira issue in the new issue view

Expected Results

• See the content of the Jira issue.

Actual Results

Workaround

• The old issue view can fetch the data normally. So by adding the following to the URL, the user can see the content:

   <instance_name>.atlassian.net/browse/<Issue_key>?oldIssueView=true