Bug System Pilot Dev Workflow: DRAFT Accepted/Understood
peter.jensen at oracle.com
Thu Jan 19 10:22:45 PST 2012
> If you're not in a context where you can trust the usage (e.g. if
> you're doing general process monitoring and release management),
> you've complicate things because you then have to combine Open and
> Evaluate to get an accurate picture of how well Development processes
Just by means of example.
If I want to know the rate at which Bug arrives on Development's plate,
I would need to count the bugs changing to Open, from states other than
Evaluated, plus the bugs changing to Evaluated, from states other than
Open, with in a given period of time.
Not impossible, just not as easy as counting bugs changing to a single
Of course, if JIRA, unlike Bugster, can impose the restriction that the
state Evaluated can only be reached from Open, then it's almost the same
(except for the Evaluated->Open transition, which I somehow don't see
getting used a lot, never mind how badly an issue was initially
BTW, does anyone know if the JIRA database records transition history in
a form that makes this kind of queries practical?
More information about the discuss