cle/docs
36
0
Fork 0
Code Issues 3 Pull requests Projects Releases Packages Wiki Activity Actions

Improve trouble labels documentation

Browse source 
* Update the times to what we are actually using
* Add story points conversion
This commit is contained in:
Michal Konečný 2025-04-10 11:36:26 +02:00
commit deaab2bf19
1 changed files with 25 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files

29
modules/ROOT/pages/glossary.adoc
View file

@ -13,12 +13,33 @@ the last).
Here is an idea of what each level corresponds to:
Low trouble:: easyfix that we know how to do, is documented and doesn't take
more than a few minutes.
more than a day.
Medium trouble:: something that is (or sounds) doable, requires a little
investigation work but should not take too long (done in a day max).
investigation work but should not take too long (done in a week max).
High trouble:: something that we have never done before and will require
some investigation work and impact analysis before we can get started on it or
something we know but will take more than a day to do properly.
more investigation work and impact analysis before we can get started on it or
something we know but will take more than a week to do properly.
[NOTE]
====
Trouble labels are being converted to story points in
link:https://issues.redhat.com/projects/CPE/issues[CLE JIRA project]. Story points
are representing the complexity of the issue and being used for deciding the capacity
of the team. The labels are being converted to story points based on following table:
[cols="1,1,1,1"]
|===
|
|Low trouble
|Medium trouble
|High trouble
|Story points
|1
|5
|10
|===
====
Low gain:: we have done without fine until now, it impacts very few people
and has a work around available.