Hello,

This issue is a variation of the following issue https://jira.atlassian.com/browse/JRA-30620 and will be track on the above link.

Therefore we have closed this issue as a duplicate.

Thanks,
Ben Magro - JIRA Service Enablement

I can add that I found one work-around that seemed to fix it, which is to remove the problem issue type (Bug in my case) from the list, create a new issue, which will now have the correct issue type because the problem issue type isn't even available, then re-add the problem issue type. I also made sure not to put the problem issue type at the top of the list. Not sure if that mattered (don't think it did). At least in my brief testing, this caused JIRA to stop grabbing the wrong issue type. I haven't yet tested this to know for sure if the problem will recur, or if this is a permanent fix for this project.

Confirmed that this bug also occurs in 6.3.13 under the same conditions defined under "Steps to Reproduce". I have not updated to a newer version to confirm beyond 6.3.13, but if not explicitly fixed, I would be concerned that this is still an active bug.

I don't think this should be tagged as minor, because it's important functionality. If users are not actively going through and setting fields, this bug in the JIRA code causes new issues to be logged as Bugs (the wrong default issue type) instead of Stories (the default issue type set in our scheme). This is serious. Please upgrade the severity of this bug.

This is the context within which I could reproduce this issue:
steps to reproduce
(requires atleast 2 projects with different Issue Type Schemes and different Issue Type defaults):

• Create projectA, with IssueTypeSchemeA and default Issue Type TypeA, as well as, projectB, with IssueTypeSchemeB and default Issue Type TypeB
• In a fresh user session, select ProjectA and then try to create an issue
• projectA and it's default issue type (typeA) will be selected on the create issue screen. go ahead and create an issue with this settings.
• Then select another projectB, and go back to create issue screen.

Expected Behaviour
The currently selected projectB will be selected in the Create issue screen, with it's own default IssueType TypeB

Actual Behaviour
The currently selected projectB will be selected in the Create issue screen, but the Issue Type field will recall the last selected Issue Type in this session (which was selected when creating an issue under another project having a different IssueTypeScheme in this case TypeA). Except of course that typeA is not available in the IssueTypeScemeB, in which case it reverts back to ProjectB's default issue type.

Using my own data, I observe the following behaviour when I first log in to JIRA:
If a browse a project "ProjX", then select "Create new Issue", JIRA defaults the project to ProjX, and because there was no "last selected Issue Type", it defaults the Issue Type to ProjX's default Issue Type.

However, this does not work when using the data that the customer supplied.
They browse their project, and select "Create new Issue", JIRA defaults the the project correctly, but does not set the Issue Type to the Project default, rather it is initialized to the first value in the issue type drop down.