Hi @P At ,
A good ticket will depend on business case. What you have listed is a great start.
Overall Guideline:
- Keep it simple - Stay with system fields unless there is no system field that can help. Too many fields may confuse the end user and make it difficult for them to fill it out.
- make sure every field provide a value like measuring, reporting, and provide info on what the ticket is about.
- You may need a field to distinguish the ticket for searching. In your case, maybe a field to distinguish the type of web base training.
There should be a priority field available to add to your issue screen. Then you can select option like high.
Impediments is a flag to let users know that the ticket is blocked. It means that item can't be worked on until that impediment is removed. For example, the training demo environment is down.
Hope this helps.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.