Bug triage
From MoodleDocs
Note: This page is for analysing and developing a bug triage process. It is a work-in-progress. Comments or suggestions are welcome! Please use the page comments.
Triage is medical term referring to the process of prioritizing patients based on the severity of their condition so as to maximise benefit (help as many as possible) when resources are limited.
Bug triage is a process where tracker issues are sorted and categorised. It should help ensure we appropriately manage all reported issues - bugs as well as improvements and feature requests.
The triage process
Step 1 - Issue details check
- Perform housekeeping, fix spelling, remove duplicates and spam
- Update priorities/assignees/components/descriptions/statuses
- If necessary, request more information
Step 2 - Setting a fix version
- If the issue is a bug in the current stable version (eg 2.0), assign "Fix version" as STABLEBACKLOG
- If the issue is related to backup and restore, assign "Fix version" to STABLEBACKLOG with high priority
- If the issue is a bug in the current stable version requiring database changes, assign "Fix version" to DEVBACKLOG
- If the issue is a feature request, assign "Fix version" to DEVBACKLOG
(List copied from Process)
Issues are then labelled triaged to indicate that step 1 and 2 have been completed.
Triage filter
The filter To triage (Moodle-all) includes:
- Issues with assignee to review (empty/nobody/moodle.com)
- Issues with fix version empty or set to some released version
- Issues not included in a backlog and not yet labelled as triaged
Triaging priorities
- Recent bugs
- By priority - aim for blockers and critical issues to be reduced to 0
- DEV sprint - focus on components of interest (currently forumng, survey, lesson and gradebook)
