Opened 14 years ago
Closed 4 years ago
#7170 closed enhancement (fixed)
Add Ticket Voting support to Haiku's Trac
Reported by: | umccullough | Owned by: | nielx |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | Website/Trac | Version: | |
Keywords: | voting | Cc: | |
Blocked By: | Blocking: | #16210 | |
Platform: | All |
Description (last modified by )
I think it would be extremely valuable to add some kind of "Ticket Voting" feature to our Trac installation.
This would allow users/testers to vote up bugs/enhancements that they feel are pertinent to them (for example, hardware/driver issues that affect their ability to run Haiku, etc.)
This would allow us to better prioritize resolution of issues. In the case of enhancements, such as drivers for unsupported hardware, or new features, the votes could be used as a measurement for creation of bounties, developer contracts, and/or hardware purchases to incent developers to work on the issues.
Note: There appears to be a "trac-hack" plugin which is *NOT* sufficient IMO:
http://trac-hacks.org/wiki/VotePlugin
It is URL-based, and not specific to tickets. I don't think this is the solution we should seek.
Change History (23)
comment:1 by , 14 years ago
comment:3 by , 14 years ago
Description: | modified (diff) |
---|
comment:4 by , 14 years ago
Description: | modified (diff) |
---|
comment:5 by , 14 years ago
Description: | modified (diff) |
---|
comment:6 by , 13 years ago
Any possibility we can install the trac-hacks VotePlugin?
I'd like to start encouraging users to use this so we can really start analyzing the importance of bugs/enhancements across our userbase.
comment:7 by , 7 years ago
Resolution: | → no change required |
---|---|
Status: | new → closed |
Closing request as it hasn't come up for the past 6 years.
comment:10 by , 7 years ago
Resolution: | no change required |
---|---|
Status: | closed → reopened |
comment:11 by , 7 years ago
I agree also. Some parts of Haiku have been broken for years, making the end user experience much less than it could be.
comment:13 by , 7 years ago
A common question newcomer devs ask when joining Haiku is "what could I work on"? It may be interesting to point them to "most voted" tickets, in addition to the "easy tasks".
Not so much useful for the current devs however, I think we all know where the problems are...
comment:14 by , 6 years ago
It appears https://trac.edgewall.org is actually running the Vote plugin. So that one seems good to use...
comment:15 by , 6 years ago
Owner: | changed from | to
---|---|
Status: | reopened → assigned |
We now have the vote plugin installed and working. However it doesn't provide a way to query for votes, or view them by default; there is a sample SQL report included that is what most people seem to use to find "high-voted" tickets, but no way to easily expose this on the Queries page.
nielx, could you take a look at this? It seems the TracVote plugin could probably be modified to add a "Voted" field to the Queries page, probably, much like your AttachmentFlags plugin adds a "Has a Patch" field.
comment:16 by , 6 years ago
The difficulty is that the TracVote does not store the vote count as property of the Ticket, but in a separate table. The ticket query system only looks at ticket properties. We have disabled the SQL report builder because quite frankly it is not that nice, nor user friendly. However, if we want to create reports with the votes we should re-enable it.
comment:17 by , 6 years ago
Do we need the report builder enabled, or can we just set up the SQL query once and link it from somewhere (as we do for the "easy tasks" query, for example)?
comment:18 by , 4 years ago
Blocking: | 16210 added |
---|
comment:19 by , 4 years ago
I have enabled the module, and you can see the resulting voting report here: https://dev.haiku-os.org/report/9
comment:23 by , 4 years ago
Resolution: | → fixed |
---|---|
Status: | in-progress → closed |
- The report can be found as report:9
- There is a link to the 'Most Voted Tickets' on the query page
Actually, it does look like a report can be written to find "most voted tickets", example on edgewall's Trac: http://trac.edgewall.org/report/34
Perhaps it could be workable after all.