Unable to create Jira issue from Confluence page: Project with id/key doesn't exist
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
Confluence is not returning Jira project names preventing Jira issues from being created within Confluence. All other application link functionality is working.
Environment
Jira and Confluence application links with OAuth impersonation. Jira is using a customized project key format.
Diagnosis
The following error is shown on the
atlassian-jira.log:
1
2
3
4
/rest/api/2/issue/createmeta [c.a.j.rest.exception.ExceptionInterceptor] Returning internal server error in response
java.lang.reflect.InvocationTargetException
...
Caused by: java.lang.IllegalArgumentException: Project with id/key: 12345 doesn't existVerify the available projects and project keys (pkey) in the Jira database with the following SQL query:
1
select * from project;Cause
The Jira instance is not using a supported project key format:
By default, the Jira project key configuration requires two or more uppercase alphabetical characters — based on the regular expression ([A-Z][A-Z]+).
Ensure that you choose a supported project key format. Only formats that meet all of the following rules are supported:
The first character must be a letter,
All letters used in the project key must be from the Modern Roman Alphabet and upper case, and
Only letters, numbers or the underscore character can be used.
Examples:
Examples of supported keys:
PRODUCT_2013,R2D2,MY_EXAMPLE_PROJECT.Examples of unsupported keys:
2013PROJECT(first character is not a letter),PRODUCT-2012(hyphens are not supported).
Solution
The solution will be to apply the resolution from changing the project key format.
If a number of issues have already been created in your Jira installation, then changing the project key format is not recommended. If you must change the project key pattern after issues have already been created, use a regular expression that allows a more 'permissive' project key pattern than the current one (e.g. use a regular expression which will still be valid for existing project keys defined in your Jira installation).
Was this helpful?