Jira

Definition: Atlassian’s issue and project tracking tool, commonly regarded as the de facto standard for agile software development teams, built around configurable workflows, issue types, and permission schemes per project. Launched in 2002 as a straightforward bug tracker, Jira has since grown into a family of connected products — Jira Software, Jira Service Management, Jira Work Management — sharing one underlying issue-tracking core. Atlassian, its parent company, was founded in Sydney, Australia in 2002 by Mike Cannon-Brookes and Scott Farquhar, reportedly bootstrapped on a credit card rather than early venture funding.

Core Services & Concepts

REST API — REST API, plus JQL (Jira Query Language) for building complex saved filters and dashboards across issues, closer to a SQL-like query language than a typical filter UI
Git integration — CI/CD, links commits, branches, and pull requests directly to issues via smart commits or the Bitbucket/GitHub integration, and can surface build/deploy status directly on the issue
Agile boards — Scrum and Kanban boards built around sprints, backlogs, story points, and burndown/velocity charts, the core planning surface most engineering teams interact with daily
Workflow schemes — custom state machines per issue type and project (e.g. To Do → In Review → QA → Done) with configurable transition rules, validators, and required fields
Webhooks — Webhook, notify external systems (Slack, CI pipelines, custom tooling) when issues are created, transitioned, or commented on
Jira Service Management — a separate ITSM-flavored product built on the same underlying core, used for IT and ops ticketing with SLAs, approvals, and a customer-facing portal

How Pricing Works

Per-user, tiered pricing: Free (up to 10 users), Standard, Premium, and Enterprise, with each tier unlocking more automation, storage, and admin controls
Premium adds unlimited storage, advanced roadmaps, and 24/7 support; Enterprise adds centralized admin across multiple Atlassian products and unlimited instances
Costs scale quickly once teams add paid apps from the Atlassian Marketplace (time tracking, advanced reporting, test management), which are billed separately per user
Data Center (self-hosted) pricing exists for large regulated organizations that can’t use Atlassian’s cloud, though Atlassian has been pushing customers toward cloud-only over time
No transaction or usage-based fees — it’s pure seat-based SaaS pricing, unlike payment platforms with per-transaction costs

Pros

Deep customization for agile workflows: custom fields, workflow states, and permission schemes per project or team
Tight integration with the rest of Atlassian’s suite (Confluence for docs, Bitbucket/Compass for code and services)
Industry standard, so most engineers and engineering managers already know it, easing hiring and onboarding
Strong reporting: velocity, cumulative flow, and burndown charts come built in without extra tooling
Huge third-party app ecosystem via the Atlassian Marketplace covers nearly any workflow gap out of the box

Cons

Can become slow and bloated with heavy customization; orgs with years of accumulated workflow schemes report sluggish page loads
Notorious for over-complicating simple workflows, small teams often end up managing more Jira configuration than actual work
Admin permissions and workflow changes can require dedicated Jira administrators at larger organizations
Marketplace app sprawl adds real per-seat cost on top of the base subscription, easy to lose track of
Often cited as the tool engineers complain about most, despite (or because of) being the one they use daily

Comparison: Jira vs Linear vs Asana vs Notion

	Jira	Linear	Asana	Notion
Primary strength	Deep configurability and audit-grade reporting for agile software engineering	Speed and opinionated simplicity built specifically for software teams	Cross-functional flexibility spanning engineering, marketing, and ops in one workspace	All-in-one flexibility combining docs, wiki, and lightweight database-driven project tracking
Typical pricing model	Per-user tiered (Free/Standard/Premium/Enterprise), rises fast with seats plus Marketplace apps	Per-user flat tiers (Free/Basic/Business/Enterprise), minimal configuration overhead	Per-user tiered (Free/Starter/Advanced/Enterprise), advanced reporting gated behind higher tiers	Per-user tiered (Free/Plus/Business/Enterprise) plus a separate paid Notion AI add-on seat
Best fit	Large engineering orgs needing formal Scrum/Kanban process, compliance, and cross-team reporting	Fast-moving startups and product-led engineering teams that find Jira too heavy	Cross-functional orgs wanting one tool across many departments rather than a developer-only tracker	Small teams and individuals wanting docs, notes, and light project tracking in one editable source of truth
API/product style	REST + JQL, mature and deeply extensible but heavier to configure	GraphQL, local-first sync for near-instant UI	REST, resource-based endpoints for tasks/projects/custom fields	REST-like API over pages/blocks/databases, not a real relational database

