Create checklist for issue triage
The documentation for issue triaging has grown organically and now contains a lot of useful information in several places. The Contributor Success team spends significant bandwidth triaging issues. This effort will grow 1-2 orders of magnitude as the number of contributions increases. To help with this, let's consolidate the issue triage guidelines into a single, complete checklist containing step-by-step instructions for how to triage issues. As Wikipedia says: A checklist helps reduce failure in repetitive tasks by compensating for potential limits of human memory and attention. It helps to ensure consistency and completeness in carrying out a task.
-
create a spike of how this consolidated checklist setup could look like: gitlab-com/www-gitlab-com!118187 (closed) -
remove issue bash events: gitlab-com/www-gitlab-com!118240 (merged) -
create an MR for an initial checklist: gitlab-com/www-gitlab-com!118364 (merged) -
merge the TextBlaze templates -
merge the partial triage section on the "issue triage" handbook page -
merge the Community issues workflow manual process section on the "Contributor Success Team" page -
merge the triaging issues section on the "issue triage" handbook page -
merge other parts of the issue triage page contain plenty of additional things to keep in mind while triaging issues (some of it outdated or contradicting other parts) -
merge daily triage reports sent out by automation can contain instructions for how to triage as well -
add bug subtypes gitlab-com/www-gitlab-com!118364 (diffs, comment 1249917210) -
add "category" labels gitlab-com/www-gitlab-com!118364 (diffs, comment 1249917214) -
mention tanukistan -
gitlab-com/www-gitlab-com!118187 (comment 1246605990) -
update template for daily triage emails sent by triage-ops to link to this checklist -
one checklist for issues from team members and wider community members -
Merge places that talk about issue spam. -
move https://docs.gitlab.com/ee/development/contributing/issue_workflow.html#severity-labels into the Issue Triage
Edited by Kevin Goslar