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.
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
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"