🚧 Help center article under construction! 🚧
What does this FAQ cover?
This is a short guide on what we expect Bug Hunters to do within the server and how to become one. To learn more about the server, please check the Bug Hunter FAQ.
Bug Hunting Guidelines
We want Discord Testers to be a fun and safe environment where you can help each other and Discord out.
These are our expectations of the behavior that we expect from every single Bug Hunter in addition to the server rules:
- Read the report fully before trying to reproduce it. (If it says "Only occurs on Android 4.1.2" and you try to reproduce it on Android 6, that's an invalid repro.)
- Always include all of your device info (device name, OS version, Discord version, etc.) when interacting with a report.
- It's common that a bug can happen in multiple locations. If this happens, there should only be one ticket and the other locations added as a canrepro.
- Buying or selling bugs is strictly prohibited.
- Abide by all Discord Terms of Service and Community Guidelines
- Check https://bugs.discord.com/ and the approval queue before you submit the bug, to avoid duplicates bug reports.
Note: If you believe someone is violating our Community Guidelines or Terms of Service, directly contact our Trust and Safety team at https://dis.gd/request immediately.
Steps to start submitting bugs
To become a Bug Hunter and start your bug-catching adventures you should follow the next steps:
- Read the introduction articles on the server and the server layout.
- Take the quiz by sending !quiz to DBug.
- Add the roles of the platform you use, dm DBug !role list.
- Write up your bug submit command.
- Submit it in the reporting channel of the platform you have a bug for.
Before submitting a bug report, make sure it is not listed as one of the unsupported report types or a duplicate of another bug report. You should be checking the #approval-queue, reporting channels in Discord Testers as well as https://bugs.discord.com.
Note: if you have a video or image to add to your bug ask one for it to be added to the bug report in the platform client chat. Bug Hunters can not add these themselves.
Want to know how to write a bug submit command? Check out how to report a bug FAQ.
As a Bug Hunter, you have access to submitting a bug report or adding can (not) reproduce information. Additionally, you can add platform roles to yourself
!role list - Used in DMs with DBug to see which platform roles are available.
!submit - As a Bug Hunter, you can submit bug reports to the server just like any other user that has a role with access to the server.
!edit - If you need to edit your bug report in case you found an error or forgot to include information.
!cr / !canrepro and !cnr / !cantrepro - Bug Hunters can add a "can repro" or "can not repro" to an approved bug report. This gives the developers more insights on whether this happens for everyone or on specific devices/systems.
!info store [option] - Stores your system information for faster bug reporting
!info check - Displays your currently stored information
Information on how to use these commands is found in DBug Bot Commands
Passing the quiz does not give you a badge, nor does it automatically give you access to any features that are in testing. When you have passed the quiz you are tier 1, a Bug Hunter. As you contribute to the server, you will level up.
To become a Bug Squasher you will need to report bugs and they have to be fully approved. Which is 3 approvals from squashers. We know that waiting is not fun but everyone on the server is a volunteer and reports get checked when the users get to it. Don’t ask users to look and test your bug report. There is no estimate on how fast this will be.