/
Ticket Standards

Ticket Standards

Each ticket that's created needs to have some required information to be considered ready to be worked on. Anyone can create a ticket when coming across issues so these issues aren't lost. However if you cannot fill this out fully please make sure to discuss with others before adding the ticket.

 

  • What's wrong

    • What is the feature or hotfix that needs to be created/fixed.

    • Why this is causing issues

  • What done looks like

    • How things will be working once the ticket is completed.

    • A list of noticeable changes that are expected from the ticket

    • Any details in how changes are expected to look and act

  • Where the changes need to be made

    • The file name where the bug is located

    • What part of the application the feature should be added to (Adding in a file name if its not a new component)

    • A list of known file names that are affected by an application wide change

Related content

Branching Strategies
Branching Strategies
More like this
PR/Merging Standards
PR/Merging Standards
More like this
Coding Best Practices
Coding Best Practices
Read with this
Meetings
More like this
Stand Up Meetings
Stand Up Meetings
Read with this
Scrum Overview
Scrum Overview
Read with this