-
Bug
-
Resolution: Not a bug
-
Medium
NOTE: This bug report is for JIRA Cloud. Using JIRA Server? 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
-
- is related to
-
-
- Closed
-
- relates to
-
JSWCLOUD-11749 Inline issue creation should use the default type from the Issue Type Scheme
- Closed
-
- Reviewing
- mentioned in
-
Page Failed to load
[JRACLOUD-30620] Setting Default Issue Type to "None" Ignored
Most likely not gonna change anything, but i'm adding a +1. Forcing user to select an issue type every time when creating a new Jira will actually makes things a lot more efficient, at least at my company.
+1 Completely agree. I really want to be able to force users to select the issue type. I make that mistake myself all the time, creating stories, when I meant to create tasks or epics because it does not prompt me. With custom issue types and workflows it's even worse.
Even it does not work when switching between the projects which have different default issue type set, which I guess is a bug.
+1 this way the default issue type option losses its true meaning and is useless.
+1 A wrong issue type generates in most cases a delay so we really would like to force the people to select the right issue type.
+1