-
Bug
-
Resolution: Not a bug
-
Medium (View bug fix roadmap)
-
None
-
5.1.3, 5.1.4, 5.2.9, 6.0.2, 6.2-OD-5, 6.2.2, 6.4
-
5.01
-
NOTE: This bug report is for JIRA Server. Using JIRA Cloud? See the corresponding bug report.
In order to force users select the correct Issue Type, is configured Default Issue Type as None, but when users click on create a new ticket Issue Type brings the last issue type selected instead of None, which means option None doesn't work as expected. If the user has never created a ticket before or just switched projects None will default to the top Issue type in the Issue Types for Current Scheme.
To reproduce:
- Login JIRA as Administrator;
- Navigate trough Issues >> Issue Type Scheme;
- Select None in Default Issue Type;
- Create an user;
- login JIRA with new user;
- Try to create an issue.
- is duplicated by
-
-
- Closed
-
-
-
- Closed
-
- is related to
-
-
- Closed
-
- relates to
-
-
- Closed
-
-
JSWSERVER-11749 Inline issue creation should use the default type from the Issue Type Scheme
- Closed
-
- Gathering Interest
- blocks
-
PS-74736 Loading...
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JRASERVER-30620] Setting Default Issue Type to "None" Ignored
2015:
"We will be removing the "none" option in a future release of JIRA in order to reduce confusion. From that point on, JIRA will default to using the first issue type in the issue type scheme as the default, and administrators can choose to set another issue type as the default."
I'm experiencing this in 8.21, which was released December 2021. The fact that it says Default: None but does indeed choose its own version of a default (a rule described above) is simply confusing. It's not behaving the way it should be based on its own words. I would call that a (outstanding) bug. Calling this "Not a bug" is very dishonest. If it weren't, the changes described wouldn't have been planned, right?
This is still a problem 8.13.4 - any status? Or please action on this one https://jira.atlassian.com/browse/JRASERVER-65439
Many thanks! 
In a large scale Jira Production, where there are already 10-20+ Issue types that is being use by different projects creating a new value "None" or "Unspecified" doesn't make sense and not necessary its like adding a redundant value to the Issue Type only to have an option to restrict the user to choose the correct issue type.
I have made some workaround by adding the "Unspecified" value and when the user use this value it will throw an error. One using Adaptavist script runner and one of our internal app but its not working this method is what I used in "Priority" field which has already a default "Unspecified" value and its working, I just don't understand why we can't implement it in the Issue Type field?
Has anyone found a workaround?
This is really bad. Forcing user to choose one is the right thing. It does not take anytime and it avoids lots of mistakes. Choosing the last settings does not make sense as chances are users creating both types randomly. It is a very common mistake that users create an issue with the wrong type simply because it is set to the last type chosen.
I am facing the same issue as well. Is there any solution for the same ?
Jira Software 7.11.2. Default issue types are being ignored.
Your classification of this as "not a bug" depends on your point of view.
Surely the solution would be to have a configuration option that determines whether the default issue type is enforced, or whether JIRA does the 'clever' thing of remembering the last type you used. Clearly some of your customers want one of those, some want the other, and some haven't thought about it.
I am running 8.20.11 and even though none is set as the default, it just remembers the users last picked issue type.