We are using the voting plugin as a way to determine the priority of the bugs our community wants to be fixed based on the most amount of votes. We have a couple of questions about the plugin.
From reading this:
Is it possible to give back a vote if the topic is marked as solved?
As a feature request, could we have the option to set every X amount of days/weeks/months etc. the user is given X amount of votes back?
For example, every month the user receives 10 new votes
As for querying, using the data explorer, is there a way to query the votes on each topic?
I don’t think it currently is, so a common practice is to set an auto-close timer so topics are closed on being solved. Set for a day or two it allows folks to ask follow up questions, and then closes, releasing the votes.
Releasing on solved would be quite useful for other scenarios, to be sure.
Following up on this, we were also under the assumptions that when a topic marked as solved the votes gets released. What is the latest implementation as of today? Does marking a topic as solved release the votes?
It’s not always practical to close a topic. We are using the votes and solved/unsolved for feature and bug reports. So even when it’s solved the topic left open indefinitely for feedback on it (future regression or comments). It would be ideal to be able to link votes to solved/unsolved for this reason.
Also we can’t auto close topic either since it can take over a year for a report to the resolved.
The topic-voting and solved plugins don’t interact directly. Both systems rely on Discourse features involving topics, but the plugins were not developed for a specific use requiring both.
So that means this feature request is still valid, and the more information we have about use cases detailed here will assist in the discussion.
