Avaratak Blog

The Case of the 49%: The Jira Service Management Stat Everyone Is Googling

August 13, 2026
Jira Service Management
Atlassian
AI
A black magnifying glass resting on a printed document, illustrating the hunt for the source of a Jira Service Management statistic. Photo from Unsplash.

A curious pattern keeps surfacing in our search analytics: people Googling, with quotation marks around each piece, “49%” “jira service management” “business teams” atlassian. Nobody types quotation marks into a search bar by accident. Quote marks are a subpoena. These searchers aren’t browsing for something to read — they’re hunting a citation.

So I went and found the thing they’re looking for. It took a shareholder letter, an SEC filing, and two text extractors that refused to agree with each other. Here’s what the number is, where it lives, why it’s so strangely hard to verify, and what a business team should actually do with it.

A quoted search is a footnote with a missing source

Somewhere, somebody encountered a claim — roughly, that 49% of Jira Service Management users sit on business teams. Maybe in a conference slide, maybe in a LinkedIn post, and most likely in 2026: in an AI answer that stated it with total confidence and zero links. Now they need the source, because the claim is headed into a business case, an article, or a procurement document, and “an AI told me” doesn’t survive contact with a CFO.

This is verification searching, and it’s quietly becoming its own genre of traffic. The machines summarize; the humans audit. The quote marks are the audit.

Where the number actually lives

Every quarter, Atlassian publishes a shareholder letter, and near the back sits a page titled “Atlassian at-a-glance.” Last week we decoded Atlassian’s Q4 FY26 shareholder letter as a product roadmap; this time, the interesting part is the chart nobody reads closely.

That page carries user-diversity charts for Jira, Confluence, and Jira Service Management, each splitting users between technical teams and business teams. The three splits, per Atlassian: 52/48, 51/49, and 50/50 — drawn, the footnote says, from a sample of five million-plus Jira and Confluence Cloud users and one million-plus Jira Service Management users as of March 31, 2024.

So yes: the 49% is real, it sits in a business-teams column on that page, and the people searching for it are in exactly the right neighborhood. And whichever chart you pin it to, the takeaway refuses to budge — across Atlassian’s three flagship products, the user base splits roughly half technical, half business. That is a remarkable fact about a company the market still files under “developer tools.”

Why nobody can close the loop

Here’s the catch: the diversity data lives in a designed chart, not a sentence. Feed that page to a text extractor — which is precisely what AI search engines do — and the three products’ numbers come out shuffled. While researching this post I ran the same SEC filing through extraction twice, and the percentage pairs kept different company each time. The layout is perfectly clear to human eyes and perfectly ambiguous to a parser.

Which produces the loop our searchers are stuck in: an AI assistant reads the scrambled text and tells someone that 49% of Jira Service Management users are business teams. The reader asks for a source. The assistant can’t produce a quotable sentence, because the primary source never wrote one — it drew a picture. The reader heads to Google wearing quote marks, and the search can’t fully resolve.

To be fair, this isn’t an Atlassian foible. It’s an industry-wide artifact of how machines read multi-column layouts, and it afflicts every vendor’s beautifully designed stats page equally. But it is a preview of how discovery works now: if your number doesn’t live in a sentence, a language model will improvise one for you — and your readers will spend their afternoon auditing it.

The number Atlassian says out loud

If you’re building a Jira Service Management business case, skip the donut forensics and use prose. In its Q3 FY26 letter (April 2026), Atlassian wrote it in an actual sentence: over 60% of Service Collection instances are for non-IT functions. HR, legal, finance, and marketing teams that used to run requests through inboxes and spreadsheets are now running structured, measurable workflows. The same letter counts 65,000-plus customers — including over half of the Fortune 500 — and puts the Service Collection past $1 billion in annual recurring revenue, growing more than 30% year over year. Forrester named Atlassian a Leader in its Q4 2025 Enterprise Service Management Wave, and Gartner followed suit in the 2026 Magic Quadrant for ITSM Platforms.

None of this is a plot twist. Jira Service Desk was born in 2013 after Atlassian noticed nearly 40% of its customers had already bent Jira into a request tracker. Business teams have been voting with their workflows for over a decade; the at-a-glance chart is just the running tally. We see the same election locally — watching HR teams retire their 47-column spreadsheets and legal departments discover they were service desks all along.

The Avaratak Take

Cite sentences, not charts. For the slide your CFO will read, use the prose stat: over 60% of Service Collection instances are non-IT, per Atlassian’s Q3 FY26 shareholder letter. It’s precise, quotable, and dated. The 49% is directionally fine, but as a citation it’s footnote-fragile. And date-stamp every vendor number you borrow — the user-diversity sample is from March 2024, vendor-reported, and directional. Good for a slide; thin for a courtroom.

If you’re a business team eyeing JSM, you are not the experiment. Roughly half the user base and the clear majority of new instances look like you. Start with one intake flow, one queue, and one quarter to prove it — the pattern that keeps working is small, visible, and boringly repeatable.

Publish your own numbers in sentences. The lesson generalizes well beyond Atlassian: language models now paraphrase charts into prose whether or not you wrote the prose. Write the sentence yourself, or the machines will draft it for you — with adventurous attribution.

And if you’d like this conversation with your org chart in it, that’s the day job. Avaratak’s senior-only consultants — Senior Atlassian consultants with 5+ years experience, no bench of juniors — help business teams stand up service management that survives contact with reality. Grab a slot at our discovery calendar or browse the rest of our thinking at avaratak.com.

Related reading

Share this post:
Copyright © 2026 Avaratak Consulting LLC - All Rights Reserved.