-
Suggestion
-
Resolution: Unresolved
-
85
-
85
-
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
-
- Closed
-
- Closed
- is related to
-
JRACLOUD-79915 Issue type is not reset to the default one when creating ticket in a new session
-
- Closed
-
-
- Closed
- relates to
-
-
- Closed
-
- mentioned in
-
Page Loading...
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JRACLOUD-74771] Default issue type additional option to not use session (last used)
+1 my users constantly complain that they have to change the issue type. Story should always be the default, independently from what was created last. Or at lest make this configurable in the project...
Why not just sort out the Issue Types on the drop-down as it's done for Custom Fields with drop-down lists? This could be associated to the projects Issue Type Scheme.
+1
What's the sense of this Setting if it only applies once when the user creates the first ticket.
Default issue type should be applied to the creation screen for all attempts of creation.
Default issue type functionality should be enforced for each Create action in for the configured issueType, regardless of last issue type selected or the session, if project is configured to use this feature. This would make this a meaningful and helpful feature.
There should, however, be an option for those who would prefer "last issue type used" (current functionality) to be persisted if they do not want "Default issue type" functionality to prevail for each new ticket created.
I would also suggest solving this issue as it does not seem to be a great effort.
I would highly prefer "default issue type" to be for every new issue created. With how it is now, there isn't even a point of having it as a setting.
This feature request is 3+ years old?
The current behavior is maddening. If the system lets you set a default issue type, it should respect that selection.
I echo the same reaction as Suzanne Raphael's post on Mar 2023. I felt the same. The default issue type on Issue Type Scheme is misleading me that I can set a default value when this default only works for the 1st time the user logs into Atlassian ever. What's the point to have this default if it only works once in the life journey! Please consider to allow a default issue type set up in the issue type scheme to work on Create Issue screen and only use the "Last Used" when there's no default value set for the issue type scheme.
OH. MY. GOD. I SO concur...I just spent a half hour trying to figure out why the default issue type seemed to be stuck on BUG. This is SO DUMB. Is it a default, or IS IT NOT A DEFAULT? Seriously, why would you want to set a default for ONE MOMENT IN TIME EVER?
I also suggest some info at the top of the page that explains clearly what they do. E.g.:
When creating a new issue which issue type that is automatically selected is determined by both the “Default issue type” dropdown and the "Re-use the previously selected issue type" checkbox.
- When the checkbox is not checked
-
- The value in the "Default issue type" dropdown will be used
- When the checkbox is checked
- The first issue created after logging in will use the value from the “Default issue type” dropdown, as there are no previously selected issue types saved in the user session
- After the first issue is created, any subsequent issues created will use the selected issue type from the previously created issue, including the issue type selected in the first issue created
The suggestion makes the most sense to me, however I could see using the "last used" Issue Type on the "Create Another" feature. "Create Another" seems like the sequence that would be used most in brainstorming, testing, or elaboration sessions and that's where you want to rapid-fire a lot of issues. Using the generic "Create" button on the form should respect the project settings as described above.
The current behavior results in a lot of issues reported as bugs instead of improvements or vice versa, based on whatever that user did the last usage. The users enter these issues as they come across them either by usage problems (bugs) or inspiration (improvements). Erroneous entries impact our triage effectiveness and responsiveness. In our case, we would set the default to "None" but make the field required. The user would have to at least choose between these two options, and we may re-categorize upon triage.