@remusmp just called my attention to the fact that casting a vote doesn't update the issue's last update time, so it might stick around somewhere near the bottom of the list and never get noticed – which can actually be a reason to go for a +1 comment instead of a vote.

Would it be possible to change that behavior and count votes as an update to the issue, so they will move to the top of the list?

@zdavis According to the announcement on the blog, all existing "+1" comments have been converted to votes – would it be possible to also filter any new comments containing just "+1" and display a suggestion that the user should possibly vote for the issue instead of creating that comment?

Looks good, thanks! Was this the only new feature released? Did I miss some public announce?

Yeah, we released this feature this afternoon but I forgot to update the status here. Happy voting!

Is not this feature already implemented? I mean, right now I can see 9 votes for particularly this issue right in the issue details section on the top-right side

A voting feature can't really be compared to the 'follow' feature. Because not all followers of an issue necessary like the issue, it can in fact be the exact opposite. For example, lets say someone creates the issue "Close down the Bitbucket site". I might want to follow that issue, to keep track on what they talk about, but at the same time I would strongly disagree with the issue, and would use a down vote if possible.

Issue BCLOUD-7700 was marked as a duplicate of this issue.

@peso I think voting should be separate, in my mind I 'follow' an issue as a way of 'voting' but I don't want all of the +1 spam. I fear if an issue doesn't have many watchers bitbucket would just consider it low priority so I stay subscribed

Since everyone is already going to get this spam anyways...
+1

Definitely.

+1 (due to a lack of voting mechanism... oh, the irony)