On Wed, Mar 20, 2013 at 1:24 PM, Donald Whytock <dwhyt...@gmail.com> wrote: > On Wed, Mar 20, 2013 at 12:53 PM, Rob Weir <robw...@apache.org> wrote: >> On Wed, Mar 20, 2013 at 12:32 PM, Donald Whytock <dwhyt...@gmail.com> wrote: >>> >>> Is there a way to list bugs in order by the number of votes they've >>> received? I couldn't find "votes" in the axis fields under tabular >>> reports. >>> >> >> You can use the vote count when defining a search criterion. But I >> have not seen a way to put the vote count into a column for display in >> the search results. >> >> -Rob > > Kinda limits the usefulness of votes, doesn't it, if you can't even > find out what the most voted for issue is? I mean, if you could > easily see that issue X has the most votes, you could bring up X on > the ML and at least decide immediately whether or not it would be > worked on. As it is, votes aren't helpful because they're not > visible. >
Bugzilla has a REST API as well, so it is possible to get a vote count in an automated way. But it appears to really slam the server, so I've been avoiding this. > Getting laborious myself, I did some URL hacking and got counts of > issues with certain minimal numbers of votes. Around 42 I got bored > and started jumping ahead...see the list at the end. > > I did a table report sorting on severity. Blockers dropped off at two > votes. Criticals dropped off at 4. Majors lasted to 70. The big > winner is https://issues.apache.org/ooo/show_bug.cgi?id=93613 with 378 > votes, and that issue's severity was listed as trivial. (Modified most > recently in January, by Rob.) > Interesting. It looks like you included all issue types, including DEFECT, ENHANCEMENT and FEATURE? I think it was suggested earlier that users tend not to vote on bugs. I don't know if that is true, but in my counts I ignored DEFECT issue types. > Perhaps a periodic report of this sort would make votes more relevant? > If we only highlight top vote issues from 2002, we're just reinforcing more of the same. Think of it this way: who is going to make a serious effort to express a preference on an idea in 2013 if the deck is clearly stacked from ongoing votes from a decade ago on some other issue? I think users will see that their vote has no meaning in a situation like that. Now, if we had a way to get the detailed counts on issues, and do this over time, then we could find a way of highlighting "trending issues", e.g., those that have recently been getting more votes, or more comments. (The number of users who have commented on the issue is perhaps more interesting than the number of votes). That might be a way of focusing in on what users think is important *today* without resetting vote counts. -Rob > Don > > 0 - 26738 > 1 - 4992 > 2 - 3647 > 3 - 1965 > 4 - 1555 > 5 - 1162 > 6 - 970 > 7 - 813 > 8 - 712 > 9 - 632 > 10 - 568 > 11 - 522 > 12 - 469 > 13 - 423 > 14 - 384 > 15 - 360 > 16 - 327 > 17 - 303 > 18 - 278 > 19 - 270 > 20 - 260 > 21 - 244 > 22 - 230 > 23 - 212 > 24 - 199 > 25 - 194 > 26 - 186 > 27 - 178 > 28 - 174 > 29 - 166 > 30 - 159 > 31 - 148 > 32 - 145 > 33 - 138 > 34 - 134 > 35 - 128 > 36 - 123 > 37 - 119 > 38 - 114 > 39 - 109 > 40 - 104 > 41 - 101 > 42 - 99 > > 50 - 81 > 60 - 63 > 70 - 49 > 80 - 39 > 90 - 33 > 100 - 29 > > 150 - 15 > 200 - 11 > > 300 - 2 > 378 - 1 > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
