Voting field reset after task is completed

[Paul Harris]

I have given participants 25 votes to identify their top 10 enhancements.

After the enhancement is complete, I want to return that vote to those users by returning their vote.

JPD does not allow me to reset or erase the votes for the completed task so that the user may vote again.

Automation offers no solution. 

[Christos Markoulatos · Accepted solution]

Hey @Paul Harris 👋 Welcome to the community!

As far as I know there isn’t a native way to “refund” or reset votes on an idea once it’s completed. The current Vote field is designed for point‑in‑time voting (dot‑voting with a fixed budget), not an ongoing “evergreen” pool that auto‑replenishes when ideas ship. Also Automation can’t trigger on or modify vote fields.

Workarounds that teams use in practice:

• Run voting in cycles (e.g., per quarter/release): create a new Vote field like “Votes – 2025‑Q4” with your 25‑vote budget, and hide last cycle’s field from active views. That way, people naturally get a fresh budget without needing refunds. It’s the most common approach for now.
• Top up the budget on the current vote field after you ship a batch (e.g., add +5 votes) instead of trying to reclaim votes from specific completed ideas. You can change the per‑user limit in the field settings.
• Exclude shipped items from voting views so old allocations don’t “trap” votes: mark them as Launched/Shipped (using a roadmap/phase field) and filter them out. If you want to keep iterating, create a new improvement idea linked to the shipped one so people can vote there afresh. This is how Atlassian’s own JPD team handles shipped ideas.
• If you mainly need a quick thumbs‑up/down signal (not budgeted trade‑offs), consider a Reactions field (👍 / 👎 / 🤔) and set simple ground rules with stakeholders. It’s a lightweight alternative while voting remains point‑in‑time.

JPD's votes are meant to kick off a prioritization conversation for a moment in time (e.g., “Q4 planning”). They weren’t built as a persistent currency that automatically comes back when an idea is done. That’s why there’s no “reset/refund” and why Automation doesn’t hook into it yet.

If Atlassian later introduces refund/reset or Automation support and it contradicts the above, the truth wins, update your practice. For now, the cycle‑based setup is the cleanest way to give people their votes back without manual cleanup.

Links that might help:

• Known limitations of Jira Product Discovery
• Product Update: Introducing Voting
• Refund Vote Budget discussion
• Triggering Automation from vote field
• Jira Product Discovery fields reference

Hope this helps!

[Paul Harris]

Exclude shipped items from voting views so old allocations don’t “trap” votes: mark them as Launched/Shipped (using a roadmap/phase field) and filter them out. ... This is how Atlassian’s own JPD team handles shipped ideas.

This seems like the best approach, but I do not know how to accomplish the described solution.

• How does one "mark them as Launched/Shipped (using a roadmap/phase field) and filter them out." I cannot find this selection?

Alternatively, 

• If you mainly need a quick thumbs‑up/down signal (not budgeted trade‑offs), consider a Reactions field (👍 / 👎 / 🤔) and set simple ground rules with stakeholders. It’s a lightweight alternative while voting remains point‑in‑time.

This is the second best solution - but the field is not displayed in Public views nor editable in Contributor views - so reactions is not an option unless this can be displayed and enabled.