━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
These are our behaviour expectations of the behaviour that we expect from every single Bug Squasher addition to the server rules and expectations of Bug Hunters:
Work from top to bottom/least recent to recent in the queue.
Discuss with squashers and above whether a bug should be approved or denied.
When asking a Bug Hunter for more information or clarification it is done in a respectful and friendly manner.
Check attachments before adding them. Ensure there are no invites, sensitive information, or offensive language.
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 Moderator or Bug Admin know.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
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:
Is the bug report valid?
1. Does the information check out?
2. Not on the unsupported list?
3. Is it too minor?
Is the bug report a duplicate of an already reported bug or already in the queue?
Test the bug with the information on the report.
If reproducible, add an approval, if not then add a denial
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
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 British Army Testers get denied but can be redirected to the suggestions channel so they can ask to get it changed.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Urgent Bugs (P3)
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 appropiate staff member.
Examples:
Appropiate rank-indicating roles are not given in our Discord Server.
Permissions are given to those that shall not have them.
Can't spawn-in in our Roblox game
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:
Bailing out everyone does not update running jail-timers.
Helicopters refuse to spawn.
Can't verify with the bot to shortcut the discord command (c!xp username >> c!xp)
Not a Bug (NAB)
These are reports that include intended behaviour. If you are unsure if something is intended or not, ask your fellow Squashers toj see if they have come across this already or if there were previously denied bugs with that behaviour.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
It's fine if you don't immediately know what bug a P2 or P3 is. 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 below or ask others in chat.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Focus tests are small (or big!) tests our HICOM 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.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
As a Squasher you unlock a new set of commands that can be used to interact with the Bug Queue additionally to the same commands Bug Hunters can use. The following commands are only used in the approval queue.
`+approve` - When a Bug Squasher can reproduce the bug report in the queue.
`+deny` - When a Bug Squasher can not reproduce the bug, it is invalid, unsupported or not a bug.
`+revoke` - Removes the squasher's 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 BA Automation Bot Commands FAQ