Contributers and greater should be able to remove votes from ideas. This would prevent an issue where Zendesk tickets can't be linked to ideas due to the user already having voted for the idea.
Many of you mentioned the need to filter out votes from certain people, like churned customers or internal employees. Segmentation is a great solution for this, to help you focus on feedback from the people you are most interested in. This is available in Ideas Advanced and you can learn more here.
We are leaving this idea open to consider in the future.
We have the Ideas Advanced version of your software today. How will this address those "extra" votes for churned customers or employees that are visible on the Idea portal? Will it also remove visibilitye of the extra votes in the customer facing Idea Portal?
Thank you,
Beth
When so many customers have submitted this as a request, and so many votes have been cast supporting it, telling us to manage this functionality by purchasing an add-on product that would SIGNIFICANTLY increase our annual licensing cost is not only insulting but sorely out of touch.
The ability to delete votes is necessary for maintaining a proper prioritization process. If there are votes from churned customers or deleted users it will skew both the vote count and the relevancy of the idea to our roadmap.
Also, if you import a bunch of ideas, you end up with them all associated with that email address, which is probably not correct.
If someone make a mistake and submits a proxy vote on the wrong organization, I want to be able to clean this up.
Our need for this feature is a little different from just removing a vote. We need a "downvote" functionality where a customer, on our product idea portal, can easily give a vote against a feature. As we have a community where we test new ideas to find out if they are deemed necessary, it should be possible to downvote an idea. Currently, the customer has to leave a comment. But it would be nice to see how many of the customers do not need a new feature.
Some of our employees voted directly on the portal - it's public - despite we have documentation to use our private proxy vote portal. I end up with invalid or duplicate votes - as some people are also creative and create 2nd portal users with a different email. I need full control over voting otherwise it's not reliable and unreliable data is useless.
I've got users where we've marked their idea as "Will not do" but there's no way to release their vote. Really could do with better features around managing vote removal to make this a viable portal.
We'd like to do a strawman vote of all our ideas each quarter with our internal teams. We'd like to delete the old votes from quarter to quarter so that we can re-evaluate which ideas are more important to focus on.
Hi there, thank you for your feedback. I did want to share that the use case you mentioned should be handled currently. Once you ship an idea, the votes are released back to the portal users and no longer count against the max votes.
Currently, when I promote an idea out to a release and then ship that release, I have to tell customers to remove their votes from shipped ideas so they can reclaim their votes from their defined maximum. It would be way better if I could define when votes were "released" from an idea back to the customer so they could then vote on more items.
Having recently launched the ideas portal to our customers I see this idea as a very helpful feature for administration of the portal. Prior to the portal being live for all of our customers we had tested it internally and with our customer advisory board for several months which resulted in many "test" votes or votes for items that have since been shipped - but the votes are not automatically returning to the voter despite configuration and our customers have noted that they must go manually remove their votes from items that are "shipped" in order to get them back.
It would also be nice if administrators could configure the system to return votes on more than one idea status - i.e. when an idea is marked "already exists" in addition to when an idea is marked as "shipped".
My scenario was I sent out a vote for internal voting with 10 big ideas to 3 people at my company. Then later I wanted 15 people from my company to vote on 20 big ideas (within that same workspace). Since the people and the ideas overlapped, I wanted them recast their votes (to make sure they didn’t incidentally favor the original 10 ideas).
I ended up having to recreate each of the original 10 ideas to dissolve all the votes.
As admins, this would be super useful. Sometimes there is a need to clean up the votes or in situations where the Aha setting was incorrect and there was voter fraud and a need to reset.
We have a pretty tough use case. We had someone log A LOT of votes using fake email addresses which have skewed the votes significantly. While we have removed these fake users there is no way to remove the damage done which feels like a huge limitation. I am not sure how we are going to move forward using ideas given this constraint. There should be a way for an administrator to eliminate votes or when blocking a user to invalidate their votes it feels like control that is necessary for a public portal.
I already voted and commented on this in April and still need this feature. It is challenging to have deleted users old votes stay on an idea when they are no longer with the company.
This is the exact situation I find myself in. Deleted a user (who had already voted for an idea) so I could link the Zendesk ticket (which re-created the user and added a vote) and now I have an additional, inflated vote. I would like to see the ability to delete votes (I administer the system after all) but I also think the Zendesk integration could be smarter and allow the link to happen even if the person was already associated with the Idea.
As priorities shift and change it would be nice to be able to clear out all votes when needed and have teams re vote on priorities. Sometimes a total reset is needed due to items that have been in the backlog a long time and already would have a number of votes.
I've returned to this idea in hopes of finding an update. Unfortunately, don't see anything but have thoughts to contribute on how this might work.
Instead of completely re-setting vote count to zero, should it be set to 1 with the 1 vote attributed to the requestor and if an admin created it, set to 0? After votes are reset, when the round of voting occurs, the portal user that has created ideas will see his votes already taken and will have the option to remove his vote without changing the created by field.
I would like to be able to configure when votes are released from an Idea.
Example: One portal the votes are released to be reallocated once the feature is committed to and planned for a release. Another portal the votes are released once the feature is implemented and shipped.