Limit the number of votes a person is able to give
That would be useful to make users focus on the ideas they like the most, thus helping us to have a more valid priority list.
That would be useful to make users focus on the ideas they like the most, thus helping us to have a more valid priority list.
I'm not exactly sure if agents should vote... This should be an internal decision in the end? But if they're acting as users, yes, they should have the same limits.
I also cannot think on a good reason for someone negative voting an idea. Is it a bad idea? If so, why? I'm not sure about the limits because of this.
Finally, maybe questions/problems should have a different limit, or no limit - a vote there would mean more people have the same issue and it should be answered soon, right? On the other hand, if you give people freedom to vote on ideas, that may dissolve the team priorities, as in "all those ideas are nice, let's vote on all of them!" instead of "those ones are better for me, so I'll give them more votes".
There hasn't been a decision on this one yet. When it is added to the roadmap you'll get an email telling that the status has been changed, e.g. to Planned or to In Progress (just check if you're following this topic).
1. Agents voting should not be possible, or configurable ('Agents can vote yes/no').
2. A negative vote should also count against your remaining votes.
3. Voting should only be possible for Ideas, not for problems or questions. I think if a problem or question is worth voting on, the issuer or an agent should transform it to an Idea first.
Thank you for your suggestions, Roelof!
When you sort questions or problems by "frequently asked" or "common" respectively, the ones with the most positive votes will come out on top. Would you rather use a different metric to sort popular questions / problems?
Vote Allocation Limits is a super valuable feature, since they help us prioritize bug fixes and features.
See UserVoice and UserEcho for examples of Vote management.
Thanks everyone for your feedback! We are already working on this feature. Here is the summary: