CTABLE-104 · Operate report controls

Expose report sorting through semantic header buttons

Practice briefStoryIntermediate

Column sorting works only by clicking an unlabeled header. Add named buttons and current sort direction.

Focused work estimate: 2h + prerequisites
Priority in the scenario: Medium
Engineering practice: Accessibility · Sorting

Estimated field mix

Accessibility70%
Frontend30%

Field percentages are editorial estimates of the ticket's engineering focus. They total 100%; they are not measured time, proficiency scores, or ownership evidence.

Your next step

Review it, then add it to your workspace.

The board opens an editable draft; nothing is saved until you confirm it. Sign-in and workspace permissions apply, and Demo boards remain ephemeral.

Use in my work board View project and downloads

Project context

Fictional cooperative Quarry reviews synthetic service-volume reports. Build local report fixtures with empty, missing and delayed values.

Setup prerequisites

Create synthetic report series with explicit missing values.
Stub report loading, sorting and export responses.

Preceding work

Complete these dependencies, or supply their agreed outputs before taking this ticket.

Acceptance criteria

Buttons identify sortable field
Current direction is exposed
Unsortable headers remain plain text

Implementation constraints

Preserve native table navigation.

Verification to include

Sort ascending then descending
Activate with keyboard

Deliverables

Sort controls and keyboard cases

Rollout and recovery

Restore fixed documented ordering if controls fail.

Value of the work

For the engineer: Practice semantic data presentation and robust interaction.

For the team: Inspect whether reporting decisions remain possible without color or pointer use.

Evidence boundaries

Outcome Evidence: Tests, patches, and runbooks are requested deliverables. They become Outcome Evidence only through a qualified Mission and immutable Evidence IDs.

Ownership Evidence: Independent adaptation must be observed under a declared verification policy and cite immutable Evidence IDs. Completing a planning ticket establishes no Ownership Evidence.