Open jberkus opened 3 years ago
This wouldn't be hard to implement and we already store this info in db (to check if the user has voted). We maintain a table of only usernames and no relation to ballots. We just need to render it.
Basically, this can be done without changing the existing schema and breaking anything. Will push a patch soon.
@jberkus
Is that what you had in mind?
That's not going to work for orgs with large bodies of voters; you'd have to scroll many pages to reach the "generate results" button.
Voter list really needs its own page/route.
What are you listing there? Is it just the folks that voted, or all voters plus what date they last voted?
Okay, I can shift this to a separate page.
What are you listing there? Is it just the folks that voted, or all voters plus what date they last voted?
These are the people who have voted and the date is when they voted or the last updated their ballot.
Some projects want to track who has and has not voted. Our ballot obfuscation system makes it impossible for the admin to determine this.
As such, we should add an election-level option to record the name of each person who casts a ballot, separate from the ballot itself, and then offer a screen in the Admin UI for this.