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?
Hey Community mates! Claire here from the Software Product Marketing team. We all know software development changes rapidly, and it's often tough to keep up. But from our research, we've found the h...
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!
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