Ben Hayward · @benhayward.ben
--- a/docs/handbook/bug-reporting.md
+++ b/docs/handbook/bug-reporting.md
+Outlined below is our internal reporting process for bugs.
+Users should instead report their bugs through [Help and Support](https://www.minds.com/groups/profile/100000000000000681/feed) or [Report a Bug](https://www.minds.com/issues/report).
+
+### Prioritizing
+Ignore any urgency labels. These labels will be assigned by Ben, or Brian, this will allow us to effectively sort through bugs and prioritize them accordingly. If you believe the issue is severe enough to warrant the triggering Superhero then skip to the Superhero header below.
+
+### Normal issues
+1. Make a card - fill out the bug template fully, if for any reason you cannot or don't understand what is happening, start a fresh Zulip topic in the Bugs stream with an appropriate title and tag @BugTeam.
+2. Give the card a `Type::Bug (Triage)` label, do not add any others.
+3. Make a new topic in the Bugs stream on Zulip, link the Gitlab issue in there, tag the `@BugTeam`.
+4. If the issue seems to fall between the cracks, which can happen at busy times. Re-tag `@BugTeam` or direct message one of us.
+
+### Urgent / Unsure
+1. Follow the steps laid out in the above section.
+2. Tag `@Developers` and `@BugTeam` in Zulip.
+3. Discussion should be had on the issue card once others attention is gained through Zulip.
--- a/docs/handbook/bug-reporting.md
+++ b/docs/handbook/bug-reporting.md
+id: bug-reporting
+title: Bug reporting
+---
+
+### Reporting a bug
+Outlined below is our reporting process for incoming bugs.
+
+#### Community members
+Community members can either [create a new issue](https://gitlab.com/minds/minds/issues/new), report it through [Help and Support](https://www.minds.com/groups/profile/100000000000000681/feed) or [Report a Bug](https://www.minds.com/issues/report).
+If you would like to to create your own card, please tag a team member to assign labels for you, and use the `bug` template next to your issue title to help us validate your issue.
+
+![GitLab Bug template](assets/bug-template.png "GitLab Bug template location")
+
+#### Team members
+
+Firstly, assess the priority of the bug to the best of your abilities.
--- a/docs/handbook/bug-reporting.md
+++ b/docs/handbook/bug-reporting.md
+Firstly, 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 then skip to the Superhero header below. Urgent bugs are lesser than superhero, but still need immediate attention. Keep in mind that urgent issues disrupt the current plan from the sprint and require immediate attention from a developer.
+
+##### Normal / High Priority issues
+
+1. 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.
+2. Give the card `Type::Bug (Triage)` and an appropriate priority label.
+3. 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.
+4. If the issue seems to fall between the cracks, which can happen at busy times, feel free to contact developer chat.
+
+##### Urgent / Unsure
+
+1. Follow the steps laid out in the above section, but give the issue an urgent label.
+2. Message the Bug Team through developer chat to alert them to the issue.
+3. Discussion relating to the issue directly must be had on the issue card. Developer chat should be reserved for internal coordination.