Best For

Software engineering teams running formal agile processes (Scrum/Kanban) that need audit trails, reporting, and cross-team visibility
Large organizations standardizing on Atlassian’s broader suite (Confluence, Bitbucket) for a single connected toolchain

Real Examples

Used by the majority of enterprise software engineering teams; commonly paired with Confluence for specs and Bitbucket or GitHub for source control
Spotify has publicly discussed adapting Jira alongside its own “Spotify model” of agile squads and tribes
Widely used by IT and ops departments via Jira Service Management for internal ticketing, separate from any engineering use

Use Cases

Sprint planning
Bug tracking
Engineering workflow management
Cross-team IT service requests via Jira Service Management
Roadmapping and release tracking across multiple engineering teams

Integration Notes & Common Pitfalls

JQL filters silently break when a custom field is renamed or a project is archived, worth auditing saved filters periodically rather than assuming they still work
Webhook payloads differ meaningfully between Jira Cloud and Jira Data Center/Server, an integration built against one won’t necessarily work unmodified against the other (see Webhook)
Workflow scheme changes can lock existing issues in an unreachable status if transitions aren’t mapped carefully during a migration, plan the migration path before editing a live scheme
Rate limits on the Cloud REST API are enforced per-app and can throttle a heavy integration unexpectedly, batch requests and use webhooks instead of polling where possible (see Rate Limiting)
Custom field IDs (customfield_10032-style) differ per Jira instance, hardcoding them from one site’s API response into an integration silently breaks when pointed at a different Jira instance

Code Example

// Creating an issue via the Jira Cloud REST API
const response = await fetch('https://your-domain.atlassian.net/rest/api/3/issue', {
  method: 'POST',
  headers: {
    'Content-Type': 'application/json',
    Authorization: `Basic ${Buffer.from(`${email}:${apiToken}`).toString('base64')}`,
  },
  body: JSON.stringify({
    fields: {
      project: { key: 'ENG' },
      summary: 'Fix login redirect bug',
      issuetype: { name: 'Bug' },
    },
  }),
});
// The response includes the new issue's id and key (e.g. ENG-123).

FAQ

Why does Jira feel slow at large organizations? Years of accumulated custom fields, workflow schemes, and Marketplace apps add real overhead to every page load and search query, especially on older Data Center deployments; Atlassian’s cloud platform has invested heavily in performance but heavily customized instances still feel it most.

What’s the difference between Jira Software and Jira Service Management? Jira Software is the engineering issue tracker (sprints, backlogs, story points); Jira Service Management is a separate ITSM product built on the same core for IT/ops ticketing with SLAs and a customer portal, they’re often run as two connected but distinct instances.

Can small teams use Jira without the complexity overhead? Yes with discipline, sticking to a single simple workflow scheme and resisting the urge to add custom fields early keeps a small team’s Jira instance close to Linear-level simplicity, though most small teams find Linear or Asana faster to start with.

Is Jira only for software teams? No, Jira Work Management repackages the same underlying platform for non-technical teams (HR, legal, marketing) who want structured workflows without the software-specific sprint/backlog concepts, though Asana or Notion tend to feel more native for that audience.

What happened to Jira Server? Atlassian ended sales and eventually support for self-hosted Jira Server, pushing customers toward Jira Cloud or, for organizations with strict data-residency needs, Data Center, a migration many large enterprises are still working through.

History

Jira launched in 2002 as Atlassian’s first product, originally a straightforward bug-tracking tool before expanding into full project management
Atlassian was founded in 2002 in Sydney, Australia by Mike Cannon-Brookes and Scott Farquhar, reportedly bootstrapped on a credit card rather than early venture funding
Atlassian IPO’d on NASDAQ in 2015, one of the rare enterprise software IPOs from a company that never had a traditional sales force
Expanded the Jira family with Jira Service Desk (2013, later renamed Jira Service Management) and acquired Trello (2017) to cover lighter-weight, non-technical project tracking
Introduced Jira Work Management to extend the platform beyond engineering into general business team use, a direct response to competitive pressure from Asana and Notion

Referenced by

Dig deeper

Spot an error in this note?