Priority field in bug DB
Number of replies: 2
I was looking through the bugs DB, trying to figure out if there was some rhyme or reason in the way bugs are assigned and resolved. I really didn't find anything I recognized as systematic, but I did notice there seems to be quite a bit of deviation as to how priority values are assigned to bugs. Are there some guidelines somewhere that explains the priority system? When bugs are reviewed, are they reviewed by descending priority? As a rule, I submit my bugs as 1-Low. Should I be submitting them at a higher priority level to increase the chance that they might actually be addressed?
Re: Priority field in bug DB
I always sort mine by severity and priority, descending. So "critical" and "5" get to the top. Then I read it, and ask, in order:
- Does it make sense?
- Does it have enough info to repro?
- Is it easy to repro -- can I repro it now? like right now?
(this is actually the main thing, if I can test immediately, it'll get fixed pretty soon).
- Do I understand WTF is happening?
- Does it affect many moodle users? my customers? my pets? or only users of frobolator 3.4beta?
- Does it make sense?
- Does it have enough info to repro?
- Is it easy to repro -- can I repro it now? like right now?
(this is actually the main thing, if I can test immediately, it'll get fixed pretty soon).
- Do I understand WTF is happening?
- Does it affect many moodle users? my customers? my pets? or only users of frobolator 3.4beta?
Re: Priority field in bug DB
it's not quite that orderly, unfortunately. Urgent bugs get fixed first while patches usually get dealt with in bursts. Various features can not just be added willy-nilly ... they have to fit in with whatever is going on with a module at that time.