Bug Squashers+

Librarian
  • Updated

🚧 Help center article under construction! 🚧

What does this FAQ cover?

Expectations/Etiquette as a Bug Squasher

These are our behavior expectations of the behavior that we expect from every single Bug Squasher addition to the server rules and expectations of Bug Hunters: 

  1. Work from top to bottom/least recent to recent in the queue.
  2. Discuss with squashers and above whether a bug should be approved or denied.
  3. When asking a Bug Hunter for more information or clarification it is done in a respectful and friendly manner.
  4. Check attachments before adding them. Ensure there are no invites, sensitive information, or offensive language.
  5. Do not under any circumstance interact with troll/spam reports/bug stealing. If you happen to find one of these in the queue, let a Jr. Mod, Moderator, or Bug Admin know.

Reviewing bugs

Submitted bugs go through review by Bug Squasher and up. Interacting with the approval queue as a Bug Hunter is not possible.

Steps to reviewing bugs are:

  1. Is the bug report valid? 
    1. Does the information check out?
    2. Not on the unsupported list?
    3. Is it too minor?
  2. Is the bug report a duplicate of an already reported bug or already in the queue?
  3. Test the bug with the information on the report.
  4. If reproducible, add an approval, if not then add a denial.

Bug priorities

As a Squasher you’ll have to decide with your fellow squashers and up about which bugs are bugs and which are too minor. The bugs which are too minor for Discord Testers get denied but can be redirected towards https://dis.gd/bugreport.  

Determining bug severity

Urgent Bugs (P0/P1)

These are reports that impact the user experience negatively on a large scale and need an urgent fix. These reports should be flagged to a Bug Admin so they can get them fast-tracked to the appropriate staff member.

Examples:

  • Discord crashes when you send a message.
  • Uploading a file crashes discord
  • Can’t create channels

Less Urgent Bugs (P2)

These bugs still negatively impact the user experience, but they do not completely break the app. They will be fixed when a developer has time and do not require escalation to a Bug Admin.

Examples:

  • Disabling slow mode doesn’t update running timers
  • The sticker picker does not close when previewing a sticker pack
  • Typing an incorrect password when changing your username shows the error on other modals

Too Minor/Won't Fix (P3)

There are a lot of little discrepancies and issues that have a very low impact on the user experience in the app. These issues are not a priority to get fixed and should not be pushed to the bug website.

Examples:

  • Trying to block a deleted account says “Friend Request Failed”
  • When moving a server, the server shows up as if it’s in a folder
  • Categories in muted servers cannot be marked as read

Not a Bug (NAB)

These are reports that include intended behavior. If you are unsure if something is intended or not ask your fellow Squashers to see if they have come across this already or if there were previously denied bugs with that behavior.

Bug severity breakdown

It’s fine if you don’t immediately know what bug is a P2 or a P1. With time and with experience in the server it’ll be easier to recognize which priority a bug has. Until then you can look at the chart or ask others in chat.

 

Urgent

Less Urgent

Important

P0

P2

Less Important

P1

Too Minor/Won’t Fix

 

Focus Tests

Focus tests are small (or big!) tests our employees set up to test and receive feedback to new potential features or builds. It can range from new features to reworked code that needs to be tested to see if things don’t break when they get updated. Anything you see in them is still a Work in Progress and can change or be discarded prior to a public release.

Once a focus test is about to launch there will be a form to react to so we have an idea of which devices/platforms we have people testing on. Once the test is ready to launch you’ll be invited into the server and receive information on what is being tested.

These tests are private. Don't share or leak information or access.

Interaction with queue

We rely on you guys to help us filter through the incoming reports and push the important bugs. You'll do this by going through the queue and approving and denying the reports. Sometimes you'll attach an image or video to a report, to aid others on what a bug looks like.

The way it works: you discuss with other squashers and up whether a bug should be approved, denied or if it is a duplicate. After you’ve discussed the bug, you approve/deny. While doing that, you should not blindly follow others.

Squasher+ Commands

As a Squasher, you can use the same commands as Bug Hunters and additionally interact with the approval queue. The following commands are only used in the approval queue.

`!approve` - When a squasher can reproduce the bug report in the queue...

`!deny` - When a squasher can not reproduce the bug, it is invalid, unsupported or not a bug.

`!revoke` - Removes the approval or denial from the bug completely.

`!attach` - Adds an attachment to a bug report.

`!detach` - Removes an attachment to a bug report. 

Information on how to use these commands is found in the DBug Bot Commands FAQ

Related articles