When an issue is created inline in the JIRA agile Backlog view (little '+ Create' under a sprint or backlog), the default issue type seems to be the the first in alphabetical order, and not the default issue type of the project. Is there a way to change the default issue type?
As the backlog shows only an icon and not the issue type name inline, it's not easy or intuitive for users to change the issue type.
The current alphabetical default leads to situations, where backlogs are full of Bugs, when they should be full of Stories or Tasks or whatever issue type the team uses by default.
So someone has an answer for this issue? I am having the same problem :-(
After lots of searching i Got the answer , We need to reorder the Issue types for the Current Issue type scheme and it would default to based on the order.
Reorder the Issue Types for Current Scheme to place the Issue type you would like to display as default right on top of the order
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Same issue here. Changed default to story, but Jira always has Task as a preferred option. Frustrating... :(
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
For me, the default is Story and I want my default to be Task. So, can we trade problems?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Markus,
you cannot specify which should be the default issue type. The create remembers you last choice of issue type and that is what is being used.
Cheers,
Peter T
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
No, it doesn't. I only create stories under epics and when I am in the backlog and click create under an epic, it creates a task, not a story.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.