We would like to be able to "weight" or possibly allow multiple votes.
I have to admit that I'm really not too sure of the best way to do this, and I think it should be considered alongside a couple of other voting requests I've found. Voting is great because it can very clearly tell the developers what the users are most interested in seeing. But for the voter, there is no way to prioritise or weight their vote.
For example, I've currently voted on 7 improvements my site would like to see. In my mind, there is a very clear order in them. We have
1 preventing the wider use of Jira within our organisation.
2 that projects are screaming for and I've had to bodge round
3 that would make life easier for a significant number of users
1 that is nice-to-have, but we'd much rather have Atlassian look at the others.
My idea would be to allow each user a level of weighting on their votes, so that they can emphasise what is important to them. It goes something like:
1) Each voter has one Gold vote, two Silver, and as many Bronze votes as they want. They can still only vote once per issue.
2) When the "number of votes" is calculated for an issue, a Gold vote would be counted thrice, and a Silver twice.
I suspect it would be a good idea to limit the Bronzes as well (e.g. "you may not vote on more than 10% of open issues"). And it would need a method of "when issue is fixed, release votes back to users".
One pitfall - it could get horribly complicated when you consider sites like mine - in London, we've got 4 commercial Jira instances (with another one on the way), of which I look after three. I have a feeling that we are using it on other sites (especially in Oz). There's an argument there for allowing me 3 Gold and 6 Silvers. To be honest, it's not a problem here, because the licenses are in different names, so each "owner" would get their own votes. The three of us agree on the priorities, so we would vote the same anyway. But that might not be the case elsewhere.