Apache OpenOffice (AOO) Bugzilla – Issue 84530
http://qa.openoffice.org/iz_votes.html outdated
Last modified: 2017-05-20 09:19:23 UTC
http://qa.openoffice.org/iz_votes.html last update: $Date: 2006/02/19 15:31:49 $ ...many issues are fixed and closed, this page shoud be daily generated (or weekly) to show current top votes. Users don't know what the top votes on open issues are... Where do developers get their priorities from? These issues are top voters, and working on them should be a high priority. Also: add a link to this page from the QA Homepage to make it more visible, this should (at least in part) drive development!
Also: include a list of the top 10 (20, whatever) open issues with the highest number of duplicate bugs in them (refresh monthly should be enough here as it's possibly a big query)
changed priority. A P1 issue is something else. If you like to find out then please read http://www.openoffice.org/scdocs/ddIssues_EnterModify.html#priority André Schnabel once created a template that is stored within the documents and files section of the project. http://qa.openoffice.org/files/documents/77/1689/issuevotes.ots A part of the URLs within that document seem to have changed. Perhaps you would like to volunteer and modify that document to reflect the changes that you would like to have included. Added the other QA leads to discuss how we can get this page updated.
Thanks Joost, but I'm subscribed to issues@qa, so it only duplicates my mails. Would be better to discuss what to do on dev@qa mailing list, isn't it?
I would suggest to make a fairly simple, automatic solution: - write one query for all not-CLOSED issues with >=40 votes - write one query for all not-CLOSED FEATURES and ENHANCEMENTS with >=40 votes - write one query for all not-CLOSED DEFECTS with >=30 votes - write one query for all not-CLOSED DEFECTS, FEATURES and ENHANCEMENTS with >=30 votes with an OOolater milestone Put those queries on the http://qa.openoffice.org/iz_votes.html page, and the issue is solved without much work.
Here are the queries, if you can put these on the http://qa.openoffice.org/iz_votes.html webpage and link it from the qa homepage http://qa.openoffice.org/ that would be great. ALL HIGH VOTES > 40 Votes http://qa.openoffice.org/issues/buglist.cgi?issue_status=UNCONFIRMED&issue_status=NEW&issue_status=STARTED&issue_status=REOPENED&issue_status=RESOLVED&issue_status=VERIFIED&votes=40 HIGH DEFECTS > 20 Votes http://qa.openoffice.org/issues/buglist.cgi?issue_type=DEFECT&issue_status=UNCONFIRMED&issue_status=NEW&issue_status=STARTED&issue_status=REOPENED&issue_status=RESOLVED&issue_status=VERIFIED&votes=20 HIGH ENHANCEMENTS, FEATURES > 40 Votes http://qa.openoffice.org/issues/buglist.cgi?issue_type=ENHANCEMENT&issue_type=FEATURE&issue_status=UNCONFIRMED&issue_status=NEW&issue_status=STARTED&issue_status=REOPENED&issue_status=RESOLVED&issue_status=VERIFIED&votes=40 HIGH PATCHES > 10 Votes http://qa.openoffice.org/issues/buglist.cgi?issue_type=PATCH&issue_status=UNCONFIRMED&issue_status=NEW&issue_status=STARTED&issue_status=REOPENED&issue_status=RESOLVED&issue_status=VERIFIED&votes=20 HIGH OOolater > 30 Votes http://qa.openoffice.org/issues/buglist.cgi?issue_status=UNCONFIRMED&issue_status=NEW&issue_status=STARTED&issue_status=REOPENED&issue_status=RESOLVED&issue_status=VERIFIED&target_milestone=OOo+Later&votes=30
Patches shows very few issues, recommend using 5 Votes as the limit. HIGH PATCHES > 5 Votes http://qa.openoffice.org/issues/buglist.cgi?issue_type=PATCH&issue_status=UNCONFIRMED&issue_status=NEW&issue_status=STARTED&issue_status=REOPENED&issue_status=RESOLVED&issue_status=VERIFIED&votes=5
Issue 79840 is basically a duplicate of this...
ja asked me in December to make suggestions on how to proceed with this issue... I replied with all the query strings I thought relevant, all that's needed is to put them on the http://qa.openoffice.org/iz_votes.html page and the issue is resolved in my opinion. Now that 2.4 is out, could someone please take care of this? I think that the vote visibility is important for the community and developers to keep in sync.
Adding a dependency, and hoping that someone will update the webpages with the suggestions below to get them to a post-2006 status...
obsolete