From 7d25ab43e3bd1368d9d30a06014ab8b9970fe217 Mon Sep 17 00:00:00 2001 From: Jeremy Stretch Date: Fri, 23 Jun 2023 09:44:36 -0400 Subject: [PATCH] Updated Issue Intake Policy (markdown) --- Issue-Intake-Policy.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/Issue-Intake-Policy.md b/Issue-Intake-Policy.md index 598c73d..3eb8f2d 100644 --- a/Issue-Intake-Policy.md +++ b/Issue-Intake-Policy.md @@ -58,7 +58,8 @@ This page serves to define the official policy for opening and processing GitHub 1. If the reported behavior is considered normal, apply the `BUG_EXPECTED_BEHAVIOR` canned response and apply the `status: revisions needed` label. 3. Attempt to replicate the reported bug on the current NetBox release (i.e. the `master` branch) by performing the steps detailed in the issue. 1. If you are unable to reproduce the reported error or behavior, apply the `BUG_UNABLE_TO_REPRODUCE` canned response, and optionally ask for further clarification on how they encountered the reported issue. Also apply the `status: revisions needed` label. -4. Assuming you are able to successfully replicate the reported issue, apply the `type: bug` and `status: accepted` labels. +4. Determine the severity of the bug, if possible, and apply the appropriate `severity:` label (high, medium, or low). +4. Assuming you are able to successfully replicate the reported issue, apply the `type: bug` and `status: needs owner` labels. 5. If there are external factors preventing you from testing the reported issue (such as another bug interfering with testing), apply the `status: blocked` label and leave a comment explaining why. # Canned Responses