Skip to content

[Sankey] Interact with Sankey rendered data #1632

@mossy426-cdc

Description

@mossy426-cdc

Story Key: sankey-view:interact-with-view

User Story

As a MicrobeTrace user, I want to interact with the Sankey view data directly, so that I can inspect, select, and drill into the data shown in the view.

Workflow / Use Case

Select, hover, pan, zoom, expand, or otherwise interact with the rendered data in the Sankey view and verify the app updates the expected detail state.

Expected Behavior

Sankey interactions expose correct tooltips, selections, drilldowns, and synchronized state without leaking stale selections or rows.

Acceptance Criteria

  • Given the linked QA tracker scenarios, when the user performs the covered Sankey workflow, then the expected behavior remains true for each listed fixture and spec.
  • Given the listed Cypress specs are run, when they pass, then this story has automated evidence for the grouped acceptance checks.
  • Given linked QA evidence changes, when this story is regenerated, then tested fixtures, specs, and coverage notes stay aligned with the current QA trackers.

QA Tracker Evidence

  • sankey-view:S011
  • sankey-view:S021
  • sankey-view:S022

Tested Against

Fixtures

  • TestStyleNodelist_snp.csv
  • TestStyleEdgelist_snp.csv

Cypress Specs

  • cypress/e2e/journeys/flows/sankey-controls-uploaded.cy.ts

Coverage Notes
Grouped from 3 QA tracker row(s): Node tooltip on uploaded data; Link tooltip on uploaded data; Node drag updates layout and link geometry. Source areas: Interaction.

Source References

  • User story row: docs/user-stories.csv#L92
  • Branch: dev
  • Commit: f4b481eb2242d2a89251300c3b94eaf09c842e04
  • Generated by: mossy426-cdc
  • Epic / Feature Group: Sankey
  • Story Type: Visualization Behavior
  • Priority: P2
  • Story Review Status: Draft
  • Source Confidence: High
  • Last reviewed: 2026-04-22

Story Notes

Generated as a grouped user story from QA tracker evidence. Review title and behavior language before enabling story_sync.

Definition of Done

  • Acceptance criteria are satisfied.
  • Linked QA tracker evidence remains current.
  • Relevant Cypress coverage remains passing or any coverage gap is documented.
  • Expected behavior remains distinguishable from bug or enhancement requests.

Manual Notes

Reviewer notes added below this line are preserved by future sync runs.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions