From 57af861899dbdcc3da3cbc303342b4255134ad89 Mon Sep 17 00:00:00 2001 From: David Date: Wed, 1 Feb 2017 16:07:35 +0100 Subject: [PATCH] New sub labels for bugs and features. --- Issue-Labelling.md | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/Issue-Labelling.md b/Issue-Labelling.md index dbe4e6f..797c26d 100644 --- a/Issue-Labelling.md +++ b/Issue-Labelling.md @@ -1,7 +1,13 @@ # Meaning of the Labels - **feature** - new end user functionality +-- **estimate/hours**, **estimate/days**, **estimate/weeks** - ballpark estimate for feature +-- **bug/P1** - High impact issue, must be updated daily, must be resolved before resuming milestone work +-- **bug/P2** - Issue is affecting users, should be resolved before resuming milestone work - **bug** - broken end use or developer functionality; not working as the developers intended it +-- **bug/P0** - Urgent issue that caused someone to be paged, must be updated hourly +-- **bug/P1** - High impact issue, must be updated daily, must be resolved before resuming milestone work +-- **bug/P2** - Issue is affecting users, should be resolved before resuming milestone work - **techdebt** - unpleasantness that does (or may in future) affect development - **chore** - refinement / improvement of end user or developer functionality, or new developer functionality - **dogfood** - important for the developer's own use of the project @@ -22,7 +28,7 @@ NB: suggestions for refining the above explanations based on edge cases / exampl There are a few guidelines to follow when labelling issues: - every issue should be labelled with exactly one of 'feature', 'bug', 'techdebt', 'chore' (aka "category labels") -- apply other labels as appropriate; avoid attaching a large number of labels - that typically indicates that the issue should be split up +- apply other labels as appropriate (component, estimates, bug priority); avoid attaching a large number of labels - that typically indicates that the issue should be split up # Creating a new Label