Added in internal bug reporting documentation.
2/4
threads resolved
mentioned in issue minds#994
added scoped labels
approved this merge request
- Resolved by Ben Hayward
- Resolved by Ben Hayward
- Last updated by Ben Hayward
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. 22 3. Discussion should be had on the issue card once others attention is gained through Zulip. - Developer
*others'
changed this line in version 3 of the diff
approved this merge request
2 id: bug-reporting 3 title: Bug reporting 4 --- 5 6 ### Reporting a bug 7 Outlined below is our reporting process for incoming bugs. 8 9 #### Community members 10 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). 11 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. 12 13  14 15 #### Team members 16 17 Firstly, assess the priority of the bug to the best of your abilities. - Developer
"Firstly" Heh.