Jira Service Management + AI Voice Agent: Resolve IT Calls Faster With AurionAI

Jira Service Management joins the AurionAI platform

Atlassian's Jira Service Management has become one of the fastest-growing ITSM platforms, especially for teams already using Jira Software and Confluence. With over 45,000 customers, JSM is a major force in IT service management.

Today, AurionAI adds full Jira Service Management support. Employees can now call your IT helpdesk and have an AI voice agent handle the entire workflow — from authentication to resolution — directly through JSM's API.

This makes AurionAI the first voice AI platform to support four major ITSM platforms — Freshservice, HaloITSM, ServiceNow, and Jira Service Management — plus customer service platforms Freshdesk and Zendesk.

31 tools for Jira Service Management

The JSM integration implements the same comprehensive tool set available for every supported ITSM platform:

Incident and request management

• Create issue — the AI extracts request type, priority, and description from natural conversation
• Update issue — add comments, change priority, update custom fields via voice
• Close issue — apply resolution with transition to Done status
• Reopen issue — reopen resolved issues with a documented reason
• Get issue history — retrieve the full activity log and comment timeline
• Reassign issue — move issues between agents or teams

Knowledge base (Confluence)

JSM uses Confluence as its knowledge base backend. The integration searches both:

• JSM knowledge base articles — articles linked to your service desk project
• Confluence spaces — broader organizational knowledge
• Known errors — documented workarounds and root causes

The AI reads relevant articles to the caller and can link them to new issues for agent context.

Change management

• Create change request — submit changes with type (normal, standard, emergency), risk assessment, and implementation plan
• List change requests — view open changes by requester, status, or project
• Get change status — check approval and deployment status

Approvals

JSM's built-in approval workflows are fully supported:

• Create approval request — trigger approval on any issue
• Get approval status — check pending, approved, or declined
• Get pending approvals for caller — list everything waiting for the authenticated caller's decision

SLA tracking

A differentiator for JSM teams: the AI agent is SLA-aware.

• Check SLA status — query time-to-resolution and time-to-first-response metrics
• Report SLA risk — flag issues approaching breach
• Factor SLA into priority — when creating incidents, the AI considers SLA impact

Asset management

• Search assets — find configuration items in JSM Assets (formerly Insight)
• Get asset relationships — map dependencies between CIs
• Report asset issue — create an issue linked to a specific asset

Service catalog

• Get service catalog — list available request types for the caller's service desk
• Create service request — submit catalog requests with required fields

The Atlassian ecosystem advantage

For teams on the Atlassian stack, the JSM integration brings unique benefits:

Confluence as a knowledge base

Unlike other ITSM platforms where KB is a built-in module, JSM uses Confluence — a full-featured wiki. This means the AI agent can search across:

• IT knowledge base articles
• Runbooks and operational procedures
• Onboarding documentation
• Team-specific Confluence spaces

The search is deeper and broader than a typical ITSM knowledge base.

JQL-powered queries

Behind the scenes, the MCP provider translates natural language into JQL (Jira Query Language) for precise issue searching:

project = "IT Service Desk" AND reporter = "john.smith" AND status != Done ORDER BY created DESC

The AI agent builds these queries dynamically based on the conversation context. Callers never need to know JQL exists.

Request types and workflows

JSM's flexible request types are fully mapped. Whether your service desk uses standard ITIL categories or custom request types for software access, hardware provisioning, or account management — the AI agent routes issues correctly based on the caller's description.

How the integration works

The architecture follows AurionAI's standard MCP pattern:

Phone call → Voice AI Agent → MCP Sidecar → JSM REST API v3
                                           → Confluence REST API

Authentication

• API Token (Atlassian Cloud) — email + API token, simplest setup
• OAuth 2.0 (Atlassian Cloud) — app-level authentication for production deployments

API specifics the MCP provider handles

Jira's API has its own conventions that the MCP provider normalizes:

• Issue keys — ITSD-1234 format (project key + number), not GUIDs or integers
• Transitions — status changes require specific transition IDs, not just status names
• Custom fields — use customfield_XXXXX identifiers
• Atlassian Document Format (ADF) — JSM uses ADF for rich text, not HTML or Markdown
• Pagination — cursor-based (startAt + maxResults)

All of this is abstracted away. The AI agent calls create_ticket with natural parameters; the MCP provider handles the translation.

Five-minute setup

1. Enter your Atlassian site URL — yoursite.atlassian.net
2. Add API credentials — API token or OAuth app credentials
3. Select your JSM project — which service desk to connect
4. Map default fields — request type, priority, and assignment group defaults
5. Test and go live — verify the connection and start taking calls

No Atlassian Forge apps to build. No custom workflow post-functions. No scripted automation rules required.

Example conversation

Caller: "Hi, I need access to the Salesforce production environment."

AurionAI: "I can help with that. Could you tell me your name and badge number?"

Caller: "Sarah Chen, badge 7834."

AurionAI: "Thank you, Sarah. I've verified your identity. Let me check if there's a standard process for Salesforce access..."

[AI searches Confluence KB for "Salesforce access request"]

AurionAI: "I found the process. Salesforce production access requires manager approval and takes up to 24 hours after approval. I'll submit the request now. I've created request ITSD-2847 for Salesforce production access, assigned to the Identity and Access Management team. Your manager will receive an approval request shortly. Is there anything else?"

Authentication, knowledge base search, service catalog request creation, and approval routing — all handled by voice through JSM's API.

Four ITSM platforms, one AI agent

With Jira Service Management, AurionAI now supports the four most-used ITSM platforms:

| Platform | Status | Tools | |----------|--------|-------| | Freshservice | Available | 31 | | HaloITSM | Available | 31 | | ServiceNow | Available | 31 | | Jira Service Management | Available | 31 | | Freshdesk | Available | 7 | | Zendesk | Available | 7 |

Every platform uses the same MCP architecture. The AI agent, voice pipeline, authentication, and conversation management are identical. Only the MCP provider differs per platform.

For MSPs and enterprises managing multiple ITSM platforms across teams or clients, this means one AI deployment serves all of them.

Getting started

The Jira Service Management integration is available today on all AurionAI plans.

Already using AurionAI with Freshservice, HaloITSM, or ServiceNow? Adding JSM is a configuration change in the admin dashboard.

New to AurionAI? Request a demo to see the JSM integration live, or start free with 25 minutes of AI voice support.