Added in internal bug reporting documentation.
Request to merge
chore/bug-reporting-docs
into
master
0/1
thread resolved
mentioned in issue minds#994
added scoped labels
approved this merge request
6 ### Reporting a bug 7 Outlined below is our internal reporting process for bugs. 8 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). 9 10 ### Prioritizing 11 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. 12 13 ### Normal issues 14 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. 15 2. Give the card a `Type::Bug (Triage)` label, do not add any others. 16 3. Make a new topic in the Bugs stream on Zulip, link the Gitlab issue in there, tag the `@BugTeam`. 17 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. 18 19 ### Urgent / Unsure 20 1. Follow the steps laid out in the above section. 21 2. Tag `@Developers` and `@BugTeam` in Zulip. ![Brian Hatchet](data:image/svg+xml,<svg xmlns="http://www.w3.org/2000/svg" width="200" height="200"><rect fill-opacity="0"/></svg>)
DeveloperNo redirecting conversations to zulip.
![:speech_balloon:](data:image/svg+xml,<svg xmlns="http://www.w3.org/2000/svg" width="64" height="64"><rect fill-opacity="0"/></svg> ":speech_balloon:"){kind=small}