It would be great if there were even different customization levels for the kinds of votes that are available. The default could simply be a thumbs-up that casts a single vote, but admins could add other options and assign unique icons to them for their personal use-case. For example, an admin could create a High Priority (red thumbs-up) vote that would count as 3 votes, an Important (green thumbs-up) vote that would count as 2, and a Nice-to-Have (blue thumbs-up) that would count as 1. 

When someone votes, the vote count would go up on a particular bug, and other users would be able to either hover over or click into the vote count to see who cast what votes, which would enable employees to dialogue with those who see a need for a particular resolution or enhancement.

Additionally, it would be great if a feature were added where both certain types of users and individual users could be assigned only a specific number of votes either for a certain period of time (e.g., first six months at the company) or indefinitely (if, say, the company decides certain positions only get x number of votes). When they reach their limit, they aren't able to cast any new votes until issues they've voted on have been moved to a certain category that the admin defines in the Settings. By default, this would be the Closed status. When this happens, their vote balance (which could be displayed somewhere on their UI) would go back up. It would even be great if users could toggle whether or not votes display on bugs/cards in the list and kanban views as well as whether or not their own votes are highlighted there.

I think having something like this would enable support agents to highlight bugs or, if a company modifies its Bug Tracker process slightly, feature requests that they feel are important, thereby enabling developers and managers to identify trends, determine items that clients/customers really want, which isn't something that Software teams are generally as aware of due to their not being in direct contact with clients/customers on a day-to-day basis, and gather actionable information for planning upcoming projects accordingly. 

This is already something available in software like JIRA and kanban tools such as Trello, so it would fit quite nicely into the BugTracker environment.