Use Cases For Vote Feature in JIRA

[Mark Symons]

I have a 100 user JIRA v4.4.4 with 15000 issues - with only 4 issues that have been voted for. Before disabling the voting system in order to simplify the system for users I would like to consider whether there are any interesting ways in which voting can be used that I might have overlooked.

So, is Voting no more complex than "issues get voted for and then you can rank by popularity (and perform JQL queries)" or are there additional tricks or uses?

I think that one consideration in a 100 user system is that even if people do start voting then one would end up with a very flat profile (not much difference between the most and least popular) and thus not much actual utility.

Thanks to reading other answers I am aware of the defect that affects activity streams when voting is disabled so I am in no hurry to implement any changes until after upgrading to v5.0.

[Nic Brough -Adaptavist- · Accepted solution]

Other than filtering for "stuff that I have voted on", I think you've described all the functionality voting provides.

[Norman Abramovitz]

If you have teams which are semi-independent then having the project lead or manager only doing the voting, you can determine issues which are blockers for future features. It is not the same thing as related links since there may not be any issue yet to associate. For example, you are bidding on a contract, but you need features fixed in other parts of the system. Vote to raise the flag, so they can be discussed.

[Sorin Sbarnea (Citrix)]

Voting is extreamly useful for open systems, system with lots of users. Still, because there is no such thing is downvote it's use is still limited.

If you do not have a big enogh number of users, or there is a small change for the requests to be voted you should disable it. Otherwise it could be very usefull, now depends on the usage patterns.