-
Suggestion
-
Resolution: Unresolved
-
286
-
81
-
Problem
The "Default issue type" dropdown is only honoured when the user has not previously selected an issue type, so only works once after logging in.
It'd be useful to have a hard default that is always used with every new issue created.
The current functionality should be retained and be the default configuration, to avoid backwards compatibility problems and to avoid making one group happy at a loss to another.
Suggested solution
- Add a new checkbox underneath the "Default issue type" dropdown with the label: "Re-use the previously selected issue type"
- New checkbox checked by default to retain current functionality and BC
Outcome
- When checkbox is checked (and previously chosen issue type exists)
-
- The user's previously chosen issue type will be used
- Current functionality retained
- Backwards compatible
- When checkbox not checked (or previously chosen issue type doesn't exist)
-
- The "Default issue type" will be used
- New functionality gained for users wanting it
- The "Default issue type" wording is now a bit more accurate/meaningful
- duplicates
-
JRACLOUD-62990 Default issue type behavior options
- Closed
-
JRACLOUD-74525 Possibility to Set Default Issue Type as "None"
- Closed
- is related to
-
JRACLOUD-79915 Issue type is not reset to the default one when creating ticket in a new session
- Closed
-
JSWCLOUD-26419 Ability to set default issue type in team-managed projects
- Closed
- relates to
-
JSWCLOUD-25983 Inconsistent default issue type behaviour when Enhanced backlog is enabled
- Closed