Clicking an issue link results in project not available error page
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
When a user clicks on an issue link, they are taken to an error page rather than the issue. The URL for the page doesn't match the normal pattern.
Expected: base url/{{/Issues/}}issue key
Actual Result: base url/{{/project/}}/issue key
The error page text is "This project isn't available. It may have been deleted or your permissions may have changed." It will look similar to this screenshot:
Cause
When configuring a custom regex pattern for project keys, an administrator has used an expression that also matches the configured pattern for issue keys. This makes JIRA mistakenly identify the issue key as a project key.
Example Project Key Regular Expressions
1
2
Default: ([A-Z][A-Z0-9]+)
Broken: ([0-9A-Z_]{2,32}-?[0-9A-Z_]{1,32})When JIRA looks at the above and notices that it can accept numbers in the second section of the Project Key before any Alphabets, when you click on the Issue Key, you would get redirected to the project URL instead and get the error.
Solution
Follow the instructions at Changing the project key format to set the pattern for project keys to an expression that does not overlap with the pattern you use for issue keys.
To fix this example, the 0-9 has been dropped from the second section following the -
Example Project Key Regular Expressions
1
2
Broken: ([0-9A-Z_]{2,32}-?[0-9A-Z_]{1,32})
Fixed: ([0-9A-Z_]{2,32}-?[A-Z_]{1,32})Was this helpful?