Skip to content

feat(planning): hide done issues in future sprints - #33

Open
cornedor wants to merge 3 commits into
mainfrom
planning-hide-done
Open

cornedor wants to merge 3 commits into
mainfrom
planning-hide-done

Conversation

@cornedor

@cornedor cornedor commented Nov 20, 2026 •

Copy link
Copy Markdown
Owner

Jira leaves done issues out of upcoming sprints in its backlog view, while the Agile API still returns them. Planning now does the same: issues in the Done status category are hidden in future sprints. The active sprint keeps showing its done issues, and the backlog already comes back without them.

The filter is visible and can be turned off with d:

  • Web: a Hide done chip next to Mine/Assignee, on by default; d or a click toggles it, remembered per site in prefs. clear leaves it alone.
  • Terminal: the view line shows done hidden d / done shown d on a future sprint; d toggles it, remembered in the site state (plan_done in ui.keys).

d matches the Hide done toggle in My Work. Counts and points follow what is shown ("1 of 2 cards"), as with a filter. While a done issue is hidden in a sprint, J/K ranking (and drag-ranking in the terminal) waits and points at d, the same rule as an active filter.

Tests: new TUI test (fails on main) and a Playwright test that marks a planned sprint's issue done and checks hiding, d, the reload and the chip click. Help, key references, planning guide and nl catalogs updated.

A done issue moved into a planned sprint is there but hidden, so the move says so (web: "DEMO-17 is done: hidden in Sprint 13 · d shows it"; terminal: the same in the status line). The planning fuzz models the hidden issues too.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant