Hermes Agent Jira Integration
Integrate Hermes with Jira for AI-powered ticket management, sprint planning, and team workflows.
Quick answer
Use Hermes Agent with Jira when the agent needs to create tickets, update sprint work, query JQL, and summarize project status inside an existing Atlassian workflow.
Watch it in action
Hermes Agent Just Became a Project Manager — Nemanja Mirkovic
Nemanja Mirkovic shows how to use Hermes Agent's Kanban board as a project manager for multi-step tasks. The demo covers installing the Kanban plugin via /update, assigning tasks to writer and designer profiles, watching cards move from to-do to in-progress to done, and using the card comment system to give feedback and redirect agents mid-task. The video also draws a direct comparison to GitHub Issues as an alternative orchestration layer for similar workflows.
- 0:00Introduction — Kanban board as project manager
- 0:47Installing via /update and running /kanban
- 1:52First task: research brief → X post + image
- 2:30Kanban board populates: writer and designer assigned
- 3:44Profiles explained: different models per agent
- 4:30Writer agent completes; designer starts image generation
- 6:45Card comments: how to give feedback to an agent mid-task
- 7:30Manual card creation and parent/child dependencies
- 8:30Finished deliverable: image and copy output
- 9:10Next video preview: GitHub Issues as orchestration layer
Features
- ✓Ticket creation and updates
- ✓JQL queries
- ✓Sprint management
- ✓Status transitions
- ✓Comment threads
- ✓Assignee management
Setup path
- 1Generate Jira API token from id.atlassian.com
- 2Configure Jira URL and credentials in Hermes
- 3Set default project and board
- 4hermes restart
Why Jira CTR is strong
Jira searchers are explicit and commercial: they want an AI agent that fits an existing ticketing workflow. Keep this page focused on Jira setup and route lighter project-management comparisons to Linear.
- •Keep the current title, meta description, and H1 unchanged.
- •Add FAQ coverage for API tokens, JQL, comments, and sprint updates.
- •Use related links to strengthen GitHub and Slack workflows around engineering handoffs.
Best Jira workflows
Jira is best when Hermes needs to operate in a structured enterprise issue tracker rather than a free-form task list.
- •Create tickets from incidents, customer requests, or QA findings.
- •Use JQL to summarize sprint scope and blocked issues.
- •Post comments or status updates after a code or product review.
Using the Kanban Board as a Project Management Layer
Nemanja's workflow treats the Hermes Kanban board exactly like a lightweight Jira or Trello — a place to define work, assign it, track status, and leave feedback. The orchestrator breaks a natural-language request into cards, assigns each to the appropriate profile (writer, designer, researcher), and the dispatcher loop claims and executes cards in order. Cards that can run in parallel do so automatically.
Profiles Enable Cost-Optimal Agent Routing
A key insight from the video is that profiles let you use different models for different tasks. You do not need to run an expensive GPT-5.5 call for every step. An image-generation profile can point at a cheaper image API while a reasoning-heavy analyst profile uses a more capable model. This is the same optimization as routing Jira ticket categories to the right team — the board makes it automatic.
Card Comments as Mid-Task Steering
The Kanban card interface includes a comment field. If the output from an agent is not right, you can leave a comment on the card — tell it to change the tone, redo the image, or adjust the copy — and the agent picks that up on its next iteration. This is a lighter-weight feedback loop than restarting the whole task.
Kanban vs GitHub Issues for Orchestration
Nemanja explicitly previews a comparison: the Hermes Kanban is native and works out of the box, while GitHub Issues as an orchestration layer offers the benefit of external visibility, existing team workflows, and webhook integration. For teams already in Jira or Linear, connecting those issue trackers to Hermes profiles via webhooks or the MCP layer follows the same pattern.
Common setup issues
- Kanban tab is not appearing in the Hermes dashboard — Run /update in the Hermes chat to pull the latest version, then run /kanban to initialise the plugin. After that, open the dashboard and you will see the Kanban tab.
- Authentication token error after adding multiple profiles — If you add new profiles and the Kanban stops working, check that the API token is copied to all profiles. The Nemanja video shows this exact issue mid-recording — open each profile in settings and re-paste the token.
- Image generation agent takes too long (7-10 minutes) — Image generation with GPT image tools is slow by nature. Consider running the writing task first, then kick off image generation as a parallel card so the overall workflow is not blocked waiting.
- Agent finishes but card stays in progress — Manually move the card to 'ready' or 'done' from the Kanban UI. The agent may have completed its work but failed to update the card state if it hit a token limit or connectivity issue.
FAQ
What credentials does Hermes need for Jira?
Hermes typically needs your Jira site URL, account email, an Atlassian API token, and default project or board settings so created tickets land correctly.
Can Hermes run JQL queries?
Yes. JQL queries are useful for sprint summaries, blocked-ticket checks, project reports, and finding issues that need follow-up.
Should Jira users also connect GitHub?
Usually yes for engineering teams. Jira tracks work, while GitHub gives Hermes access to pull requests, CI status, repository context, and code-review follow-ups.
Can Hermes Agent act as a project manager for multi-step workflows?
Yes. The Kanban board lets Hermes break a task into cards, assign each to a specialist agent profile, run them in parallel or sequence, and deliver a combined output — behaving like a project manager routing work to the right team members.
How does the Hermes Kanban board compare to Jira?
The Hermes Kanban board is agent-native: cards are created and claimed by AI agents rather than humans. Jira is better for large team workflows, compliance, and long-lived ticket history. Hermes Kanban is better for autonomous AI pipelines where tasks are created and resolved in minutes.
Can I use Hermes with both Jira and the Kanban board?
Yes. A common pattern is to use Jira as the source of truth for team-visible work and have Hermes agents pick up Jira tickets, do the work, and update ticket status using the Jira API integration alongside the internal Kanban for agent-to-agent coordination.
How do I give feedback to an agent mid-task on the Kanban?
Open the card in the Kanban dashboard and use the comment field. Write your feedback — change direction, adjust scope, redo a specific step — and the agent will pick it up on its next loop iteration.