default issue type not set, but jira is still picking an issue type when I create an issue (Jira 5.2.4)

Hi,

I want users to *not* get a pre-selected issue type when creating an issue -- I know it is a required field, but I want the initial selection to be "None" or "Please Select"... or something similar.

I don't have a default value set in the Issue Type Scheme.

Is there a way to do this? Seems like there should -- I don't want people picking incorrect issue types because they are automatically picked.

Thanks.

2 answers

1 accepted

Hi Bryan,

JIRA pick the last issue type the user have choosen. I'm afrid the only way we can modify it is via customization.

Best regards,
Lucas Timm

Okay -- they which velocity field do I tweak? I see information on how to remove None from a drop down -- but none saying how to enforce it.

Okay -- then do you know which velocity field I'd tweak? I see information on how to remove 'None' from a drop down -- but nothing saying how to enforce 'None' in a drop-down.

So in that case the default issue type field in the issue type scheme is pointless, right? I tried to do a workaround, so I created new issue type named "Unknown" with an empty screen (yes no field on it), set that as default. At first create issue action, the issue type Unknown will be used forcing the user to pick the issue type needed. Unfortunatelly, that works just once, because user will see last used issue type in the next "create issue" instead of default one!! So, as I said in the beginning, default issue type field it is pointless. This is a 100% application bug!

So in that case the default issue type field in the issue type scheme is pointless, right? I tried to do a workaround, so I created new issue type named "Unknown" with an empty screen (yes no field on it), set that as default. At first create issue action, the issue type Unknown will be used forcing the user to pick the issue type needed. Unfortunatelly, that works just once, because user will see last used issue type in the next "create issue" instead of default one!! So, as I said in the beginning, default issue type field it is pointless. This is a 100% application bug!

This is a really big problem for me. We filter issue types to different teams and right now people don't pay attention when creating the issue. Having a default type of None would solve this problem.

We also have this issue. Defaults are good but they also have users not paying attention and just accepting what is on the screen.

Suggest an answer

Log in or Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

3,317 views 14 20
Join discussion

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
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot