The Journey of Atlassian Jira: Revolutionizing Project Management
From a 2002 bug tracker named after Godzilla to the project management platform millions of teams run on today — the real history of Atlassian Jira, and what good PM discipline should look like in any software partner.
Jira started in 2002 as a simple bug tracker for Atlassian's own two founders and grew into the project management platform millions of software teams now run their work on. Its journey — from issue tracker to agile powerhouse to full work-management suite — says as much about how software teams evolved as it does about the tool itself.
Where it started: two founders and a bug tracker
Atlassian was founded in 2002 by Mike Cannon-Brookes and Scott Farquhar, who met at the University of New South Wales. Before Jira existed, they were using Bugzilla to track their own work and kept hitting its limits. So they built their own tool — Jira 1.0 — to track bugs and tasks for software developers. The name itself is an internal joke: "Jira" comes from "Gojira," the Japanese name for Godzilla, a nickname that stuck during development.
From bug tracker to agile powerhouse
- 2002–2010: Jira established itself as a leading issue-tracking tool and introduced a plugin ecosystem through the Atlassian Marketplace — letting teams extend it far beyond its original scope.
- 2009: Atlassian acquired GreenHopper, which brought release planning, burndown charts, and the agile board features that are now core to Jira Software.
- 2011: The first cloud-based version of Jira launched, opening the tool up to teams who didn't want to self-host.
- 2012: Scrum boards (originally built as "RapidBoards") became a standard feature.
- 2013: Jira Service Desk — which started as an internal hackathon project — joined the product suite.
- 2015: Jira split into distinct application types, separating general work tracking from software-specific workflows.
- 2020–present: The suite expanded further into Jira Software, Jira Service Management, and Jira Work Management, with AI-assisted features arriving in recent years to help teams triage, summarize, and plan faster.
What's notable across two decades is the direction of travel: every major addition made Jira less of a bug tracker and more of a general operating system for how teams plan, build, and ship — mirroring the industry's own shift from ad-hoc development toward disciplined agile process.
Why this history matters beyond Jira itself
Jira's evolution is really the story of software teams demanding more structure: visible backlogs, sprint planning, burndown tracking, and a shared source of truth for what's actually getting built. That discipline is valuable regardless of which specific tool enforces it. When you're evaluating a development partner, the question isn't "do they use Jira" — it's whether they run the same underlying discipline Jira was built to support: a visible backlog, a frozen scope per iteration, and a clear view of what shipped this week versus what's still in progress.
It's exactly what we cover in our checklist for choosing a software development company — ask to see the board, not just the pitch. A team that can't show you a real, current backlog for a real, current client is asking you to trust the process on faith.
How we apply that discipline
We run every project the way Jira's own history argues for: a frozen scope per milestone, a visible backlog, and a working demo every single week — whether or not the client's team uses Jira, Linear, or a spreadsheet to track it with us. Tooling is negotiable; the discipline behind it isn't. See how that plays out project to project in our custom software development work.
Evaluating a development partner and want to see real process, not just promises?
Ask us for a live look at how we run an active project — backlog, weekly demos, and all.
Talk to our team →Frequently asked questions
When was Jira launched and who created it?
Jira 1.0 launched in 2002, built by Atlassian founders Mike Cannon-Brookes and Scott Farquhar after they hit the limits of Bugzilla while tracking their own work. It started as a bug and issue tracker for software developers before evolving into a full project management platform.
Why is it called 'Jira'?
The name comes from "Gojira," the Japanese name for Godzilla — an internal nickname from Jira's early development that stuck and became the product name.
How did Jira become an agile project management tool?
The turning point was Atlassian's 2009 acquisition of GreenHopper, which added release planning, burndown charts, and agile board features. Scrum boards became standard by 2012, and by 2015 Jira had split into distinct application types, expanding well beyond its original bug-tracking scope.
What should I look for in a software partner's project management process?
Regardless of which tool they use, look for a visible backlog you can see, scope that's frozen per iteration rather than constantly shifting, and a working demo delivered on a regular cadence — weekly is a good standard. A team that can show you their actual current process, not just describe it, is the one worth trusting.