It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

How to include all issue types in "Default issue type scheme"? Edited

I´m trying to set "Default issue type scheme" for all my projects, but it only has "Epic" issue type assigned, and I need all standard issue types to be available.

When I edit the scheme, it does not show the "Available issue types" component, which it is present when editing any other scheme (see attached screen capture).

As a workarround I could create a new scheme, but I´d like to use the default.

Thank you.





1 answer

When you go to Jira Administration > Issues > Issue Type Screen Schemes

When you click on "configure" for the default and "Associate an issue type with a screen scheme" is this what you see?isthisit.png

Hello Raynard, thank you for your quick answer. I can´t find steps to get to that screen. When I clic on  Jira Administration > Issues > Issue Type Screen Schemes, I see the list of schemes and options for each are: Edit | Associate | Copy. If I edit, I see the screen I just added to my post, where there are no issue types to select.

If I clic on Associate, it shows me the list o projects assigned to any other schemes.

Hmm...there seems to be an option missing.

This is what I see when I get to the screen schemes. 



That´s weird. I don´t have the "Configure" option you have, and you don´t have the "Associate" option I have. However, I think my Edit option should work, as when editing any other scheme but the default I have all issue types available to select. Below an example.


Looks like we're not using the same Jira.

Hi Mariano,

Did you finally managed to include all issue types in your default ITS ?

I have the same problem on my Jira.

I don't understand why Raynard suggested to look at ITSS configuration ...


Hi Eddy. No, I haven´t been able to. I ended with creating another scheme as workarround.


Hi Mariano,

Thanks for your answer. 

Actually, it seems that it's a normal behaviour for Atlassian :

But it's not consistent with the following KB article :

So I don't understand Atlassian position ...



Suggest an answer

Log in or Sign up to answer
Community showcase
Posted in Jira

Demo Den Ep. 7: New Jira Cloud Reports

Learn how to use two new reports for next-gen projects in Jira Cloud:  Cumulative flow diagram and Sprint burndown chart. Ivan Teong, Product Manager, Jira Software, demos the Cumulative ...

344 views 1 3
Join discussion

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you