On create issue screen, the issue type always defaults to type of 'BUG'

[Paul Gallen]

On the Create Issue screen, the Issue Type always reverts back to type of 'BUG@, despite selecting another type. Obviously something not correct on our config, any help to point it out would be appreciated.

[Alon Erez]

It is a documented bug in version 5.0 ,resolved in 5.0.1

https://jira.atlassian.com/browse/JRA-27338

We have the same problem I intend to upgrade soon and test it.

Alon

[Cyril Egan]

Have you verififed that the 'Default Issue Type' is not set for your issue type scheme?

1. Login with administrator account
2. Go to Jira administration section
3. Go to 'Issue Types' area
4. Go to 'Issue Type Scheme' tab or click on the 'Issue Type Scheme' for your project(s)
5. Click 'Edit' opposite the relevant issue type scheme
6. Make sure the 'Default Issue Type' field is set to 'None'
7. Click 'Save'

[Paul Gallen]

Thanks for yor response Cyril. I can confirm that the 'Default Issue Type' field is set to 'None' and the problem still persists. Note - we are only using the default issue type scheme for the projects.

Any ideas?

[Renjith Pillai]

It also depends two other things. If it is the first issue you are creating after login, it shows the first one in the order in which you have sorted the Issue Types in the Issue Type Scheme. If you have created an issue in this login already once, it remembers the previous type used.

[Cyril Egan]

Is 'Bug' the first issue type in your default issue type scheme?

If it is then I suspect when the issue type scheme has the 'Default Issue Type' set to none that it is choosing the 1st issuetype in the scheme rather than the last one used.

What version of Jira are you using and what browser are you testing with?

[Paul Gallen]

Yes 'Bug' is the first issue type in the default issue type scheme.

Using JIRA version 5.0. On server, IE 7 is used, on client using IE 8.....

[Renjith Pillai]

So then sort the types in Issue Type Scheme to have your required one at the top.

[Cyril Egan]

I think the design is probably that Jira does not remember your last selection for issue type within the project eventhough it does for project. If this is the case then it would be an enhancement for Atlassian as they would need to implement some sort of cookie logic to do that.

A workaround might be to bookmark in your browser the create screen for the issue type you want in the project you want.

1. Click 'Create Issue'
2. Choose the project
3. Choose the desired issue type
4. Click 'Create'
5. Bookmark the resulting URL and give the bookmark a friendly name e.g. "New Task - Project X"
6. The resulting URL will be in the format below...

http://myjira.url/secure/CreateIssue.jspa?pid=9999999&issuetype=999&Create=Create

[Paul Gallen]

Hi Renjith.

The problem is not a case of having whichever Issue Type on top of the list. The problem is that when I drop down and choose another issue type other than the one that is shown, it keeps reverting back to the one that is shown, so becasue it keeps reverting back and wont keep my selected choice from the list, I cannot change the Issue Type on the Issue when creating it.

Cyril seems to be onto something and on the right track....

[Paul Gallen]

I think we are gone off track here. Surely to select any issue type from the available drop-down list (be it BUG, NEW FEATURE etc.), when creating an issue, and save the issue with that selected issue type - is something that must work otherwise all clients would have a problem. There is no problem with this on the edit issue screen and when evaluating the OnDemand version before our server installed version, we had no problem with this either.

Let me know if I need to clarify any further ....?