Setting Default Issue Type to "None" is not working

[siva kedari veerla]

In my Issue Type Scheme i have the Default Issue Type set to 'None' but when I go to create a new issue the default is not blank as I would expect.

[John Funk]

Hi Siva,

Is the field required? If so, I don't think it will allow you to default to None. 

If not required, maybe take off any default and see what it goes to. My experience is that it will default to the None. 

All of this is assuming that None is not an actual answer that you created. 

[siva kedari veerla]

Hi John,

The current Jira behavior is that the default issue type will only work for the first time when the user login and try to create a new issue. Once a user has created an issue in a project, JIRA retains the issue type from the previous issue any time the user creates a new issue. This is intended to make it easier for users to quickly create issues.

But providing the Default Issue Type option is of no use because of the above feature. 

[John Funk]

Sorry, but I misunderstood your original question. I failed to see it was about Issue Types and not custom fields. 

So, having said that, I go back to my first comment above about the field being required. If a field is required, and Issue Type is, then there will ALWAYS be a default value. The Create mode will never have None in the value since the field is required. 

If you set a default value (other than None), Jira should always respect that value and not just use the previously used one. 

[James Cope]

Here's an idea whose time has come. How about (and this is strictly -- and sarcastically -- hypothetical, we be allowed to have the issue type UNSET so as to require the user to select one during creation. Once that happens, we can then use the field configuration to require the field (which is required by default because an issue type is required for a ticket to exist the same as a Summary or a ticket number) which will then require that the user actually make a conscious selection when creating a ticket.

I don't think the server product behaved like this and I vote that we restore some sanity to functionality. But who am, right?

[jd_santos]

@James Cope Came here looking for a solution. I'm not sure how I'm supposed to encourage an active selection of the Issue Type when the default is there.

Sure I can use a Transition condition, but that just leads to confusion about why certain transitions aren't available. 

I can't use the "Field is blank" validator because the field can't be blank.