RELATED IDEAS
Return votes to users when an idea is marked as "already exists" or "will not implement"
Currently if you mark an idea as shipped it returns votes automatically to idea portal users because this is now in the system. I feel if a user puts an idea in and it is something that already exists and they just didn't realize it, when I mark it as already exists they should get their votes back as well because it is the same end result as shipped.
-
ADMIN RESPONSEMar 13, 2026
Thank you for your idea. In some cases, an ideas portal user might wish to keep their vote on the idea, and other users might cast votes, even if the idea status is Will not implement. Since portal users can remove their vote if they need to use it elsewhere, this puts the decision into the user's hands.
Please continue to add comments to share your use case and thoughts.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- +1
13
MERGED
Automatically give back vote to user if idea status is changed to "will not implement"
As a product manager, I want to give back a vote to a user automatically if I set the idea status to 'will not implement' so they may use that vote on a different idea. Users get their vote back when an idea is set to 'shipped', but they do not au...
1
Future consideration
1
MERGED
Votes Per User feature should return votes to users when:
Today, the only thing that returns a vote to a user is the status of "Shipped". Statuses of "Already Exists" and "Will Not Do" should return votes to the user. Additionally, portal visibility should be considered as well. If a user cannot get to a...
0
Future consideration
© 2026 Aha! Labs Inc.•All rights reserved
Has there been any progress with this request? It would be very beneficial to allow us to determine which statuses would return votes to our users to keep them more engaged with the ideas process.
The issue of votes not being returned for items that will not ship. With not over 200 users that can vote, asking them to do it manually.
Also agree with this. Actually I see this not as an Idea but as actually overlooked the original voting process implementation.
Our users have to manually keep track of their rejected or already implemented ideas and retract their votes to get them back, and actually told me they do because the votes hold value to them.
This is a major point of frustration when we want to not penalize customers for voting on something that has made it to development, but without this being configurable we loose the ability to automate the status updates and this becomes very manual.
I agree. It would also be helpful to be able to manually set which statuses cause votes to be returned so product managers can control that for their portal.
@Mark, yes, that is what happens. Only Shipped ideas get the votes returned to users. I agree that "Already Exists", "Will not implement" and "Planned" should do the same.
Even better, if we can configure on the portal what statuses return votes.
Do I understand correctly this ONLY Happens when marked to SHIPPED. Even with planned the votes are not returned.
Agree with the comment to do the same on "Will not implement".
I'd like to see it configurable. A multi-select of idea statuses that let the product owner decide when votes are refunded. In my case, I can make it work with Shipped, Will not implement and already exists, but would like to refund also when an idea is planned.
I believe the same should apply to "Will Not Implement"