Repository navigation
feat(tracker): previous/next navigation in the issue panel - #11134
Open
MichaelUray wants to merge 1 commit into
Open
MichaelUray wants to merge 1 commit into
MichaelUray wants to merge 1 commit into
Conversation
An opened issue could only be left by going back to the list, there was no way to step to the neighbouring issue. The view UpDownNavigator component still existed but was no longer used since the panel header redesign dropped the navigator slot, and it relied on the global focus provider, which is taken over by the sub-issue list inside the issue panel. UpDownNavigator now looks up the list that contains the opened document (ListSelectionProvider.Find), lets that list resolve the previous/next item so grouping and sorting are respected, and opens it. The buttons are only shown while such a list is present and navigation is not restricted. Alt+ArrowUp / Alt+ArrowDown do the same unless the user is editing text. EditIssue shows the navigator in the panel header. Fixes hcengineering#9510 Signed-off-by: Michael Uray <michaeluray@users.noreply.github.com>
MichaelUray
force-pushed
the
feat/issue-prev-next-navigation
branch
from
October 26, 2026 11:28
75f738e to
823f1ee
Compare
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.
Fixes #9510
Problem and change
An opened issue could only be left by going back to the list, there was no way to step to the neighbouring issue. The view UpDownNavigator component still existed but was no longer used since the panel header redesign dropped the navigator slot, and it relied on the global focus provider, which is taken over by the sub-issue list inside the issue panel.
UpDownNavigator now looks up the list that contains the opened document (ListSelectionProvider.Find), lets that list resolve the previous/next item so grouping and sorting are respected, and opens it. The buttons are only shown while such a list is present and navigation is not restricted. Alt+ArrowUp / Alt+ArrowDown do the same unless the user is editing text. EditIssue shows the navigator in the panel header.
Tests
New unit tests
plugins/view-resources/src/__tests__/upDownNavigation.test.ts. Checked manually on a self-hosted instance: the arrows in the issue panel header and Alt+Up/Alt+Down move to the previous/next issue of the list behind the panel, also across group boundaries; nothing happens while typing in the description; hovering the sub-issue list inside the panel does not change the target.Notes
The order is the list's own keyboard navigation order (the same as ArrowUp/ArrowDown in the list). In grouped lists that order can differ from the rendered order in some cases; that is existing list behaviour and not changed here.