We're exploring JPD and I'm interested in the voting capabilities, but I have a lot of questions.
I understand how you can create a new field for voting to give people more votes, however, what is the recommendation in terms of when all votes have been used up besides creating a new field for collecting new votes?
For example, PMs have exhausted all their allotted votes for a specific field but we want to give them more while keeping their existing votes. While I realize we could increase the number of votes available to all, is any of the following possible:
Can voting be defined by time range? (e.g., voting open from March 1st through April 1st, 2024)
Can voting be tied to another field? (e.g., the number of votes available is based on another field's value, while allotting vote limits for each value)
Can we archive the existing votes and "reset" the amount people have available to keep using the same field? (e.g., a way to lock/archive existing votes to renew the number of votes available & reusing the same "voting" field)
We'd prefer not to create additional fields to collect voting because we'd wind up with hundreds of fields just for voting
Is there any way to report on the number of votes used vs. available on a user-by-user basis per voting field, and a way to see which ideas a user has voted for?
Thank you in advance for any assistance you can provide!
We could really use the ability to allow some way to delete votes from an idea.
The Problem:
Person votes on idea that is done. They want their vote back to vote on other issues. They can only get the vote back if they delete their own vote from that done idea.
Now let's say a person leaves the company. That idea now always has their vote on the idea and even global admins have no option to delete that vote.
Desired Outcome:
At a minimum allow Global Admins to delete votes submitted by other uses. Even better if this can be done through automation allowing for votes to be cleared off an idea once the idea is marked done.
85 comments