Broken issuetype scheme under project settings: ${issueTypeScheme.name}
Platform Notice: Cloud - This article applies to Atlassian products on the cloud platform.
Summary
The project lost its issuetypescheme, and now it appears as broken ${issueTypeScheme.name} issuetype in UI:
Environment
Jira Cloud
Diagnosis
JIRA's Default Issue Type Scheme has somehow become corrupted in the database causing problems with new issue creation, and accessing the existing issues in the affected project.
The root cause for this is still unknown (but we observed such behavior post migrations/recovering projects from the archive where the associated issuetypescheme doesn't exist).
Solution
Through API call, you can apply the primary fix:
HTTP Method: GET
API Call: https://<site name>.atlassian.net/rest/api/3/issuetypescheme/project?projectId=<projectId>
It will show the "Default Issue Type Scheme" in the result
Example:
{
"maxResults": 50,
"startAt": 0,
"total": 1,
"isLast": true,
"values": [
{
"issueTypeScheme": {
"id": "10000",
"name": "Default Issue Type Scheme",
"description": "Default issue type scheme is the list of global issue types. All newly created issue types will automatically be added to this scheme.",
"isDefault": true
},
"projectIds": [
"10099"
]
}
]
}- Create a copy of "Default Issue Type Scheme"
- Get the Id of the new IssuetypeScheme
- Use the below API call to associate the new IssuetypeScheme with the project.
HTTP Method: PUT
API Call: https://<site name>.atlassian.net/rest/api/3/issuetypescheme/project'
Body:
{
"issueTypeSchemeId": "10001",
"projectId": "10099"
}
* Replace 10001 with the required IssuetypeSchemeID, and 10099 with the correct projectID.
A BUG is already raised in our portal to track broken issuetypescheme for projects
JRACLOUD-72473
-
Getting issue details...
STATUS
If this solution is not helpful, please contact Atlassian Support
Last modified on Jun 29, 2023
Powered by Confluence and Scroll Viewport.