Reporting a bug
Outlined below is our reporting process for incoming bugs. Incoming bugs go to the the Bug Triage board, where you can see the current status.
If you would like to to create your own card, please search existing issues to confirm that it is not already in the system, if it is, comment on the existing issue and let us know you are also experiencing it. If there is no matching issue, please create one using the
bug template next to your issue title. Once completed just tag a member of the team so that we can properly label your issue.
First, assess the priority of the bug to the best of your abilities.
If you believe the issue is severe enough to warrant the triggering of Superhero, take a look at the Superhero page. Urgent bugs are lesser than superhero, but still need attention from a developer as soon as possible. Keep in mind that urgent issues disrupt the current plan for the sprint and require immediate attention from a developer.
Normal / High Priority issues
- Search our GitLab for an existing issue, using keywords that describe the issue.
- Make a card - fill out the bug template fully if for any reason you cannot or don't understand what exactly is happening, contact the bugs team through developer chat and we will help.
- Give the card
Type::Bug (Triage)and an appropriate priority label.
- Diagnosis and triaging discussion should happen on the GitLab issue, if it ends up being talked about in a private chat, make sure information is relayed onto the card.
- If the issue seems to fall between the cracks, which can happen at busy times, feel free to contact developer chat.
Urgent / Unsure
- Follow the steps laid out in the above section, but give the issue an urgent label.
- Message the Bug Team through developer chat to alert them to the issue.
- Issues must be discussed on the card. Developer chat should be reserved for internal coordination. Any new information relating to the issue happening in live chats must be posted on the issue; it is the Single Source of Truth (SSOT) for the bug.