"Dirt simple"? Default issue type set to "Epic" but still getting "Story" when I hit Create...

[Sjoquist, Carl]

Hi 

I changed the default issuetype for a company-managed project's issuetype scheme from "story" to "epic".    For me, create still defaults to "story" and same for some other users, while one use reports that it correctly defaults to "epic" for her.    

This is Jira cloud.

I thought this change would be "dirt simple".   What am I missing?

Thanks

Carl

[Trudy Claspill]

Hello @Sjoquist, Carl 

Per an Atlassian team member comment in 2016 on this issue, this is how Jira sets the issue type field when you create a new issue:

1. Most recently used issue type in user session
2. Default issue type in the issue type scheme
3. Ordering of issues in the issue type scheme

Based on that, the Create Issue dialog will not keep setting the Issue Type field back to the specified default in the Issue Type Scheme associated with the project, in a single user session.

[Sjoquist, Carl]

Ah, that clever Jira!   Thanks Trudy!  Nice cat!

[Sjoquist, Carl]

I tested now and it unfortunately does not take the "default issuetype" per issuetype scheme.   After logging out, back in again, it still defaulted to Story on my Create.   Hmmm, not what my users wanted, but oh well.

[Trudy Claspill]

It may be recorded in the browser cache...?

[Sjoquist, Carl]

Thanks Trudy, I had a look at cookies from Atlassian but didn't see anything obvious related to this.   My guess would be they implemented this as a user preference, so it doesn't depend on the browser that the user happens to use.