Our organization promises to review and take some action on any idea that receives over 25 votes. We don't count internal votes toward that total, but internal votes will push it over that threshold.
The main problem is that the customers only see the vote total in the Ideas Portal. So we can have 3 customer votes and 22 internal votes. Customers will only see the 25 and be chasing us for answers, even though that idea is nowhere near the threshold for review.
This also applies to standard views. The main Vote Overview are that shows new and popular ideas would be a great screen to help us manage the ideas, but it's polluted with votes that make the whole thing unusable. When we go to create any new view, the best we can do is mark all the email domains that we want to include in the view, which is a cumbersome and heavy lift when I want to quickly create different views of Ideas. To be clear: filtering domains out of reports does not handle this use case.
What we really want is global a feature that removes votes according to email domain from all counts displayed everywhere: in new views, in standard overviews, and especially in the externally facing Ideas Portal.
I'd like to add on to this that I'd like to be able to filter out internal domains in a report on created ideas so I could review Ideas that were created by customers but have not been made visible globally.
I join the voting. We have to have this feature. Voting is taken seriously in my company, and an internal vote cannot have the same value and be counted the same as a real customer vote. We need a way to somehow be able to easily track customer votes without internal influences. I would go as to even say we need two voting fields.
How about going further with this...rather than simply excluding certain domain's votes, perhaps there should be a scoring mechanism where a weighting could be applied to domains e.g. categorise one (or more) domains as "internal" (with all others considered "external"), then allow the ability to set a weight for internal vs external ideas. You could then offer customers the ability to choose from an "absolute" vote count (current behaviour) or a "weighted" vote count (proposed).
Just to note, the value is already recognized right here, albeit used differently. On this idea I can see the count for total Votes and My Organization Votes.
The difference between those two counts is the number that this idea is most concerned with, but it's essentially the same concept. Distinguishing between my organization's votes and votes not from my organization is a critical function across all of Aha!, for every user type.