Integration profile
8 min read
By Giulia Whitaker · Published on · Updated on
AI Agent for Jira Service Management
The short answer
An AI agent for Jira Service Management comes either from Atlassian or from a third-party vendor. Atlassian’s virtual service agent and Rovo agents work inside JSM. Third-party agents such as Siit, Serval, Ravenna and Harmony answer employees in chat or a portal and connect to JSM for tickets. They differ on five points: how they connect, which account authorizes them, what syncs, where employees ask, and whether an approval comes first.
Which AI agents exist for Jira Service Management?
The market splits on where the agent lives. A native agent is a feature of JSM itself: it uses the JSM portal, request types and knowledge base as they are configured, and it is switched on rather than integrated. A third-party agent is a separate product with its own conversation surfaces. It reaches JSM through a connector, and from there it creates tickets, reads their status, and in most cases syncs updates in one or both directions.
Both families leave JSM in charge of the tickets. The choice is less about replacing the service desk than about where employees ask for help, and how much of the work the agent may carry out before a specialist or an approver steps in.
Inside JSM or in front of it
Atlassian's virtual service agent and Rovo agents run inside JSM. Siit, Serval, Ravenna and Harmony take requests where employees ask and work JSM tickets through a connection.
OAuth for all four
Siit, Serval, Ravenna and Harmony connect through an Atlassian OAuth sign-in.
Approval sits in different places
Siit gates its Create JSM ticket step behind approval where needed, and Serval's prebuilt Jira workflows default to installer approval.
What do Atlassian’s own agents do?
Atlassian documents two agents for JSM. The virtual service agent can give AI answers drawn from a linked knowledge base. Rovo has to be turned on for the instance, and the knowledge base space must be viewable by all logged-in users. Answers follow the customer’s permissions, with one exception Atlassian names: in Slack, only articles open to all logged-in users are used. The same agent runs in Microsoft Teams or in Slack, and Atlassian states that it cannot run in both today.
Rovo agents add the ability to act. Their Create Request tool raises JSM requests on behalf of help seekers from a conversation, using the fields configured on the request type. Fields that cannot be filled in chat, such as Checkbox or Attachments, go to a pre-populated form whose link is sent to the help seeker.
For a team that already works in one chat tool and keeps its knowledge base open to employees, the native route needs no connector at all. Its limits are the ones above: one chat platform at a time, and answers bounded by the visibility of the knowledge base.
Which third-party agents connect to JSM?
Four vendors publish documentation for a JSM connection. Siit’s Triage Agent takes requests in Slack, Microsoft Teams and its employee Portal, and hands specialist work to JSM as a linked ticket. Serval’s help desk agent works across Slack, Teams, email and a web portal, and syncs tickets with JSM projects through its Jira integration. Ravenna presents itself as a Slack-native service desk, with a Portal for people who do not work tickets, and replicates tickets to Jira channel by channel. Harmony pulls JSM tickets into its own inbox and lets its agents export tickets back to JSM.
How do the third-party agents compare?
Every cell restates what the vendor’s own documentation says, with the page given in parentheses; all pages were consulted in October 2026.
| Agent | Connection to JSM | Account that authorizes | What syncs | Employee channels | Approval before action |
|---|---|---|---|---|---|
| Siit | Atlassian OAuth: an admin signs in to the Atlassian site and approves the requested scopes (JSM page) | A JSM admin or Jira site admin; a dedicated Jira user is suggested; reach limited to projects with Browse Projects and request types the user can create (JSM page) | Resolution, assignee, notes and messages, each opt-in per direction; JSM status comes back to the request (JSM page) | Slack, Microsoft Teams, employee Portal (Triage Agent) | Create JSM ticket workflow step with approval gating where needed (JSM page) |
| Serval | Atlassian OAuth 2.0 (3LO), Serval-managed or the customer’s own app; Serval Forge app for ticket syncing (Jira page) | A Jira account with site access approves the scopes picked in permission presets; calls run as that user unless a workflow opts in to the Forge service account (Jira page) | Direction set for new tickets (out, in or two-way); updates to synced tickets flow both ways per Sync Scope toggles; internal notes stay private (Jira page, Syncing) | Slack, Microsoft Teams, email, web portal (Help Desk Channels) | Prebuilt Jira workflows default to installer approval; JSM request types can run as workflows with centralized approvals (Jira page) |
| Ravenna | Atlassian OAuth, authorized while logged in as the dedicated Ravenna user (Setup) | A dedicated standard Atlassian user with a seat, not a managed service account, with JSM agent and space administrator roles; its name appears on every action (Setup) | Per channel, bidirectional or one-way: creation, public and internal comments, mapped status, descriptions, assignee; custom fields one-way as a comment; attachments not synced (Ticket replication) | Slack, Portal (Overview, Portal) | Approval rounds gate a ticket before work proceeds, tracked on the web and in Slack (Approvals) |
| Harmony | Atlassian OAuth, approved by an account with admin permissions (JSM page) | The OAuth integration user; its permissions are audited per project, with a warning if it lacks the JSM agent group for outbound sync (JSM page) | Tickets, statuses, comments and internal notes, assignee and queue, request type data, refreshed every 5 minutes; outbound sync on a toggle; manual export to JSM (JSM page) | Harmony Portal, Slack, Microsoft Teams (Portal, Slack, Teams) | Approval requests answered in the Portal and inside Teams (Portal, Teams) |
The Harmony and Ravenna pages cited do not tie an approval to an action taken in JSM, so their last cells describe each product’s general approval feature.
How to choose an AI agent for JSM
Five questions narrow the list quickly, and each can be answered from the vendor’s documentation before a trial:
- Where employees ask today. If they use both Slack and Teams, Atlassian’s virtual service agent covers one of the two. Among third parties, the channel lists differ more than the feature lists: Serval adds email and a web portal, Ravenna is built around Slack.
- What the agent should do in JSM. Answering, creating a ticket, and updating or resolving one are three levels. Resolving needs the right transitions in the Jira workflow.
- Which account it acts as, and how it signs in. An OAuth sign-in and a username with an API token are different things to grant and to revoke. Prefer a dedicated account, and list the JSM roles each vendor asks for: Ravenna’s requirements are written role by role.
- What crosses back, and what stays private. Check whether sync is chosen event by event or as a whole, and how internal notes travel. Siit sets each event per direction, Serval and Ravenna keep internal notes internal, Harmony refreshes from JSM every 5 minutes.
- Where the approval sits. Before the agent acts, in the agent’s own workflow, or in JSM’s approval workflow. Ask which of the three applies to the actions you plan to automate.
The connection itself, checked point by point from request type to the record left by each action, is covered in the JSM connection checklist.
The tools involved
Siit
Its Triage Agent takes requests in Slack, Microsoft Teams and the employee Portal, and its JSM integration escalates a request into a JSM ticket of the chosen service project and request type.
Serval
Its help desk agent takes requests in Slack, Microsoft Teams, email and a web portal, and its Jira integration syncs tickets with JSM projects once the Serval Forge app is installed.
Ravenna
A Slack-native service desk with a Portal, whose Jira integration replicates tickets per channel through a dedicated Atlassian user account.
Harmony
Its AI agent answers in the Harmony Portal, Slack and Microsoft Teams, and its JSM integration pulls service desk tickets in and lets agents export tickets back to JSM.
Frequently asked questions
Which AI agents work with Jira Service Management?
Two families. Atlassian builds two into the product: a virtual service agent that answers help seekers from the knowledge base linked to the service project, and Rovo agents able to raise requests in chat. Third-party agents connect to JSM from outside: Siit, Serval, Ravenna and Harmony all document a JSM or Jira integration that creates or syncs tickets, while employees ask in Slack, Microsoft Teams, a portal or other chat tools.
Does Atlassian have its own AI agent for JSM?
Yes, two. The virtual service agent answers help seekers from a linked knowledge base once Rovo is enabled, and runs in Microsoft Teams or Slack, not both at once. Rovo agents can use a Create Request tool to raise JSM requests on behalf of help seekers in conversation, and send a link to a pre-filled form for fields they cannot fill in chat.
How does a third-party AI agent connect to JSM?
Through an account that the JSM side authorizes. Siit, Serval, Ravenna and Harmony use an Atlassian OAuth sign-in, approved by an admin or by a dedicated user, and Serval adds a Forge app for ticket syncing. In every case, that account's JSM roles and permissions bound what the agent can see and do.
Do I have to replace JSM to use a third-party AI agent?
No. In the documentation of all four vendors, JSM keeps the tickets: the agent creates them, reads their status and syncs updates. Siit describes the JSM ticket as internal, worked by specialists, while employees stay in Slack, Teams or its Portal. Harmony pulls JSM tickets into its inbox and can export tickets back.