I think we need a lighthearted break before we all go at it again:
Just so long as it's not captcha hell like what protects the issue trackerThen you layer more complicated mechanics on top that require too much user skill to easily fake with bots.
To give some important context on how the Issue Tracker works, when an issue is submitted it remains in the system for a certain amount of time before expiring. During this time, if it gains enough confirmed reproductions (to prove the issue is legitimate), it will remain on the tracker until it is closed. This is the “confirmed” state. Confirmed issues are investigated by our QA team, and if they are confirmed internally, they enter the “acknowledged” state.
You're completely right, and we do prioritise issues according to our own assessments rather than peel off the top votes list. There are many issues outside of the top 20 list that are worked on and show up in each update. That said, it's still useful for us to have an idea of what the community generally considers to be the most pressing/current issues as a factor in that assessment.
Consider this, why is it so important to you that they communicate with us, and choose their bug fixing, based on your standards? You worked at a call center, great.Hmm.. maybe that could somehow be communicated more clearly then. (sorry, you probably hear this sort of thing a lot).
But then, i can also see people getting salty they their issue was highly voted for but then didn't get worked on, while something with less votes did get worked on.
Really, i see nothing good coming from a visible voting system at least.
Consider this, why is it so important to you that they communicate with us, and choose their bug fixing, based on your standards? You worked at a call center, great.