Multiple projects show up for migration when changing the issue type scheme for a project in Jira
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 changing the Issue Type Scheme for a Project in Jira, several other projects may show up for issue type migration instead of only the project that's having the issue type scheme changed.
Environment
All versions of Jira Core 8 and later
Diagnosis
Execute the query below replacing the destination Issue Type Scheme:
1
2
3
4
5
6
7
8
select distinct p.pkey as "Project", it.pname as "Missing Issue Type"
from jiraissue i
join issuetype it on it.id = i.issuetype
join project p on p.id = i.project
join configurationcontext cc on cc.project = p.id and customfield = 'issuetype'
join fieldconfigscheme fcs on fcs.id = cc.fieldconfigscheme and fcs.configname = 'Destination Issue Type Scheme name' -- Replace here
left join optionconfiguration oc on oc.fieldconfig = fcs.id and oc.fieldid = 'issuetype' and oc.optionid = it.id
where oc.optionid is null;Confirm if the projects and issue types are the same that came up on the screen when switching the project's issue type scheme.
Cause
When switching the issue type scheme for a project, Jira validates whether the destination issue type scheme is valid.
If some other projects use the destination issue type scheme and have issues whose types are not present in the scheme, Jira identifies this inconsistency and prompts the admin to fix it—even if the project in question has nothing to do with the others being shown.
Solution
To fix this, simple include in the issue type scheme all the issue types brought by the query in the Diagnosis section then proceed to switch the issue type scheme for the project.
You may later remove the issue types you don't want present in the scheme, and Jira will prompt you to migrate all existing issues that make use of those issue types in all associated projects.
Should you remove issue types from the schemes, bear in mind you'll need to migrate issues and may need special permission in the projects such as assign issues, create issues, etc.
Was this helpful?