I can not understand why this is so difficult. I have tons of projects on my Jira server and a lot of them now have the unwanted default issue type scheme. I can not look at each of the several hundred projects and check. Why ONLY the default issue type scheme doesn't show associated projects(or a lit of unassociated projects) is just inconvenient and perplexing.
So we're not supposed to query the Jira DB with SQL, well that's fine because I don't have access anyways. I took a peak at the REST API and have tried so many things and googled a lot of stuff trying to find a solution.
Is there a way? I surely can not see it now.
Michael,
Go to "Administration">"Issues">"Issue Type Schemes". Find the default issue type scheme and click "Edit". This will then show you a view where it will say "Used by X projects". Click on that link to see the list.
OR
Find a project that is currently using the default issue type scheme. Navigate into that project's administration section.
Once you are in there, click on "issue types" on the left hand side bar. Then, click "Actions>Edit Issue Types".
This will then show you a view where it will say "Used by X projects". Click on that to see the list.
I feel silly now, I should have checked this. This is awesome thank you!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Kian Stack Mumo Systems , I have more than 50 projects which are using this Default Issue Type Scheme. I can see only a few project, and it says "and 36 hidden projects". Is there a way that I can run SQL against the database? or any other way?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Nirmani Kalakheti ,
You can check those projects using default Issue type scheme with the following SQL
SELECT p.pkey, p.pname
FROM project p
LEFT JOIN configurationcontext cc ON p.id = cc.project
WHERE cc.id is NULL
Those projects using default issue type scheme will not have a corresponding record in the configurationcontext table.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.