The Invoice ■ Episode 13
“Streamline your workflow! Track everything! Complete visibility!”
Splendid. Let us examine what you are actually paying for.
You wanted to track bugs. A sensible ambition. What arrived was a bureaucracy engine with custom fields nobody remembers creating and workflows nobody dares to simplify. Jira began life in 2002 as a bug tracker built by two Australians who named it after Godzilla. Twenty-four years later it has become the software that makes other software take longer to build.
The Complexity Invoice
Atlassian conducted their own user research. The finding: 68 per cent of new Jira users felt overwhelmed within their first month. Not by the work. By the tool designed to organise it.
Their research recommends five to seven workflow statuses. The average enterprise instance has dozens. Custom fields accumulate like geological strata: each layer deposited by a manager who needed one more dropdown, none removed because nobody remembers why it exists and nobody dares to find out.
Then there is JQL, Jira's query language. It resembles SQL closely enough to inspire confidence, then diverges in ways that consume your afternoon. No joins. No subqueries. A proprietary syntax useful in precisely one product on Earth. It is the linguistic equivalent of a cul-de-sac dressed as a motorway.
The Design Invoice
Three views for the same data: board, list, timeline. Each behaves differently. Settings buried behind nested menus. Modal dialogues for actions that should take one click. Navigation that changes depending on which project you are in.
This is not a product designed by people who use it. It is a product designed by people who demo it. The interface optimises for the sales call, not the Tuesday morning. Every feature that impressed a procurement committee is a feature that slows down the person who actually has to click it eight hours a day.
The Performance Invoice
Jira Cloud takes one to four seconds to load a single issue. Worst cases reported on the Atlassian Community forums: 40 to 60 seconds. The batch.js file alone exceeds 7 MB. Each marketplace plugin adds weight. Each custom field adds a query. Each workflow transition adds a round trip.
A tool designed to make work visible should not require a tea break to become visible itself.
The Migration Invoice
In February 2024, Atlassian killed Jira Server. No more patches. No more security updates. Cloud or Data Center, nothing else. The Data Center minimum: 500 users. Team of 50? You pay for 500.
In February 2025, Data Center prices went up 30 per cent. In March 2026, Atlassian cut 1,600 jobs to “self-fund AI.” Revenue: $5.2 billion. Rather generous of the remaining staff to fund the innovation with their former colleagues' desks.
The Outage Invoice
April 2022. A maintenance script deleted 883 customer sites. 775 customers. Up to 800,000 end users affected. Products down: Jira, Confluence, Opsgenie, Statuspage. The irony of Statuspage being unable to report its own status was presumably not lost on the incident team.
Restoration took fourteen days. Two weeks without the tool that was supposed to track all the work. One rather hopes someone had a spreadsheet.
The Alternative
Linear was built by engineers who left Uber because Jira was unbearable. $1.25 billion valuation. 100 employees. $35,000 marketing spend. Total. Not annual. It sells itself because it loads in under a second. The product is the marketing.
GitHub Issues: already where your code lives. No context switch. No separate licence. No JQL. The query language is the same search bar you already know.
JetBrains built Space: fast, thoughtful, integrated with the IDE. Launched 2020, killed 2024. The better product lost. The lock-in is not quality. It is inertia. Organisations do not stay with Jira because it is good. They stay because migration is expensive and nobody wants to be the person who proposed it.
The Pattern
Jira was a bug tracker. Then a project management platform. Then a workflow engine. Then a compliance surface. Then a reporting layer for people who do not write code but need to feel informed about people who do.
At each step, it gained features. At no step did it lose any. This is the pattern: a tool begins by solving a problem, then solves adjacent problems, then solves problems that only exist because it solved the previous ones. The custom fields exist because the workflows are complex. The workflows are complex because the permissions require them. The permissions exist because the reporting layer demands them. And the reporting layer exists because someone three levels above the codebase needs a pie chart for a meeting that could have been an email.
The Verdict
The Jira invoice is not a single line item. It is the compound of complexity that overwhelms 68 per cent of new users, a query language useful in one product, load times that require patience your developers do not have, a forced migration that eliminated self-hosting, price increases that fund AI development with your money and their former colleagues' livelihoods, and a fourteen-day outage that deleted 883 customer sites while the status page was itself down.
You wanted to track work. You got a tool that became the work.
Jira was a bug tracker that became a project manager that became a workflow engine that became a compliance surface that became a reporting layer for people who do not write code but need to feel informed about people who do. At each step it gained features. At no step did it lose any.
Linear proves the alternative: 100 people, no enterprise sales team, sub-second load times, and a valuation that says the market agrees. JetBrains Space proved the tragedy: a better product that died because inertia is a stronger force than quality.
Rather an expensive workflow.