Forcing a JIRA issue type to be manually selected on creation

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?

1 answer

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").

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.

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?

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Jan 08, 2019 in Jira

How to Jira for designers

I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...

1,084 views 4 9
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you