Our customers are creating issues with incorrect issue types, because the system is providing a default value on creation (apparently the last issue type they used?), which they do not change. Should be simple right? Apparently not simple enough. We've got bugs as new features, and new features as tasks.
We would like the ability for the issue type to be empty, or none to start, and force them to pick an issue type before they can finish creating the issue.
Any ideas on how to accomplish that?
Hi Matt, have you tried changing the Issue Type Scheme and select the default one to 'None'?
Yes, I tried that. It doesn't seem to have any effect when I create new issues. The issue type is still being populated (in my case by "new feature").
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Well this is not a possible feature on the Jira core, and I'm not sure if there is any plugin for this. I'll do some research since I'm curious about this... Maybe doing some coding to the field.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I have the issue type defaulted to "None" but it always defaults to the previously opened issue type. I would like to find a way to force the user to select an issue type at every creation. Any suggestions?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.