Just a heads up: On March 24, 2025, starting at 4:30pm CDT / 19:30 UTC, the site will be undergoing scheduled maintenance for a few hours. During this time, the site might be unavailable for a short while. Thanks for your patience.
×I am a helpdesk manager new to JIRA and looking for a solution to help prioritize our bugs and enhancements for our developers that track all their work in Jira. The voting feature in JIRA would be ideal if it would allow each user to vote more than once for tickets. That way I could have our Helpdesk associates tick a vote every time they take a call that relates to a particular ticket (maybe tick it a few times if a customer feels really strongly about it). Currently each user can only vote/unvote once for each ticket, and can't vote for any tickets they submitted themselves.
to vote on behalf of someone else (the customer) is difficult to measure. A generic feature which is unbound to the current users possibilities to vote will probably be difficult. The easiest way to achieve something like you want is probably a custom field with a number where everyone (support) can update the field. Another easy solution would be to use labels, e.g. customer_impactHigh (or maybe even a component), especially if you can group such things like high, medium, low.
In my company we have such labels customer_impact. I can check at work how they are called exactly, i am just a developer, for me the priority is sufficient to resolve them
Yes we are prioritizing into High/Med/Low buckets but I was looking for a way to tell when an issue needs to get more attention. I'm going to try the custom field idea and have our helpdesk techs increase an integer value for each "vote"
Thx for the suggestion!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.