current behaviour
- Initially, the inline issue creation in Agile board backlog pre-selects the issue type based on the alphabetical order of available types.
- After a user changes the issue type and creates an issue with it, the new default type will be cached in their browser.
- The new default type is retained until an issue with a different type is created, or the user clears their browsing data.
Example: in the applicable Issue Type Scheme, "Task" is the default type, but "Bug" is higher in the alphabetical order. In the inline issue creation, "Bug" will be the default issue type at first. If a user changes it and creates a "Task" though, it will be the default type from then on - until an issue of another type is created.
suggestion
Initially, the default type from the applicable Issue Type Scheme should be selected in inline issue creation. Afterwards, the type can be determined by previous usage the way it is now.
- is related to
-
JRASERVER-30620 Setting Default Issue Type to "None" Ignored
-
- Closed
-
[JSWSERVER-11749] Inline issue creation should use the default type from the Issue Type Scheme
sbostitch - this issue has actually now been resolved. JIRA Software Server 7.0 shipped with fixes to use the default issue type for each scheme if one is selected. Prior to this the inline issue create did not check this.
Once the user changes this selection that one will prevail and this is the designed and expected behaviour. This is stored in local storage and so will persist for that browser.
Kind regards,
Martin
JIRA Software
The "default type" behavior described here seems to be true of issues created from the Create button as well. That is, if the user preference for issue type is not set (is this preference really cached in the browser?) then the first issue created will use the default issue type, if one is specified. If no default is set then the ordering of issue types seems to prevail; the top one being selected (or is it really alphabetical?). Once a different issue type is created, and the user preference is set, this new type will prevail on all subsequent creates until the type is changed again. Thus, marking an issue type as 'default' in the issue type scheme doesn't seem to offer much functionality.
On its face, I would expect setting a type as default to override the user preference setting. If it did work that way, it doesn't seem like there would be any loss of functionality from what exists now. Projects not wanting such behavior would simply not set a default and then would put the preferred issue type at the top of the order for those cases when a user preference was not set. Or am I missing something?
Thank you mjopson. I appreciate you taking the time to reply. I should probably create a different issue altogether. I got here from
JRA-30620which I came across after researching a question about default issue types which was raised during a demo of JIRA cloud that I gave the other day. I have to admit that I had not thought much about the previous behavior before this question and so I think I may have misunderstood this suggestion somewhat.As mentioned in the comments of
JRA-30620, I would expect default issue types to always override user selections. That is what I was proposing in my previous comment. I will search again for an issue dedicated solely to that request and open one if needed.Keep up the great work.
Cheers,
Nathanael