Stop context-switching between issue trackers. The Agent gives you a unified view of issues across all your connected platforms, and can create, update, and organize them from the chat.
What You Get
Unified Issue View
A single card showing issues from every connected platform:
- Grouped by status, platform, or priority — your choice
- Platform indicators — see which tool each issue lives in
- Click to expand — opens full issue detail in a side panel with comments, history, and status
Per-issue quick actions
Hover any issue row to reveal inline action buttons:
- Close / Reopen — one-click state toggle
- Reply — pre-fills a comment composer
- Change priority — pick from Critical / High / Medium / Low / None
- Reassign — re-route to another teammate
- Copy link — grab the platform URL
- Open — jump to the original issue in GitHub / Linear / Jira / Asana
Issue Creation
Create issues on any connected platform directly from chat:
- GitHub Issues — with labels, assignees, and milestones
- Linear Issues — with team, project, priority, and cycle
- Jira Tickets — with project, type, priority, and sprint
- Asana Tasks — with project, section, and assignee
The Agent returns a confirmation card with a direct link to the created issue.
Batch operations & re-classification
Check boxes next to multiple issues to reveal a bulk action bar:
- Close / Reopen all — one action across every selected item
- Reassign all — pick a new owner for the set
- Set priority — bulk re-prioritize to Critical / High / Medium / Low / None
- Re-classify — add / remove / replace labels across the selection (e.g. move 5 “bug” issues to “tech-debt”)
- Reply to all — post the same comment on every selected item
- Link to plan — attach the whole selection to a Kasava plan
- Batch creation — “Create issues for each of these bugs” still works the same way; preview-before-execute keeps you in control
Blocker Chains
Visualize what’s blocking what across your entire project:
- Dependency chains — see the full blocked-by/blocking tree
- Code dependencies — when blockers are tied to code changes
Example Prompts
| What you ask | What you get |
|---|
| ”Show all open issues” | Unified issues card |
| ”What’s open in Linear?” | Platform-filtered issue list |
| ”Create a GitHub issue for the login bug” | Issue created + confirmation card |
| ”File a Jira ticket: auth tokens expiring too fast, P1” | Jira ticket with priority |
| ”What’s blocked right now?” | Blocker chain visualization |
| ”Create issues for: fix nav, update API docs, add rate limiting” | Batch creation with preview |
| ”Close all the issues related to the auth refactor” | Bulk close with confirmation |
| ”Set priority of ENG-123 to urgent” | Single-issue priority change |
| ”Reassign PROJ-456 to @jamie” | Single-issue reassignment |
| ”Re-classify these issues as tech-debt instead of bug: ENG-10, ENG-11, ENG-12” | Bulk label swap |
| ”Close these issues: 47, 48, 49” | Uniform batch close in one call |
Why It Matters
One interface for all your issue trackers. Whether your team uses GitHub, Linear, Jira, or Asana (or a mix), the Agent gives you a unified view and lets you take action without switching tabs. Blocker analysis helps you focus on the work that unblocks the most progress.
The Agent respects your platform’s conventions — it’ll set the right fields for each tool (sprints for Jira, cycles for Linear, milestones for GitHub).
