Story: labeling alluvial nodes for IRV results #533

Open
opened 2026-05-02 02:21:32 +00:00 by 2nPlusOne · 0 comments
2nPlusOne commented 2026-05-02 02:21:32 +00:00 (Migrated from github.com)

Story Summary

As a user, I want to see the per-round IRV breakdown on the election results, so that I can see each candidate's vote counts.

Problem / Context

Image

The number of votes is shown in the final round's alluvial node, but it would be valuable to see the counts in the other rounds as well so we can view the initial vote distribution and how the votes flowed through the IRV rounds.

Scope

  • In scope:
  • Out of scope:

Acceptance Criteria

  • Given [context], when [action], then [expected result]
  • Given [context], when [action], then [expected result]

Implementation Tasks

  • [Task 1]
  • [Task 2]
  • [Task 3]

Testing Notes

  • New/updated tests identified
  • Manual test steps listed
  • Epic:
  • Related issues:
  • Design docs:

Definition of Done

  • Acceptance criteria met
  • Linked PR is merged to dev
  • Docs updated if setup/process/behavior changed
  • Project board status moved to Done
# Story Summary As a **user**, I want **to see the per-round IRV breakdown on the election results**, so that **I can see each candidate's vote counts**. ## Problem / Context <img width="1333" height="786" alt="Image" src="https://github.com/user-attachments/assets/64a938fd-2dc8-4e77-8d98-253c21a73806" /> The number of votes is shown in the final round's alluvial node, but it would be valuable to see the counts in the other rounds as well so we can view the initial vote distribution and how the votes flowed through the IRV rounds. ## Scope - In scope: - Out of scope: ## Acceptance Criteria - [ ] Given [context], when [action], then [expected result] - [ ] Given [context], when [action], then [expected result] ## Implementation Tasks - [ ] [Task 1] - [ ] [Task 2] - [ ] [Task 3] ## Testing Notes - [ ] New/updated tests identified - [ ] Manual test steps listed ## Dependencies / Links - Epic: - Related issues: - Design docs: ## Definition of Done - [ ] Acceptance criteria met - [ ] Linked PR is merged to `dev` - [ ] Docs updated if setup/process/behavior changed - [ ] Project board status moved to `Done`
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
SSE/WebsiteTheSSEquel#533
No description provided.