Feature #1011

Add voting to tickets

Added by Maxim Krušina almost 4 years ago. Updated 3 months ago.

Status:Closed Start date:2008-04-07
Priority:Normal Due date:
Assignee:- % Done:

100%
Category:Issues
Target version:-
Resolution:Wont fix

Description

As I see lot of people voting for different tickets, I got idea why not to add voting to tickets.
Here is my rough idea:
  • Voting can be enabled/disabled per project/tracer
    • so some projects will have no voting, some projects will have voting, but in some trackers (probably we don't vote in "bugs" tracker)
  • Every user can give only one vote per ticket
    • so voting will be for registered users only (probably)
  • Proposal of voting model:
    • Simple: you can vote (+1) or not vote (0)
    • 1-5 model: you can select "how much" you vote: 5 = very much, 1 = maybe...
    • -1,0,+1 model: you can vote in positive or negative way...
  • Each ticket will display voting score (numbers of points) and number of votes (this apply based on exact voting model)
  • When Nr. of votes and/of voting score will be added to ticket list's filters, we can list tickets by voting score or number of votes
  • Top 10 (5 etc) of most wanted issues can be displayed on homepage of project

What others think?

Related issues

related to Feature #8299: Add "vote for this issue" button on issues Closed 2011-05-05
duplicated by Feature #8478: Vote for feature Closed 2011-05-31

History

#1
Updated by Ale Muñoz almost 4 years ago

I'd say +1 for this : )

#2
Updated by Maxim Krušina almost 4 years ago

Yes, +1 for me too ;)

#3
Updated by Rocco Stanzione almost 4 years ago

+1. May be a good candidate for a plugin.

#4
Updated by Raz Mataz almost 4 years ago

+1 from me, too

#5
Updated by F. D. Castel almost 4 years ago

+1 here.

(Hey! We are VOTING here... Nice hack. :) )

#6
Updated by Leandro Lucarella almost 4 years ago

+1

#7
Updated by Arthaey Angosii over 3 years ago

+1. See http://www.uservoice.com/ for a clean example of simple issue-voting.

#8
Updated by David Gillard over 3 years ago

+1

#9
Updated by Roy Belview over 3 years ago

+1. This would be a really great feature!

#10
Updated by Dmitry Lihachev over 3 years ago

+1

#11
Updated by clawfrown clawfrown over 3 years ago

+1 !

#12
Updated by Marcello Henrique over 3 years ago

+1 great!

#13
Updated by clawfrown clawfrown over 3 years ago

I believe simple model of voting will be the best.. Coz 5 stars and -1,0,+1 are weird..

#14
Updated by Jan Losinski over 3 years ago

+1

#15
Updated by Curtis Stewart over 3 years ago

+1 I could use it.

#16
Updated by David Davis over 3 years ago

Here's something that is 'sort of working for me': change the 'Issue priorities' Enumerations to [..., -1, 0, +1, +2, +3, ...] (as many as you need). This had the side-effect of making the 'priority' more relevant as well.

Then, the task would be to allow a non-manager 'user' to change the priority (explicitly?). Maybe 'voting' is a simple rule: a (non-manager/developer) 'user' can only change the priority, once, by one increment or decrement.

I was just toying with this solution as a workaround tonight, but thought it was interesting to implicitly tie the 'votes' to the 'priority' of an issue. Then the issues that are the 'squeakiest wheels' will automatically get the highest priorities.

#17
Updated by Thomas Lecavelier over 3 years ago

Like the idea and its description.

But that's another layer of cmoplexity: including it would move redmine closer to the bloated status :(

I preach for a plugin/module approach: let redmine admin add features they want to their very redmine, don't put all of them in it.

HTH

#18
Updated by Mischa The Evil almost 3 years ago

  • Status changed from New to Assigned
  • Assignee set to Mischa The Evil

I'll start some work for a plugin-implementation of issue-voting soon...
More to come...

