From 3c9edcdd34bd3f2976afb7047f805bc555bee70a Mon Sep 17 00:00:00 2001 From: Simon Michael Date: Wed, 2 Apr 2025 15:08:36 -1000 Subject: [PATCH] ;doc:ISSUES: simplify user pain score again --- doc/ISSUES.md | 64 +++++++++++++++++++++++++++++++++++++++++++-------- 1 file changed, 55 insertions(+), 9 deletions(-) diff --git a/doc/ISSUES.md b/doc/ISSUES.md index 8513157e7..3d149821b 100644 --- a/doc/ISSUES.md +++ b/doc/ISSUES.md @@ -186,20 +186,66 @@ To people affected, how serious is this bug ? **User Pain** -The bug's User Pain score is **Impact * Severity * 4**, so ranging from 4 to 100. +The bug's User Pain score is **Impact * Severity** (1 to 25). Then, practices like these are possible: -- All open bugs can be listed in order of User Pain (AKA priority). -- Developers can check the Pain List daily and fix the highest pain bugs on the list. -- The team can set easy-to-understand quality bars. For example, they could say “In order to release, we must have no open bugs with more than 50 pain.” +- Open bugs can be prioritised in order of User Pain. +- The team can set easy-to-understand quality bars. For example, they could say “In order to release, we must have no open bugs with more than 15 pain.” - If there are no bugs left above the current quality bar, they can work on feature work. - If a bug is found that will take more than a week to fix, it can be flagged as a ‘killer’ bug, for special treatment.