[Development] Long-lived P1 issues

Oswald Buddenhagen oswald.buddenhagen at gmx.de
Tue Nov 3 15:50:27 CET 2020


On Tue, Nov 03, 2020 at 10:34:29AM +0000, Alex Blasche wrote:
>After all the trinity of quality - time - resources must be adhered to.
>
indeed, but you're still failing to draw the obvious conclusion. ;)

"priority inflation" is a "natural" effect of an issue tracker drowning 
in unresolved issues. this must be actively countered:
- one must not allow oneself to be bogged down by feature requests. it 
   is completely natural that more come in than can ever be resolved.
- one must make a conscious effort to remain honest in evaluating the 
   priority. this can be assistet by mandatorily using tools like user 
   pain.
   - for that matter, i found the implementation of the bug triaging duty 
     within tqtc (as still done two years ago) completely 
     counterproductive, as one is often left with little more than 
     guesswork, so no amount of honesty will help.
- if after correct prioritization there is still an inflation in a 
   priority level considered critical, then that is simply a 
   cultural/management failure (or missing political will, as jason put 
   it).


More information about the Development mailing list