slaesvuo/hledger
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

;doc: ISSUES: edits

Browse Source
This commit is contained in:
Simon Michael 2023-12-12 19:01:30 -10:00
parent 766faf5c1e
commit 0646218205
1 changed files with 15 additions and 15 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

30
doc/ISSUES.md
View File

@ -147,27 +147,27 @@ What adaptation of it might work for the hledger project ? Eg (WIP):
**Type (What type of bug is this?)**
5: Crash or data loss or privacy/security loss.
4: Major usability or documentation issue.
3: Minor usability or documentation issue.
2: Installability or packaging issue.
1: Localisation or internationalisation issue.
- 5: Crash or data loss or privacy/security loss.
- 4: Major usability or documentation issue.
- 3: Minor usability or documentation issue.
- 2: Installability or packaging issue.
- 1: Localisation or internationalisation issue.
**Priority (How will those affected feel about the bug?)**
5: Blocking further progress on the daily build.
4: A User would return the product. Cannot RTM. The Team would hold the release for this bug.
3: A User would likely not purchase the product. Will show up in review. Clearly a noticeable issue.
2: A Pain – users won’t like this once they notice it. A moderate number of users won’t buy.
1: Nuisance – not a big deal but noticeable. Extremely unlikely to affect sales.
- 5: Blocking further progress on the daily build.
- 4: A User would return the product. Cannot RTM. The Team would hold the release for this bug.
- 3: A User would likely not purchase the product. Will show up in review. Clearly a noticeable issue.
- 2: A Pain – users won’t like this once they notice it. A moderate number of users won’t buy.
- 1: Nuisance – not a big deal but noticeable. Extremely unlikely to affect sales.
**Likelihood (Who will be affected by this bug)**
5: Will affect all users.
4: Will affect most users.
3: Will affect average number of users.
2: Will only affect a few users.
1: Will affect almost no one.
- 5: Will affect all users.
- 4: Will affect most users.
- 3: Will affect average number of users.
- 2: Will only affect a few users.
- 1: Will affect almost no one.
**User Pain = Type * Likelihood * Priority / Max Possible Score**