when I tried to move an issue from one project to another keeping the issue type (type 'bug'), it gives me an error. Just like reported earlier here:
Now I learned the origin of that error is that the issue type i am trying to move does not exist in the default issue type scheme. Which isn't supposed to happen since the default scheme is the global issue type list which contains all the issues that have been created.
I can't simply add the issue type to get it into that list, because it already exists in some of my other schemes (Error: An issue type of that name already exists.) And since the issue type is in use already, deleting and re-adding it wouldn't be my first choice. Are there any alternatives to just add it silently to the default (say: "repair" the default issue type scheme so it contains all the types again)?
Thanks in advance!
Ah. The design flaw of "default has to contain all issue types" has been fixed in recent versions of Jira.
So you should be able to simply add the Bug back into the default scheme, just like any other scheme.
thanks for the answer. We're running Jira 6.2.3, not sure if that is the latest version. Unfortunately, I don't find how to add the issues to the default scheme since there are no buttons etc. like those for custom schemes.
Did I get you wrong or is my default scheme just messed up?
Bother, yes, I've been working with 6.3 a lot recently. I've just checked a 6.2 and you can't modify the default scheme in there, so yes, you definitely have a broken scheme.
I think you need https://confluence.atlassian.com/display/JIRAKB/Issue+Types+Missing+from+the+Default+Issue+Type+Scheme- I've seen this break when doing upgrades, but that was a while ago, and I had the option of deleting the issue type. I'm not sure how else to reproduce the problem, but I can see you've run into it.
Okay, now - thanks to Nic Brough I got it fixed now. Nic, it was exactly as you described and your linked help page provided the solution.
So, if you use Jira 6.2.x and can't move issues because they are not listed in your default issue type scheme, you have to add them to your database manually (download version only, I assume).
You need access to the Jira database (on file-system level) and better know what you are doing. If you know SQL, it's a piece of cake. After adding those issues to the right database and restarting jira (!), all runs fine again.
I am running Jira Cloud and am experiencing this exact issue. Original issue types were somehow removed from the Default issue type scheme and there is no way to add them back, the buttons do not exist.
As I am on Cloud an there is no DB access, how does one reset the Default Issue Type Scheme?
I did open a ticket and got this solution:
"Regarding the issue, you will have to manually insert them in the database. Please refer to the workaround of Cause 1 in this article. It provides the steps on how to enter the values in the database.
Make sure to generate a backup prior to modifying the database for roll back purposes. If possible, perform this in a Test Instance to make sure everything works before performing it to your Production Instance"
Worked for me.
Atlassian Summit is an excellent opportunity for in-person support, training, and networking.Learn more
Hello! I'm Rayen, a product manager at Atlassian. My team and I are working hard to improve the trial experience for Jira Software Cloud. We are interested in talking to 20 people planning t...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs