bojackduy/lazyjira

lazyjira

A keyboard-first Jira workspace for the terminal.

<p align="center" <img src="assets/demo.png" alt="lazyjira active sprint board with project navigation and issue inspector" width="100%" / </p

lazyjira brings active sprint tracking, backlog grooming, Kanban flow, issue triage, and rich issue detail into one focused terminal workspace. It keeps lazy/vim muscle memory while making the state of work visible before you drill into a ticket.

Install

npm install -g @bojackduy/lazyjira
lazyjira auth login
lazyjira

Use lazyjira dev to run with bundled fixture data and no Jira credentials.

Why lazyjira

• Overview first: active sprint, backlog, and Kanban are first-class views, not filters over a ticket list.
• Context stays visible: inspect an issue beside the board instead of losing your place in the browser.
• Keyboard-native: j/k, h/l, /, ?, q, Tab, and focused Jira actions keep daily work fast.
• Safe writes: stage changes locally, review the exact Jira operations, then apply them deliberately.

Product Direction

Jira is valuable because it gives teams a shared overview of work:

• What is in the backlog?
• What is in the active sprint?
• What is blocked?
• What is stale?
• What is unassigned?
• What is moving across statuses?

• What needs grooming, ranking, assignment, transition, or comment follow-up?

The terminal app should optimize those workflows first.

Issue details and Confluence-style rich documents still matter, but they are the drill-down surface. The main experience should open on a board, backlog, or workspace overview, not on a single issue reader.

Product Principles

• Overview first, details second.
• Boards and backlog are first-class screens, not just filters over a ticket list.
• Active sprint health should be visible without running reports in the browser.
• Rich ticket/document reading should be beautiful when opened, but should not dominate the default workflow.
• Keyboard actions should be one or two keystrokes for common Jira work.
• The UI should feel native to the terminal, not like a cramped copy of the web page.

• Keep lazy-family navigation muscle memory: j/k, h/l, g/G, /, ?, q, Esc, Tab, Enter.
• High-impact writes need confirmation and clear before/after context.
• Jira errors should be actionable, not vague.