Inconsistent default issue type behaviour when Enhanced backlog is enabled

Issue Summary

We document here how the default issue type setting is meant to work:
https://confluence.atlassian.com/jirakb/how-to-change-the-default-issue-type-displayed-at-the-create-issue-screen-when-a-user-creates-an-issue-for-the-first-time-in-a-specific-project-707986896.html

This entire setting seems to be meant to apply only to the first time a user logs in. Subsequently, when creating an issue, Jira Cloud will show the issue type selected by the user when they last created an issue. This behaviour has changed in the Enhanced backlog and board making the issue-create behaviour inconsistent. If you create an issue using the Create button in the top nav bar, it will continue to display the most recent issue type the user selected.

If, however, you create an issue by going to the backlog and clicking "+ Create issue" and the default issue type is set to None, the user story issue type is shown instead.

Steps to Reproduce

1. Enable the Enhanced backlog
2. In a company-managed project go to Project Settings > Issues > Types and select Actions > Edit issue types
3. Make sure there is some non-None value in the "Default Issue Type" dropdown. I chose the issue type "Ask a question":
   
4. Go back to the project's board. Click the Create button in the top nav bar. Observe that in the issue Create screen, the selected issue type matches the type of the issue you last created. Mine was "Story":
   
5. Go to your backlog and click "+ Create issue". Observe that the issue type matches the one selected in the issue type scheme ("Ask a question"):
   
6. Disable the enhance backlog and click "+ Create issue" again - observe that the issue type is "Story"

Side note: If you select "None" as the "Default Issue Type" in your Issue Type Scheme the backlog issue create defaults to Story.

Expected Results

Consistency in behaviour from all issue creation methods in terms of default issue type. When "Default Issue Type" has a value, all issue create methods should respect it. When "Default Issue Type" has no value, the issue type of the last issue created should be used.

Actual Results

Inconsistent in behaviour from the top-nav bar Create button and issue creation methods on the Enhanced board and backlog

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available