Ability to vote for a ticket

[anonymous]

The ability to vote for a ticket would be a great functionality, allowing users to vote for the ticket they would like to see resolved the most.

Additionally, if this is going to be implemented, it would be very nice to have the ability for the trac administrator to create different user category, and assign a given user to a given category.

This way, a developer voting for a certain ticket would have a "bigger" voice than a simple user, etc etc.

Thanks for this great software.

[anonymous]

Yes, indeed that would be a very nice feature, espechially for Open-Source projects.

[anonymous]

1

[anonymous]

We've been using Trac as internal system for more than a year now. Recently we've decided to add ability for our users to submit bugs and improvement suggestions for our software. Trac seems like a nice choice but we would really like to have voting functionality. Is it in some near plans or it's not going to be implemented at all?

[Matthew Good]

No, there are no plans for implementing this at the moment. I would prefer to close this ticket as wontfix. If someone wants to write a plugin for it then go ahead, but I don't see a reason to make this a core Trac feature.

I actually think that ticket voting is generally a bad idea and ​Havoc Pennington's comments on the Redhat mailing list do a good job of explaining why I feel that way.

[anonymous]

Well that's fine. Thanks for clarifying.

But I think that Havoc's argument is flawed. You are not required to fix the bug with the largest amount of votes, but it is still nice to have this feature if you believe it helps you see the real situation, which is the case in many cases when you don't get spammed, with spamming itself being mostly the problem of quite big projects.

[mrenzmann@…]

In case someone writes a plugin for this feature: it might be a good idea to restrict the voting option to admin-definable ticket types. This way votes could be allowed for enhancements only, for example, while voting for defects or tasks is not possible. This would give the benefits of the original idea without the downsides that have been outlined in Havoc's posting.

[mmihajlovic@…]

So, any takers on this? I would love this functionality, but am not a python developer.

[Christian Boos]

Considering the ticket has been created 2 years ago, I think you have by large the time to learn Python before the ticket will implemented and closed ;)

More seriously, this is a candidate for a plugin, especially once the more flexible ticket WorkFlow infrastructure will be in place. As I don't think the vote feature will ever be part of Trac core, I'm closing this as wontfix.

Alternatevely, you can follow the recent renewal of interest in the redesign CC field topic (#1459). The number of people on the nosy/CC list of a ticket is a somewhat good measure of the popularity of a ticket.

[jm3@…]

i'm very interested in this feature. bugzilla has a nice implementation of it.

[Emmanuel Blot]

As cboos wrote, this feature would better be implemented as a plugin, see ​Trac Hacks and 'request-a-hack'.

[anonymous]

no takes on a plugin yet. just implement in a build please. shouldn't be very hard.

[henke.mike@…]

never mind found some @ track-hack.or called voteplugin and poolmacro ​voteplugin ​pollmacro

[Igor Tkachenko <tkachenko.igor@…>]

I'd vote to add this ability to trac's core, as this is one of the kernel features for those who develop applications basing on users' feedback. Moreover even edgewall's trac has this feature.

[Noah Kantrowitz]

Replying to Igor Tkachenko <tkachenko.igor@…>:

I'd vote to add this ability to trac's core, as this is one of the kernel features for those who develop applications basing on users' feedback. Moreover even edgewall's trac has this feature.

Yes, because this Trac has VotePlugin installed.

[Emmanuel Blot]

Replying to Igor Tkachenko <tkachenko.igor@…>:

I'd vote to add this ability to trac's core,

This is typically a feature which is mostly useless in an enterprise environment (private Trac installation, no open source project or the like)

[igardais@…]

What is the [Vote] section meant for in the TracIni wiki page ?

[Ryan Ollos <ryano@…>]

Replying to igardais@…:

What is the [Vote] section meant for in the TracIni wiki page ?

I found this to be confusing as well. After seeing the [vote] section in TracIni#vote, I went off trying to enable it on my Trac installation. However, after reading this ticket and finding the ​th:VotePlugin, I have to assume now that the [vote] section exists of t.e.o. because the VotePlugin is installed here. This is a bit of a confusing issue since I was assuming that the documentation on t.e.o. was the same as a default installation of Trac.

[Ryan Ollos <ryano@…>]

Replying to nkantrowitz:

Yes, because this Trac has VotePlugin installed.

Actually, I guess if I had read more carefully I would see that it definitely is installed!

[Emmanuel Blot]

| This is typically a feature which is mostly useless in an enterprise environment

Actually, it's useful for any product with a large userbase, enterprise or not. Enterprise customers benefit from feedback as well.

[Christian Boos]

(quick check: … le vrai Manu ? (or who needs #1890?))

[manu.blot@…]

Replying to cboos:

(quick check: … le vrai Manu ? (or who needs #1890?))

Definitely not, the above eblot user is being impersonating my login.

[Christian Boos]

Good to know ;-)

[anonymous]

I'm interested in a solution that would allow the stakeholders to place a finite number of stars per person on tickets, as a way of forcing us to explicitly prioritize our tickets. It should probably be a plugin though (: