Jira Service Management

Rest of world Report an error

Panel rating · 6 judges · How to read the stars

Category median

Sovereignty: 1 of 6 dimensions proven

0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.

by Atlassian Corporation · www.atlassian.com

Report an error on this page Is this your product? →

Link to this page

Jira Service Management: AI-assisted analysis on whats-best.ai Jira Service Management: AI-assisted analysis on whats-best.ai (dark)

Add ?theme=dark to the image address for dark backgrounds. The badge shows the category and the month of the latest evaluation, and EU-Made where that is the product’s provenance. It never shows a score.

Jira Service Management at a glance

Vendor
Atlassian Corporation
Headquarters
Incorporated in the United States source, captured 8 Nov 2026
Data hosting
Not stated on the vendor’s pages as of 16 Nov 2026
Free plan
Yes, per the vendor’s own page source, captured 15 Sep 2026
Panel verdict
The AI panel rates Jira Service Management 2.5/5, the mean of 6 judges. Jira Service Management, Atlassian's cloud service desk, earns its top scores on integrations, where five of six judges gave 7 for over 1,000 marketplace apps, REST APIs with rate limits, a sandbox and a guided Salesforce import. how scores are made
As of
Vendor pages captured 31 Aug 2026 to 16 Nov 2026; evaluated by the panel 18 Nov 2026. all sources

Jira Service Management alternatives, European ones first →

Read this page as one judge. Each weighs the same scores by what they care about.

The panel's verdict

Jira Service Management, Atlassian's cloud service desk, earns its top scores on integrations, where five of six judges gave 7 for over 1,000 marketplace apps, REST APIs with rate limits, a sandbox and a guided Salesforce import. The data protection judge scored 0 on every criterion — no other judge went below 2 — and the other five cluster at 6-7 on ticketing core, knowledge self-service, customer data protection and integrations. Sovereignty is the weakest criterion for those five, at 2-3: contracting entities sit in the United States and Australia, hosting is stated only as Amazon Web Services with no region, and the privacy policy describes transfers to wherever Atlassian or its providers operate. Pricing transparency genuinely splits those five, 5 to 7: they credit unusually detailed per-tier tables and a $1-per-resolution AI agent but differ on computability, since captured pages give different figures for Standard ($20 versus $21.50 per agent per month) and Premium ($51.42 versus $55.28 per agent per month), Enterprise sits behind contact sales, and annual saving is stated only as up to 17%.

Report an error

Speaks for it

  • Integrations took 7 from five of six judges for over 1,000 marketplace apps, REST APIs with rate limits, a sandbox, and a guided Salesforce import mapping accounts to organizations
  • Queues come with list, board and calendar views, JQL search, SLA goals on business-hours calendars, and queues that surface work nearing an SLA breach
  • A Confluence-powered knowledge base surfaces articles in channels before a request is raised, with the AI agent at $1 per resolution and 1,000 assisted conversations per month on Premium
  • Permission schemes give issue-level security and restricted comment and work-log visibility, audit logs start on Standard, and AES-256 encryption at rest is stated
  • Per-agent monthly prices are public for Free, Standard and Premium, with per-tier storage, automation steps, uptime and support limits, and Free covers 3 agents with unlimited customers

Report an error

Held against it

  • Sovereignty drew 3 from four judges, 2 from one and 0 from the data protection officer — contracting entities in the United States and Australia, hosting named only as Amazon Web Services with no region, and transfers described as global to wherever Atlassian or its providers operate
  • The captured pricing pages give different figures for Standard ($20 and $21.50 per agent per month) and Premium ($51.42 and $55.28 per agent per month), Enterprise is contact sales, and we found no public information on VAT treatment or minimum term
  • Documented channels are email, a customer portal and chat through Slack and Teams, with phone calls and voicemails turned into alerts routed on an on-call schedule, and we found no public information on messengers, social channels or one shared conversation history
  • The permissions overview states plainly that field-level permissions are not supported, and we found no public information on ticket-content redaction, per-queue retention rules or requester erasure workflows
  • We found no public information on macros, merge and split, skills- or load-based assignment, or first-response and resolution reporting by agent and queue

Report an error

Best for

  • You run IT, HR or facilities service teams inside the Jira ecosystem and want configurable queues, JQL search and SLA goals on business-hours calendars
  • You want deflection you can meter — articles surfaced in channels before a request is raised, AI at $1 per resolution, and 1,000 assisted conversations per month on Premium
  • Your roadmap leans on APIs and apps — REST endpoints with rate limits, bulk customer and organization APIs, a sandbox and a 1,000+ app marketplace
  • You are starting small — the Free plan is free forever for 3 agents with unlimited customers

Report an error

Avoid if

  • Your compliance review requires a named hosting region — ask the vendor: the public pages we read do not show it
  • Your customers reach you mainly through messengers or social channels — the documented channels are email, a customer portal, chat in Slack and Teams, and phone calls turned into on-call alerts
  • You must fix an annual invoice before committing — the captured pages give different Standard and Premium figures, Enterprise is contact sales, and annual savings are stated only as up to 17%
  • You need field-level restrictions on ticket data — the permissions overview states field-level permissions are not supported

Report an error

The scores

Panel median The median of the judges’ scores per criterion. Each label opens its reasoning below.
Scores per criterion, in stars out of 5
Criterion Panel median
Ticketing, queues & SLA 3 of 5
Channels in one queue 2.5 of 5
Knowledge base & deflection 3 of 5
Customer data protection 3 of 5
Integrations & API 3.5 of 5
European sovereignty 1.5 of 5
Pricing transparency 3.5 of 5

Ticketing, queues & SLA

panel disagrees Show reasoning
How this is scored

The engine: how work is routed, prioritised, escalated and measured — and whether an agent can find the ticket they need among ten thousand.

0 — Not a ticketing tool: requests stay in a shared mailbox or chat with no ticket, owner or status of their own.

3 — Tickets with assignment, a status and a conversation history, worked from a shared inbox with views or filters.

5 — Tickets routed by rules or automations to teams or agents, priorities and statuses, SLA targets or response-time reporting, and search across tickets.

8 — Business-hours-aware SLA policies per queue or customer with breach warnings and escalation, macros and triggers, merge and split, skills- or load-based assignment, and reporting on first-response and resolution time by agent and queue.

10 — The workload is managed rather than merely tracked: capacity-aware assignment, SLA per contract with reporting an account manager could show a customer, audit of every status change, and search that finds the ticket from a half-remembered phrase.

Report an error

The Support Lead

Queues are documented in real depth — custom and dynamic queues, list, board and calendar views, filters by status, assignee and priority, and Jira Query Language search — and SLAs have JQL-defined goals, business-hours calendars, pause conditions and queues that surface work by how close it is to breaching. Escalation for major incidents is listed plan by plan. We found no public information on reporting of first-response and resolution time by agent or queue, macros, merge and split, or skills- or load-based assignment. 6 7 2

Report an error

The Agent Advocate

The queues documentation is the real thing: customizable queues with dynamic per-viewer assignment, JQL search, and queues that surface work by how close it is to breaching an SLA, with goals set via JQL, pause conditions and business-hours calendars in the SLA articles, plus escalation by plan and per-plan automation steps. But I found no public information on macros, merge and split, or first-response and resolution reporting by agent and queue, so it stops short of the top band — six years of replies and no documented canned response is a real gap. 6 7 2

Report an error

The Data Protection Officer

Queues are real: preconfigured and custom queues with list, board and calendar views, JQL search, and urgency queues that surface work items approaching an SLA breach, while SLA goals are defined per project with business-hours calendars and pause conditions and escalation runs manual, automatic or API-driven depending on plan. This sits in the upper-middle band. We found no public information on macros, merge and split, skills- or load-based assignment, or first-response and resolution reporting by agent and queue, which is what separates a managed workload from a tracked one. 6 7 2 14

Report an error

The Shop Operator

Queues are genuinely configurable — preconfigured or custom, with list, board and calendar views, filters on status, assignee, priority and custom fields, and JQL search that would find the half-remembered ticket — and SLAs run on business-hours calendars with goals defined by query and queues that surface work close to breaching. Escalation is manual, API-based or automatic depending on plan. We found no public information on macros, merge and split, skills- or load-based assignment, or first-response and resolution-time reporting by agent and queue. 6 7 2

Report an error

The Integrator

Queues are documented with filter criteria, dynamic per-agent queues, list, board and calendar views and JQL search, and SLAs are configured per project with goals defined as queries, pause conditions and business-hours calendars; queues can even be built around how close work sits to breaching an SLA. Escalation appears as manual, automatic and API on the higher plans. We found no public information on merge and split, skills- or load-based assignment, or first-response and resolution reporting by agent and queue, so the documented engine stops short of the top of the scale. 6 7 2

Report an error

The Skeptic

Queues come with list, board and calendar views, filters on status, assignee, priority and custom fields, JQL search, and SLA goals defined by JQL with business-hours calendars plus queues that surface work nearing an SLA breach — that is working routing-and-SLA ticketing. We found no public information on ticket escalation paths, macros, merge and split, skills- or load-based assignment, or first-response and resolution reporting by agent and queue. 6 7

Report an error

Channels in one queue

panel disagrees Show reasoning
How this is scored

Email, chat, phone, portal, messengers and social — judged on what actually lands in the same queue with the same history, not on how many channel logos the marketing page carries.

0 — No customer channel of its own; the product only works on tickets entered by hand or by another system.

3 — Email turned into tickets, with a web form or one further channel.

5 — Email, a web form or portal and live chat or a messenger landing as tickets in one inbox, with the customer's earlier conversations visible to the agent.

8 — The above plus telephony integration with call logging, at least one messenger (WhatsApp or similar) with its consent handling stated, social channels, and a customer portal where a requester can see their own tickets — all in one history.

10 — Channel is an implementation detail: every channel including voice and messengers writes to one conversation with one history, agents answer from one screen, and the customer can move between channels mid-issue without repeating themselves.

Report an error

The Support Lead

Email channels with a monitoring endpoint, a customer portal with request forms, chat connected through Slack and Microsoft Teams, and phone calls and voicemails turned into routed work items are all documented. We found no public information on WhatsApp or other messengers with their consent handling, social channels, or whether every channel writes to one shared conversation history. 8 9 11 1 2

Report an error

The Agent Advocate

Email channels, a customer portal with request forms, and chat through Slack and Microsoft Teams are all documented, and phone calls and voicemails are turned into alerts routed by the on-call schedule. What I miss is the join: the captured pages do not show these channels writing into one conversation with one history, or the customer's earlier conversations on the agent's screen, and we found no public information on messenger consent handling or social channels. 8 9 11 2

Report an error

The Data Protection Officer

Email channels, a customer portal with request forms, chat through Slack and Microsoft Teams, and phone calls and voicemails turned into items routed by on-call schedule all reach the queue system, with AI agents covering chat, email, mobile, embedded widgets and the support site. We found no public information on customer messengers such as WhatsApp, on consent handling for any channel, or on whether a requester can see their own past tickets in the portal, so I stop short of the higher band. 8 9 11 1 2

Report an error

The Shop Operator

Email channels, a customer portal collecting requests through forms, and chat via Slack and Microsoft Teams are documented, with phone calls and voicemail turned into alerts routed on an on-call schedule. What I cannot see is WhatsApp or another messenger with its consent handling, social channels, or call logging landing in one history — we found no public information on those. 11 9 2 8

Report an error

The Integrator

Email channels, a customer portal that collects requests, and chat via Slack and Teams are documented, with AI agents answering across chat, email, mobile, embedded widgets and the support site. The pricing page documents turning phone calls and voicemails into alerts routed on an on-call schedule, which is paging rather than customer telephony landing in the queue. We found no public information on WhatsApp-style messengers, social channels, or consent handling for messengers. 8 9 11 2

Report an error

The Skeptic

Email channels and a customer portal with request forms land as work items, and chat exists through the Assist app in Slack and Microsoft Teams, which clears the email-plus-portal bar. But the product page counts chat, email, phone and support-site logos while the pricing detail turns phone calls and voicemails into alerts routed on an on-call schedule, and we found no public information showing these channels share one queue and one conversation history, nor any messenger consent handling. 8 9 11 2

Report an error

Knowledge base & deflection

panel disagrees Show reasoning
How this is scored

Whether the product reduces the number of tickets as well as organising them: public help centre, article workflow, suggestions to agents and to customers.

0 — No knowledge base or self-service of any kind; the product is a ticket inbox only.

3 — A knowledge base or FAQ with articles, internal or public, that agents can link in replies.

5 — A searchable public help centre with categories and its own branding, draft and publish states, and agents able to insert or suggest an article in a reply.

8 — Article suggestions to the customer before they submit and to the agent while they answer, multilingual articles, review dates or versioning that flag stale content, and reporting on which articles deflect.

10 — Knowledge is a managed asset: gaps identified from unanswered tickets, article performance measured against ticket volume by topic, versioned content with approval, and deflection reported as a number the team can act on.

Report an error

The Support Lead

The Confluence-powered knowledge base is documented with a customizable help center, articles surfaced to customers before a request is even raised, articles shareable on work items, and AI that spots knowledge gaps and drafts new articles. What I could not find is review dates or versioning that flag stale content, article suggestions to the agent while answering, or reporting on which articles deflect. 1 10 11 1

Report an error

The Agent Advocate

A Confluence-backed knowledge base, a customizable help center with articles, forms and an AI assistant, articles surfaced in-channel before a request is even raised, and AI documented to spot knowledge gaps and draft new articles — that is genuine deflection, the kind that cuts ticket volume. I found no public information on article versioning or review dates, multilingual articles, or reporting on which articles actually deflect, which is what separates a help centre from a managed asset. 1 10 1 11

Report an error

The Data Protection Officer

A Confluence-powered knowledge base behind a customizable help center, articles surfaced to customers before a request is raised, agents sharing articles on work items, 24 supported languages, and AI that spots knowledge gaps and drafts new articles — gap detection is the beginnings of treating knowledge as a managed asset. We found no public information on article versioning, staleness flags, or deflection reported as a number a team could act on. 10 1 1 2 11

Report an error

The Shop Operator

Deflection is more than a promise here: articles are surfaced in channels before a request is even raised, agents share knowledge base articles on work items, AI spots knowledge gaps and drafts new articles, and the virtual agent runs on metered resolutions at $1 per resolution with 1,000 assisted conversations a month on higher tiers — a deflection number I can watch against December's ticket volume. The knowledge base is Confluence-powered behind a customizable help center. We found no public information on article versioning with approval or reporting on which articles actually deflect. 10 1 2 2

Report an error

The Integrator

A knowledge base powered by Confluence sits behind the portal and help centre, agents can share articles with customers on work items, and articles are surfaced in channels before a request is even raised — genuine deflection, plus AI spotting knowledge gaps and drafting articles. We found no public information on multilingual articles, review dates or versioning, or reporting on which articles deflect, which is what the top of this criterion asks for. 1 10 11 1

Report an error

The Skeptic

A Confluence-powered knowledge base sits behind a customizable help center with articles and forms, articles are surfaced in-channel to resolve issues before a request is raised, and AI is documented as spotting knowledge gaps and drafting new articles — a real deflection story. We found no public information on article suggestions to the agent mid-reply, review dates or versioning that flag stale content, or reporting on which articles deflect, and multiple help centers only begin at Premium. 1 10 11 1

Report an error

Customer data protection

panel disagrees Show reasoning
How this is scored

A ticket archive is personal data written by the data subject. Retention, deletion, access control, subject rights under DSGVO, and what the vendor does with attachments — judged on what the product documents it executes.

0 — The vendor's own terms state that ticket content is used for purposes beyond providing the service, or that a data processing agreement is not offered.

3 — A privacy policy and a data processing agreement (DPA) offered, with agent roles that limit what an agent can do.

5 — A DPA published or signable online, agent roles and group- or queue-level visibility, and deletion of tickets or of a requester's data documented in the help centre.

8 — Automatic retention or deletion rules per queue or data category, attachment handling stated, an audit log of agent access or changes, documented support for access and erasure requests, and redaction of ticket content.

10 — Built for a data-protection audit: retention executed and evidenced per category, field-level redaction, full audit trail, subprocessor list published, and the vendor's own support access to customer instances documented and consent-gated.

Report an error

The Support Lead

A data processing addendum is referenced with Atlassian acting as processor; permission schemes, issue-level security and restricted comment and work-log visibility control what an agent sees, audit logs and multi-region data residency appear from the Standard plan, and encryption in transit and at rest is stated. The privacy policy lists machine learning and AI model training among its purposes under legitimate interests, while stating it does not apply where Atlassian acts as processor under the addendum. Beyond alert-data retention by plan we found no public information on per-queue retention or deletion rules, redaction of ticket content, or the vendor's own support access to customer instances, and Jira is documented as not supporting field-level permissions. 3 12 13 2 2

Report an error

The Agent Advocate

A data processing addendum and a privacy policy with retention, de-identification and portability commitments sit on top of deep permission machinery — project schemes, issue-level security, comment and work-log visibility — with plan-level audit logs and stated attachment encryption. I found no public information on per-queue retention rules for the ticket archive, redaction of ticket content (field-level permissions are explicitly unsupported), or a documented erasure workflow; the policy also lists machine-learning training under legitimate interests while carving out Atlassian's processor role, which I would want nailed down in the addendum before trusting it. 3 13 2 12

Report an error

The Data Protection Officer

A Data Processing Addendum is referenced with Atlassian acting as processor, and access control is genuinely layered: permission schemes, issue-level security, restricted comment and work-log visibility, plus audit logs from the Standard plan and automatic deletion of alert data after a stated per-plan retention period. The privacy policy lists machine learning and AI model training under legitimate interests, though it states that policy does not apply where Atlassian processes personal information as processor for customers. We found no public information on ticket deletion or requester erasure workflows, redaction of ticket content, or whether vendor support can open a customer ticket, and field-level permissions are explicitly not supported. 3 13 2 2

Report an error

The Shop Operator

A data processing addendum is referenced with Atlassian acting as processor, backed by a delete-or-deidentify retention principle, automatic alert-data deletion per plan, granular permission schemes with issue- and comment-level visibility, and audit logs. The captured pages state plainly that field-level permissions are not supported, and we found no public information on redaction of ticket content or a documented erasure workflow for requesters. 3 13 2 2

Report an error

The Integrator

A data processing addendum is referenced with Atlassian acting as processor, the privacy policy commits to delete or de-identify after retention with isolation of backups until deletion, and the Jira permission model — project schemes, issue-level security, restricted comment and work-log visibility — is granular, though the permissions overview itself states field-level permissions are not supported. Audit logs appear on the paid plans and attachments are named in the AES-256 at-rest statement, with a sub-processor list you can subscribe to updates about. We found no public information on redaction of ticket content, per-queue retention rules for tickets, or a documented erasure workflow for requesters. 3 12 13 2 5

Report an error

The Skeptic

A data processing addendum is referenced in the privacy policy, permission schemes with issue-level security and comment and work-log visibility give genuine role granularity, audit logs arrive on Standard, attachments are named in the AES-256 at-rest statement, and a sub-processor list is maintained with update notifications. The permissions page states plainly that field-level permissions are not supported, and we found no public information on ticket-content redaction, retention rules per queue, or consent-gated vendor support access to customer instances. 3 12 13 2

Report an error

Integrations & API

panel disagrees Show reasoning
How this is scored

The systems a helpdesk has to reach — CRM, shop, order management, identity — and whether the API is documented for building or gated behind a partner conversation.

0 — A closed tool with no API and no integrations; context is copied in by hand.

3 — A handful of named integrations or a connector service such as Zapier, or an API with basic documentation.

5 — Named integrations for common CRM, shop or collaboration tools, a documented REST API, and webhooks or triggers that call other systems.

8 — An app marketplace with maintained bidirectional integrations, customer context from other systems shown inside the ticket, SSO and SCIM provisioning, documented rate limits and a sandbox.

10 — A component rather than a destination: versioned API with a deprecation policy, event streaming both directions, an app framework for in-ticket extensions, and integrations the vendor maintains rather than lists.

Report an error

The Support Lead

Over 1,000 marketplace apps, documented REST APIs with rate limits, a sandbox, bulk customer and organization APIs, and a guided Salesforce import that maps accounts to organizations are documented, with bidirectional integrations on Premium and Enterprise. We found no public information on SCIM provisioning, a versioned API with a deprecation policy, or event streaming — and private endpoints are documented as changeable or removable without deprecation or warning. 8 14 15 1 2

Report an error

The Agent Advocate

Over a thousand marketplace apps, a documented REST API with bearer authentication and stated rate limits, a guided Salesforce CRM integration that maps accounts and contacts onto organizations and customers, bidirectional integrations on Premium and Enterprise, and a sandbox for testing rollouts — most of what the high bar asks for. I found no public information on SSO and SCIM provisioning, and one documented mail-channel endpoint is private and can change or vanish without deprecation warning. 14 15 1 2 8

Report an error

The Data Protection Officer

Over 1,000 marketplace apps, documented REST APIs with rate limits and a sandbox, a guided Salesforce integration that maps accounts and contacts into organizations and customers inside the service desk, bulk customer and organization APIs, and chat integrations for Slack, Microsoft Teams and Zoom; bidirectional integrations are gated to Premium and Enterprise. We found no public information on directory-based single sign-on and SCIM provisioning for agents, which is the piece I would want evidenced before calling the ecosystem complete. 1 14 15 2 2

Report an error

The Shop Operator

Over 1,000 marketplace apps, a documented REST API with rate limits, bulk customer and organization APIs, bidirectional integrations on higher tiers and a sandbox give me real plumbing, and the guided Salesforce import maps business accounts straight to customer organizations with detail fields like phone and region. That context arrives as imported profile data, though — we found no public information on live order data shown inside the ticket, and none on SSO or SCIM provisioning. 2 15 14

Report an error

The Integrator

The developer documentation gives real REST endpoints with Bearer auth, asynchronous bulk customer and organisation import with a task-status API, and an explicit note that the customer service APIs are rate-limited; Salesforce CRM import with account-to-organisation mapping is documented, bidirectional integrations sit on Premium and Enterprise, and a sandbox plus a 1,000+ app marketplace are on the pricing page. We found no public information on webhooks with retry, SCIM provisioning, rate-limit numbers, or an API deprecation policy — and the email-channel monitoring article leans on a private endpoint its own page warns can change or be removed without notice. Strong plumbing, but the identity and eventing story is unproven on these pages. 14 15 1 2

Report an error

The Skeptic

A 1,000+ app marketplace, documented REST APIs with Bearer authentication and stated rate limits, a sandbox copy of the environment, and a guided Salesforce mapping of business accounts to organizations and contacts to customers put CRM context inside the product. Bidirectional integrations are confined to Premium and Enterprise, and we found no public information on SSO or SCIM provisioning, so the upper end of the integration story is not documented. 14 15 1 2

Report an error

European sovereignty panel opinion

panel disagrees Show reasoning
How this is scored

Where the ticket archive lives, who the contracting entity is, which subprocessors touch it, and whether vendor support can read customer data. Independently sourced by the sovereignty pipeline; scored here as this buyer weighs it. Dimensions the evidence does not establish are unknown, not non-EU.

0 — Proven non-EU on every dimension the evidence covers: non-EU vendor and contracting entity and non-EU hosting, with no EU option stated.

3 — One European element proven — an EU hosting option, an EU contracting entity or EU representative, or a published DPA — with the rest of the chain unstated.

5 — EU hosting stated as standard or selectable and an EU contracting entity or EU representative, with a DPA offered; the subprocessor chain is unstated or partly non-EU.

8 — EU or DACH hosting with a named data-centre provider, EU contracting entity, subprocessor list published with locations, and any non-EU processing named with its legal basis.

10 — Sovereign end to end and evidenced: vendor, entity, hosting and every subprocessor in the EU, certification published, and a self-hosted or private-cloud option for buyers who need the archive on their own infrastructure.

Report an error

The Support Lead

The contracting picture is a US legal entity in San Francisco alongside an Australian-registered company, with an EU representative named but addressed care of the US office. Data residency is presented as a choice within a global cloud footprint with no EU region named, and hosting is stated only as Amazon Web Services without a location. If my archive's location gets questioned in an audit, these captured pages do not let me answer it. 3 4 16 5 2

Report an error

The Agent Advocate

What the pages prove is a non-EU chain: contracting entities in San Francisco and under Australian law, hosting on Amazon Web Services with no region named, and transfers stated as global to wherever Atlassian or its providers operate. The EU representative named in the privacy policy is the one European element I can verify; the data-residency choice is advertised but names no EU location, and we found no public information on subprocessor locations or vendor support access to customer instances. 16 3 4 2

Report an error

The Data Protection Officer

The contracting picture is American and Australian — Atlassian Corporation at a San Francisco address and Atlassian Pty Ltd registered under Australian law as service provider — with hosting on Amazon Web Services and no region named, and transfers of information globally stated. European elements do exist: an EU representative (Atlassian B.V.), a UK representative, a Data Processing Addendum, and selectable data residency within the global cloud footprint, though no EU region is named. We found no public information on subprocessor locations or on vendor support access to customer instances, so the chain cannot be assessed end to end. 16 5 4 3 2

Report an error

The Shop Operator

The contracting entities sit in the United States and Australia, transfers are stated as global "to wherever we or our third-party service providers operate", hosting is on AWS with no region named, and data residency is a choice within the global cloud footprint with no EU region stated. The one European element the pages prove is the named EU representative, Atlassian B.V. 16 3 5 4 2

Report an error

The Integrator

The contracting picture is Australian and American — Atlassian Pty Ltd as service provider, a US legal entity — hosting is on AWS with no region named, data residency is a purchasable choice rather than a stated default, and the privacy policy states information is transferred globally to wherever Atlassian or its providers operate. The European element is a compliance artifact: Atlassian B.V. is named as EU representative and a data processing addendum is referenced. That is one proven European element with the rest of the chain unstated. 3 4 16 5

Report an error

The Skeptic

The contracting picture is American and Australian — Atlassian Corporation in San Francisco and Atlassian Pty Ltd under Australian law — the privacy policy speaks of transferring information globally to wherever Atlassian and its providers operate, and the trust page names AWS as host without a region. An EU representative (Atlassian B.V.) and an EU VAT number are proven and a data processing addendum is referenced, so one European element is established with the rest of the chain, including hosting location and sub-processor locations, unstated. 16 3 5 2

Report an error

Pricing transparency

panel disagrees Show reasoning
How this is scored

Whether a support lead can compute the real annual invoice for their agent count — including the channels and features they actually need — from public pages alone.

0 — No public prices at all; every tier is a sales conversation.

3 — A public "from" price or one priced tier, per agent or flat.

5 — Per-agent prices public for the main tiers with the billing period stated and the main features per tier listed.

8 — Every tier and add-on priced publicly with per-agent maths, telephony or messenger costs and light-agent or contact limits given, billing period, minimum term and VAT treatment stated; only genuinely custom enterprise work lacks a number.

10 — Complete price computability: a calculator or table producing the annual invoice for a given agent count and channel selection, including usage-metered channels and overage.

Report an error

The Support Lead

Per-agent monthly prices are public for the Free, Standard and Premium tiers with detailed per-tier feature lists — storage, automation steps, assisted conversations, SMS and voice, uptime SLA — and the Customer Service AI agent is priced at $1 per resolution, though the captured pages give different figures for Standard ($20 and $21.50 per agent / month) and Premium ($51.42 and $55.28 per agent / month). Enterprise is contact sales, Guard subscriptions and volume add-ons carry no public numbers, and VAT treatment and minimum term are not stated. 2 2 2 2 2

Report an error

The Agent Advocate

Per-agent prices for Free, Standard and Premium are public with monthly billing stated, an unusually honest per-tier table covering storage, automation steps, alert retention, support hours and uptime, unlimited customers, and a metered "$1 per resolution" AI agent. But the captured pages give different figures for Standard ($20 per agent / month versus $21.50) and Premium ($51.42 per agent / month versus $55.28), Enterprise is contact-sales, the annual saving is only "SAVE UP TO 17%", and Guard subscriptions and volume add-ons carry no numbers — so I cannot compute the annual invoice for my agent count from these pages alone. 2 2 2 2

Report an error

The Data Protection Officer

Free, Standard and Premium carry public per-agent monthly prices with the billing period and a long list of per-tier limits — storage, automation steps, uptime SLA, support hours, agent and customer limits, SMS counts — plus a priced AI agent at $1 per resolution and annual savings of up to 17%, with Enterprise as contact-sales. The captured pages give different figures for Standard and Premium across pricing-page captures, and we found no public information on VAT treatment, minimum term, telephony costs, or the price of the Guard subscriptions that several security features require. 2 2 2 2 2

Report an error

The Shop Operator

Per-agent prices are public for the three main tiers with feature and limit detail — automation steps, storage, SMS counts, Rovo credits — and add-ons carry numbers, including the AI agent at $1 per resolution. Computability slips because the captured pages give different figures for Standard ($20 per agent / month on one capture, $21.50 per agent / month on another) and for Premium ($51.42 per agent / month versus $55.28 per agent / month), the annual saving is stated only as up to 17% without a computed annual price, and we found no public information on VAT treatment or minimum term. 2 2 2 2

Report an error

The Integrator

Per-agent prices are public for Free, Standard and Premium with the billing period and an unusually detailed per-tier matrix — automation steps, storage, emails, SMS, uptime SLA, support hours, assisted conversations and credits — and the AI agent is priced at $1 per resolution. Enterprise is contact-sales only, the annual figure is given only as "SAVE UP TO 17%", and we found no public information on VAT treatment, minimum term, or numbers for Guard and the volume-discounted add-ons. The captured pricing pages also give different figures for Standard and Premium ($21.50 versus $20, and $55.28 versus $51.42 per agent per month), so pinning one exact invoice is hard. 2 2 2 2 2

Report an error

The Skeptic

The pricing pages are unusually specific: per-agent monthly prices with each plan's automation steps, storage, uptime percentage, support hours, site counts and alert retention, agent and customer limits given, and AI metered at "$1 per resolution" with virtual-agent conversations capped at 1,000 per month on Premium. However, the captured pricing pages give different figures for the Standard and Premium per-agent prices, we found no public information on minimum term, VAT treatment, telephony costs or overage unit prices for conversations and credits, and Enterprise sits behind contact sales — so the real annual invoice is not fully computable from public pages. 2 2 2 2

Report an error

European sovereignty — proven facts

1 of 6 dimensions proven

Built only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.

Hosting location Not determined unverified
Why unverified?

No specific region (EU or US) is named and no default hosting location is stated; the choice-based residency is presented only as a higher-tier feature, and the trust page says merely 'hosted on Amazon Web Services (AWS)' without location.

— uncited Report an error
Hosting options Not determined unverified
Why unverified?

Not confirmed on the vendor’s own pages as captured.

— uncited Report an error
Open source Not determined — uncited Report an error
Data processing agreement Not determined — uncited Report an error
Transfer impact assessment Not determined — uncited Report an error

Questions about Jira Service Management

Is Jira Service Management European?

No. whats-best.ai classifies Jira Service Management as Rest of world. Its vendor, Atlassian Corporation, is incorporated in the United States, per the vendor’s page captured 8 Nov 2026.

Where does Jira Service Management store data?

Not stated on the vendor’s pages as of 16 Nov 2026.

Does Jira Service Management have a free plan?

Yes. Jira Service Management has a free plan, per the vendor’s page captured 15 Sep 2026.

What are the best alternatives to Jira Service Management?

As of 18 Nov 2026, the panel rates Zendesk (3.5/5), LiveAgent (3.5/5) and Intercom (3.5/5) highest among the other 35 Customer Service & Helpdesk products evaluated. Ratings that look equal are rounded to half stars; the order uses the unrounded rating, then the name. The highest-rated European alternative is Zammad (EU-Made, Germany). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: Jira Service Management alternatives.

Where this could be wrong

What we left out

A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.

Sources (16)

The pages every claim on this page was read from — each one checked, dated, and kept verifiable.

  1. 1 Product page www.atlassian.com Checked 16 Nov 2026 +2 earlier captures: 2 Nov 2026, 26 Oct 2026 Details →
  2. 2 Pricing www.atlassian.com Checked 16 Nov 2026 +5 earlier captures: 9 Nov 2026, 2 Nov 2026, 5 Oct 2026, 15 Sep 2026, 31 Aug 2026 Details →
  3. 3 Privacy policy www.atlassian.com Checked 16 Nov 2026 Details →
  4. 4 Security / trust page www.atlassian.com Checked 16 Nov 2026 Details →
  5. 5 Imprint www.atlassian.com Checked 16 Nov 2026 +1 earlier capture: 2 Nov 2026 Details →
  6. 6 Ticketing, queues & SLA — found from sitemap support.atlassian.com Checked 16 Nov 2026 Details →
  7. 7 Ticketing, queues & SLA — found from sitemap support.atlassian.com Checked 16 Nov 2026 Details →
  8. 8 Channels in one queue — found from sitemap support.atlassian.com Checked 16 Nov 2026 Details →
  9. 9 Channels in one queue — found from sitemap support.atlassian.com Checked 16 Nov 2026 Details →
  10. 10 Knowledge base & deflection — found from sitemap support.atlassian.com Checked 16 Nov 2026 Details →
  11. 11 Knowledge base & deflection — found from sitemap support.atlassian.com Checked 16 Nov 2026 +1 earlier capture: 19 Oct 2026 Details →
  12. 12 Customer data protection — found from sitemap www.atlassian.com Checked 16 Nov 2026 Details →
  13. 13 Customer data protection — found from sitemap support.atlassian.com Checked 16 Nov 2026 Details →
  14. 14 Integrations & API — found from sitemap support.atlassian.com Checked 16 Nov 2026 Details →
  15. 15 Integrations & API — found from sitemap developer.atlassian.com Checked 16 Nov 2026 Details →
  16. 16 Structured-data backfill: markup only, no text or screenshot www.atlassian.com Checked 8 Nov 2026 Details →