For some reason (something I did, I'm sure), the default issue type scheme now only has Epics, Requirements (a type I created), and Tests (Zephyr). When I edit the default issue type scheme, there is no side box where I could select the other issue types.
Background:
I've been playing around with our new Jira Cloud instance (emersonlnc.atlassian.net) as we work towards using it for the first time. Our main current use is going to be requirements and test definitions, so I was working on defining a custom workflow, etc., etc. I realized after a bit that this wasn't the best idea since Jira is fairly complex and I'm new to administering it. I went in and deleted the extra issue type schemes, screens, etc., etc. I must have messed it up somehow,
Note: if resetting our instance back to the beginning is possible, that's probably a good choice. We don't have anything significant in there yet.
Thanks!
Aimée
@Aimee Willoz Did you delete "Issue types" or "Issue type schemes"? If you deleted only custom "Issue type schemes", then "Issue types" should still be there. Please check what all issue types are present.
Are you using JIRA Software Cloud as well?
If you are using JIRA Software Cloud, then it adds few default issue types like Story, New Feature, Improvement, etc. Try creating a new Scrum or Kanban project and see what issue types do you get in the relevant Issue type scheme created by JIRA.
Yes, we're using Jira Software Cloud.
The issue types are all still there. I created a new Scrum board and the issue type scheme it created had all the default issue types: Task, Sub-task, Story, Bug, Epic. (I added Test from Zephyr.)
Is it a problem that the Default Issue Type Scheme doesn't have the ability to select all the possible issue types?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Aimee Willoz No, it is not a problem. I think it works like that only. Default issue type scheme is the list of global issue types. All newly created issue types will automatically be added to this scheme. But, you are not able to see those issue types added, and this is a known JIRA Cloud bug : https://jira.atlassian.com/plugins/servlet/mobile#issue/JRACLOUD-59866
Please have a look at the comments from Atlassian on this known bug, and you will come to know that this behaviour is expected in case of Default Issue Type Scheme in JIRA Cloud.
As a workaround of this known issue, you can raise a support ticket with Atlassian Support to get those issue types (available in JIRA Software, JIRA Code Project buleprints) added to Default Issue Type Scheme in JIRA Cloud.
Hope it helps !
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Aimee Willoz Could you please mark my answer as accepted if it helped resolving your issue/queries?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.