Limit number of votes per user#127

In order to mitigate users voting for everything their heart desires, allow for limiting the number of votes each user can cast. This makes them think hard when voting for a feature as they know they have a limit. Once a feature is closed or they remove their vote from a feature then they can use that vote again.

Hi Mike, and welcome! That’s something we have been considering. Thanks a lot for your suggestion.

I would love to see this:
For every user I can limited number of upvotes per month.
So for example, if I could limit our customers to upvote requests 5 or 10 times a month, that would clarify the true needs and would be a better input when we prioritize our backlog.

Because now the problem is that they don’t “lose” anything if they upvote a request, they can just go through the requests and upvote everything freely.

But if they would have a monthly limit of upvotes, they would think twice before they upvote anything - which can identify what are the true needs of our customers better. Not just a “wishlist” but a truly prioritized list of real problems.

I very much agree. I am hesitating to share this board with our community as they will just vote on everything - they are all good ideas. The purpose of the board is to help us prioritise needs.
By limiting to x number of votes per month we get a true picture and can use the board for what it was intended.

Echoing the same thoughts as above.

User’s vote for items, but over time, things change, other work-arounds are found, or the original need for the feedback is no longer relevant.

From our point of view, we’d rather set a fixed limit of votes (5 votes). So that once a user has voted those 5 times, they would have to remove a vote in-order to vote again (votes on Completed/Archived wouldn’t count towards these 5 votes).

This would ensure our users only vote for the X most important things to them, and stale feedback posts would not sit at the top of the feedback board.

Thereby reducing noise, and allowing us to focus on what’s truly important for our users.

Echoing again the same thoughts again. @Avida Hancock hit’s the nail on the head -

…as they will just vote on everything - they are all good ideas. The purpose of the board is to help us prioritise needs.

Unfortunately we don’t have the resource to speak to each user individually to access their priorities. Vote limiting sounds like the ideal automated solution to that problem.

@Viktor Egri ‘s idea might work for their scenario, but I expect that’s a very complicated one for the Nolt team to implement, and overkill for most scenarios. A simpler solution could be - when a user votes, check how many active votes they have, and if they’ve already hit board’s settings of votes, don’t add the vote to the feedback item.

Has anyone got any tips on how they manage this within their community?