Thank you dmeyer for taking the time to reply. Clarifying the copy or calling this out in the online documentation would be great.

Hi sbostitch,

While the issues aren't identical, the rationale ends up being the same. JIRA will follow the existing order:

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

I do not anticipate that we will change this behavior, as it is key to supporting key features like creating multiple stories in a backlog or creating multiple bugs during a blitz testing session. I will speak to our designers about clarifying the copy on the issue type scheme management page to better indicate how JIRA will behave.

Regards,
Dave Meyer
Product Manager, JIRA Platform

Thanks ohernandez. However, as I commented above, I don't think this is the same issue as JRA-30620. This has nothing to do with a 'None' issue type or forcing users to choose an issue type. Exactly the opposite, actually. If a default issue type is set, new issues should default to it (in spite of user session settings). Please reconsider your resolution of this issue.

Cheers,
Nathanael

Hi all,

This has been reported before under JRA-30620, and the behaviour reported is by design.

Please do refer to our detailed explanation at https://jira.atlassian.com/browse/JRA-30620?focusedCommentId=755385&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-755385 for further details.

Regards,

Oswaldo Hernández.
JIRA Bugmaster.
[Atlassian].

mmuthusamy - it looks like you opened this issue and JRA-44027 around the same time. Dave Meyer closed JRA-44027 as a duplicate of closed bug JRA-30620. I would not say it's a duplicate, however. I recently commented on GHS-11749 (https://jira.atlassian.com/browse/GHS-11749?focusedCommentId=844467&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-844467). In lieu of creating a new issue I've decided to vote and comment here. I think the summary should be something like: "User session settings should not override default issue type". If Atlassian doesn't agree then the in-app wording and documentation should make it more clear that user session preferences will take precedence and that the default issue type functionality is therefore very limited in scope. Thanks.