-
Bug
-
Resolution: Not a bug
-
Medium
-
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
-
JRASERVER-15213 Sometimes the default Issue Type is not set correctly when creating an Issue.
- Closed
-
JRASERVER-44026 Default Issue Type is being ignored
- Closed
- is related to
-
JRASERVER-40898 Default Issue Type - value from Issue Type Scheme is not used.
- Closed
- relates to
-
JRACLOUD-30620 Setting Default Issue Type to "None" Ignored
- Closed
-
JSWSERVER-11749 Inline issue creation should use the default type from the Issue Type Scheme
- Closed
-
JRASERVER-13048 Allow 'No default' for Priority
- Gathering Interest
- blocks
-
PS-74736 Loading...