I'm curious what kind of issue types people are using other than the standard four.
I know there's no limit to it, but is it best practice to keep it simple? Any downside to having too many?
It really depends on the team. We make up issue types as needed. Some examples:
Server Build
Workstation Deploy
Employee Onboarding
Employee Offboarding
Server Refresh
Problem
Support Request
Question
Issue
etc....etc....etc...
You can make the issues types that work for you depending on the needs of the team/project.
We're using "what ever we need". Incident, bug, request, improvement, new starter, holiday request, question, sales call, the list is endless.
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.