#19
Updated by Igor Tkachenko almost 3 years ago

+1
I think this is a must have thing for every successful product aimed for end user!

On the first stages of product development when user community is small you may just write all users' suggestions to a paper sheet and easily see how many users want certain feature (this feature is wanted by 3 users and other features are wanted by only a one user, ok I'll do the first feature). But when the product community grows it's getting to hardly define what users want more. Without this feature you may think that users want EVERYTHING and RIGHT NOW! Having this feature allows us to plan what improvements we should implement first and what may wait for some time.

#20
Updated by colin moock almost 3 years ago

huge +1. every professional, public software project needs this.

#21
Updated by colin moock almost 3 years ago

notice that even redmine's issues are littered with +1 notes. those should all just be votes. every "+1" note in this system is a vote for ticket #1011.

#22
Updated by Mike K almost 3 years ago

colin moock wrote:

notice that even redmine's issues are littered with +1 notes.

lol, that's a good point
oh yea... +1 ;p

#23
Updated by Mischa The Evil almost 3 years ago

  • Assignee deleted (Mischa The Evil)

Andrew Chaika developed an issue-voting plugin which probably solves this issue. It can be found here on the forums: Issue Vote Plugin.

#24
Updated by Eric Davis almost 3 years ago

  • Status changed from Assigned to Closed
  • % Done changed from 0 to 100
  • Resolution set to Wont fix

Closing issue. Andrew Chaika has developed this in a plugin. See my comment for more information.

#25
Updated by Kamil . about 2 years ago

What is the reason of not integrating this feature into trunk?
The best example is redmine.org itself, where users are voting constatnly still using comments.
If there would be necessity not to have voting - it should be possible to disable it in options.
What do you think?

#26
Updated by James Turnbull about 2 years ago

Or just activate the voting plugin on Redmine.

#27
Updated by Kamil . about 2 years ago

James Turnbull wrote:

Or just activate the voting plugin on Redmine.

That would be also a good solution, but if it is so desirable, why not to include it?

#28
Updated by Ngewi Fet about 2 years ago

I agree that issue voting be used on redmine.org either as the plugin or in trunk
to eliminate the need for voting in comments which incidentally I am doing now.

#29
Updated by Luiz Carlos Junior over 1 year ago

+1 (this is horrible)
Isn't it possible to add this feature to Redmine.org (into the trunk or as a plugin)?

#30
Updated by Terence Mill over 1 year ago

It should be transparent to the comunity how ranking of features is. Else the future development can't be community driven.

+5 (new syntax - lol)

#31
Updated by Sascha Herrmann about 1 year ago

+1 for activating this feature on redmine.org!!!

#32
Updated by Fernando Hartmann 7 months ago

+1 This should be in Redmine basic features !

#33
Updated by Fernando Hartmann 7 months ago

Are someone using this plugin with Redmine 1.2.0, where is it available to download ?
I Found only a updated up to 2009 in https://github.com/Ubik/redmine_vote !!
Is it abandoned ?
If so, we need to reopen this ticket !

#34
Updated by Kurt Christensen 3 months ago

I nice guy forked the original redmin_vote plugin, and his fork is working for me. I'm running Redmine 1.2.1 on Ubuntu 10 with MySQL.

#35
Updated by Kurt Christensen 3 months ago

Urmf. Sorry for the garbled previous post. Here's the link to the nice guy's fork of redmine_vote:

https://github.com/jimmyz/redmine_vote

#36
Updated by Terence Mill 3 months ago

I am working on a fork with missing features
https://github.com/cforce/redmine_vote

  • per project module which can be switched on/off
  • added 3 rights
    • vote_issue
    • view_votes
    • view_voters
      separated view from hook code, no more inlining
      TODO:
  • fix #2 bug for public projects
  • establish view_rights for issues vote patch
  • provide filters for issue search

Also available in: Atom PDF