Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Problem: Lack of clarity regarding failed elections #3426

Open
mochet opened this issue Jul 30, 2022 · 1 comment
Open

Problem: Lack of clarity regarding failed elections #3426

mochet opened this issue Jul 30, 2022 · 1 comment
Labels
community-dev issue suitable for community-dev pipeline design Description of a feature scope or detailed requirements enhancement New feature or request mainnet Mainnet scope query-node bug caused by query node defects scope:council should-have SP:5 to-triage

Comments

@mochet
Copy link
Collaborator

mochet commented Jul 30, 2022

Example election: https://dao.joystream.org/#/election/past-elections/0000000j

image

This election failed for some reason, but to an end user there is no explanation of why.
Based upon QN research this election failed because the requirement for at least 5 council members to get revealed votes did not happen.

At minimum I would suggest the following:

  • An easily distinguishable signifier of whether an election failed or succeeded
  • If it failed, a human readable reason for why (i.e. "Not enough candidates", "Not enough votes")
  • If it isn't possible to provide a distinct reason for failure, ideally a tooltip/popup that explains to the end-user the possible reasons for an election having failed.

┆Issue is synchronized with this Asana task by Unito

@traumschule
Copy link
Collaborator

From what i can see there is no definitive outcome status available via QN.

query { electionRounds { id isFinished endedAtTime
  referendumStageVoting {startedAtBlock} referendumStageRevealing {startedAtBlock}
  candidates { createdAt votesReceived{voterevealedeventcastVote{createdAt}}} castVotes {stakeLocked} }
}

This incomplete query enables to infer the outcome based on

  • was there a voting / revealing stage
  • how many candidates (consider withdrawn) => at least council size +1
  • how many cast votes => at least council size
  • how many revealed votes => seems reasonable election would fail not enough votes for min. 5 candidates are revealed
  • elected candidates

In the current design the ENDED AT date has a prominent place but poor visibility. I could see combined stats box: failed on MM/DD/YYYY / elected on MM/DD/YYYY with a tooltip:

candidates / withdrawn
votes / revealed

@traumschule traumschule added design Description of a feature scope or detailed requirements to-triage query-node bug caused by query node defects community-dev issue suitable for community-dev pipeline mainnet Mainnet scope labels Oct 25, 2022
@dmtrjsg dmtrjsg removed their assignment Dec 8, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
community-dev issue suitable for community-dev pipeline design Description of a feature scope or detailed requirements enhancement New feature or request mainnet Mainnet scope query-node bug caused by query node defects scope:council should-have SP:5 to-triage
Projects
None yet
Development

No branches or pull requests

4 participants