Repository navigation
Conversation
Every issue of the board's project, open and closed, in a list that sorts and filters locally, offline too, from a mirror of the project in the index (internal/mirror): read whole once in the background, then only what changed. The assignee and quick filters ask Jira for the keys they find. Cards carry resolution and resolved, as search terms, a sort and columns. The filter builder counts each value over what the rest of the search leaves. The terminal list draws only the rows near the screen, so a list of thousands stays quick.
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.
A view of every issue of the board's project, open and closed, like Jira's issue list but sorted and filtered locally, offline too. In the terminal it's the view after Backlog; in the browser also a page of its own (
/issues/PROJECT/BOARD, All issues in the top bar). List only: lanes make no sense with thousands of issues.internal/mirrorkeeps the project in the index: the first open reads it whole in the background, newest first (the title row says how far it got), after that only what changed (updated >= -Nm), and hourly the keys to drop deleted or moved issues. The browser polls while the first read runs; the TUI and the web share the index./search andFfilter run over the whole project. The assignee filter, mine and the quick filters ask Jira which keys they find (jira.Keys, keys only, 5000 a page), so they mean what they mean on the board; offline the index answers what it can and says what it left out.ResolutionandResolved:resolution:andresolved<7dterms, a resolved sort, columns in the browser, a✕ Won't Domark in the TUI list.Tests:
internal/mirror,internal/index,TestAllIssues*,TestLongListDrawsRowsOnSight,TestFilterBuilderCountsFollowSearch,TestResolvedSearchAndSort,TestAllIssuesCards(web endpoint),cardquery/cardsortJS tests.TestBulkUndo(e2e/tui) now picks Sam by name: with the demo's index the assignee picker ranks people it has seen first, which moved him. Locally the TUI e2e and the board, views, global, search, planning, work, bulk and typing Playwright specs pass.Not measured: the first read of a big real project (only the 23-issue demo), and the browser with 10,000 issues (its list is virtual, but each refresh fetches every card).
The contract recording predates cards asking for
resolutionandresolutiondate, so those paths are ininternal/contract/testdata/allow.txtfor now; re-recording on corne-team (go test ./internal/contract -run TestRecord -record corne-team -project LAN,LWC) verifies them and can drop the lines.