--- Comment #17 from Andre Klapper <aklap...@wikimedia.org> ---
(In reply to Santiago Dueñas from comment #16)
> I've added some new charts that try to show this.
Thanks! They feel more helpful than the "Time to close by..." charts.
> These charts have some problems:
> - A peak that goes down doesn't implies you are closing the oldest bugs. It
> can means that there are more bugs that were open recently, decreasing the
> median. You can see this behaviour in Feb 2011. The median of Unprioritized
> bugs is 530 days because there's only one bug that were opened 530 days ago.
> The next month, the median goes down to 282 days because another bug was
> opened in Mar 2011 and at the end of that month none of them were closed.
Probably overhead and not a good idea, but could the overlay also display on
how many items the calculated value is based on?
> - Take into account that we are using the current priority of a bug. I think
> that for these kind of charts, it makes more sense to take the priority of
> the bug at that time, but it raises another problem: changes in lines might
> be produced by changes in the priority. If you change the priority of a bug,
> the old priority line will decrease while the new one will increase.
Yeah, that's what I meant in comment 10 - but let's revisit the "when to query
the priority/severity value of a report" aspect later.
You are receiving this mail because:
You are on the CC list for the bug.
Wikibugs-l mailing list