Summary
Add a Jira "My Tickets" view to h-code that surfaces assigned and recently viewed Jira issues, providing a quick-launch surface for starting or resuming agent threads tied to Jira work items.
Motivation
- Developers spend significant time context-switching between h-code and Jira to find what to work on next
- The existing seeded-work-item flow (Jira → slack → manager inbox) is manager-agent-oriented and not suited for individual developer daily workflow
- A "My Tickets" view would let developers see their Jira backlog directly in h-code, pick a ticket, and launch a worker thread with the ticket context pre-seeded
Proposal
A sidebar or panel that lists:
- Assigned to me — Jira issues assigned to the authenticated user, ordered by priority/updated
- Recently viewed — issues the user has interacted with in h-code
- Watching — issues the user is a watcher on
Each ticket should show:
- Issue key (e.g. PROJ-1234)
- Summary/title
- Status, priority, assignee
- Quick action: "Start thread" (creates a worker thread with the Jira issue title + link as context)
Integration points
- Reuse the existing Jira API client / MCP integration for data fetching
- The Jira base URL is already configured per-project in the Todo panel (
jiraBaseUrl)
- Could reuse the seeded-work-item writeback infrastructure for bidirectional sync (marking done in h-code → transitioning in Jira)
Scope decisions needed
- Where exactly in the UI does this live? Sidebar panel? Command palette command? Separate route?
- How is Jira auth handled? Is it the user's personal Jira token or a shared project token?
- Does this belong in the core app or as a MCP-server-provided view?
Related
Summary
Add a Jira "My Tickets" view to h-code that surfaces assigned and recently viewed Jira issues, providing a quick-launch surface for starting or resuming agent threads tied to Jira work items.
Motivation
Proposal
A sidebar or panel that lists:
Each ticket should show:
Integration points
jiraBaseUrl)Scope decisions needed
Related
mcp.listServers/mcp.toggleServer)SeededWorkItemWritebackReactor) already handles Jira → h-code work item flow