Jira issues form natural hierarchies (epic > story > subtask), but lazyjira currently treats the issue list as flat. There is no way to navigate to a parent issue, and drilling into children is also not straight-forward.
Proposal
Three navigation keys on top of the existing issue list:
- Enter drills down: replaces the list with the selected issue's children. On a childless issue it moves focus to the detail pane.
- Backspace drills up: replaces the list with the current issue's parent.
- Esc pops back: restores the previous list and cursor position (full UI state, including which panel and tab had focus).
The same Enter key works from the info panel's Sub and Link tabs: pressing it on a subtask or linked issue pulls that issue into the main list as a single-item view, so you can inspect its metadata before drilling further.
Each drill direction gets a short dynamic tab label ("Child", "Parent", "Link") so you always know what you are looking at. Esc walks the stack back to the original query result.
Switching JQL tabs clears the navigation stack.
I modeled this after lazygit's context stack (branches > commits > files, Esc to pop), adapted for Jira's issue hierarchy.
Does this match how you see issue navigation working? Happy to submit a draft PR.
Jira issues form natural hierarchies (epic > story > subtask), but lazyjira currently treats the issue list as flat. There is no way to navigate to a parent issue, and drilling into children is also not straight-forward.
Proposal
Three navigation keys on top of the existing issue list:
The same Enter key works from the info panel's Sub and Link tabs: pressing it on a subtask or linked issue pulls that issue into the main list as a single-item view, so you can inspect its metadata before drilling further.
Each drill direction gets a short dynamic tab label ("Child", "Parent", "Link") so you always know what you are looking at. Esc walks the stack back to the original query result.
Switching JQL tabs clears the navigation stack.
I modeled this after lazygit's context stack (branches > commits > files, Esc to pop), adapted for Jira's issue hierarchy.
Does this match how you see issue navigation working? Happy to submit a draft PR.