Repository navigation
Conversation
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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:dor a click toggles it, remembered per site in prefs.clearleaves it alone.done hidden d/done shown don a future sprint;dtoggles it, remembered in the site state (plan_doneinui.keys).dmatches 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 atd, 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.