Jira

Jira is a project and issue tracking platform used primarily by software development teams, IT operations, and business project managers. At its core, it organises work into issues that flow through customisable workflows, displayed on Scrum boards, Kanban boards, or traditional list views.

Key capabilities include sprint planning, backlog management, workflow automation, time tracking, reporting and dashboards, roadmapping, and JQL (Jira Query Language) for advanced searching and filtering. The platform integrates tightly with Atlassian's other products (Confluence for documentation, Bitbucket for code hosting) and has a marketplace with thousands of third-party apps.

Jira Work Management (the business-focused variant) was merged back into the main Jira product in 2024-2025, so there are now two main products: Jira (for all project types) and Jira Service Management (for IT help desks and ITSM). The target market spans from small development teams to large enterprises, though Jira is particularly strong with engineering and IT organisations.

Jira Cloud has four tiers. The free plan supports up to 10 users with basic Scrum and Kanban boards, which is genuinely useful for small teams getting started. Standard sits around US$8 per user per month and adds audit logs, project roles, and 250GB storage.

Premium runs roughly US$15 per user per month and is where serious teams should start. It unlocks cross-team planning, dependency management, unlimited storage, a 99.9% uptime SLA, and a sandbox environment for testing. Enterprise is custom-priced and adds advanced admin controls, unlimited automation, and analytics.

Two things to watch on pricing. First, Atlassian implements annual price increases of 5 to 20%, typically each October. Second, marketplace plugins can significantly increase your total cost. Some organisations report spending $5,000 to $75,000 annually on plugins alone, which can dwarf the base licence cost. Their self-hosted Data Center product is being sunset starting March 2026, so new customers should plan for cloud.

Vendor lock-in with Jira is moderate to high, and it increases the longer you use the platform. Raw issue data (titles, descriptions, statuses, comments) can be extracted via CSV exports or the API without much trouble. The lock-in comes from everything else: custom workflows, automation rules, board configurations, JQL saved filters, and marketplace plugin data are all Jira-specific and don't port to any other platform.

The deeper concern is organisational. Teams build their entire development process around Jira's concepts (epics, stories, sprints, boards), and that muscle memory doesn't transfer. Organisations that have spent years configuring Jira to match their workflows often find that migrating to an alternative means rethinking their entire project management approach, not just moving data.

With Data Center being sunset, self-hosted deployments (which gave you full control over your data and backups) are being phased out. Cloud is increasingly the only option, which means you're relying on Atlassian's export tools and backup capabilities rather than your own infrastructure.

Atlassian was founded in 2002 by Mike Cannon-Brookes and Scott Farquhar, two University of New South Wales graduates, in Sydney, Australia. Jira launched as the company's first product and remains its flagship. The company is publicly traded on NASDAQ (ticker: TEAM) with a market cap of approximately US$18 billion.

Atlassian's trajectory is strongly upward. Revenue hit US$5.2 billion in FY2025, up roughly 20% year-on-year, and Q2 FY2026 saw their first-ever billion-dollar cloud revenue quarter. They employ around 13,800 people and serve over 350,000 customers globally. Co-founder Scott Farquhar stepped down as co-CEO in August 2024, leaving Mike Cannon-Brookes as sole CEO. The transition was orderly and framed as personal.

Atlassian has been on an aggressive acquisition spree, including Loom (video messaging, US$975 million), DX (developer productivity, US$1 billion), and several AI-focused companies. The company is investing heavily in AI capabilities across its product suite. There have been targeted layoffs in customer support roles, with those functions being replaced by AI, but overall headcount has grown 13% year-on-year. This is a stable, growing company with clear strategic direction.

Jira has a comprehensive REST API available in two versions. Version 2 uses plain text for content fields, while version 3 uses Atlassian Document Format (ADF) for rich text. Both are currently available, though Atlassian has signalled the eventual retirement of v2.

As of March 2026, Atlassian moved to a points-based rate limiting system. For most integration scenarios, the default allocation of 65,000 points per hour is adequate, since a typical issue read costs just one point. Higher tiers with more generous limits are available on request for Premium and Enterprise plans. If you're syncing small to moderate volumes of data, rate limits won't be an issue. High-volume batch operations (think thousands of issues) require more careful planning.

Authentication uses OAuth 2.0 for production integrations or simpler API tokens for internal scripts. OAuth setup requires registering at the Atlassian developer portal and managing token refresh logic, which adds initial complexity but is standard practice. The API documentation is detailed and well-maintained, with clear examples and a solid reference. The main frustration is that Atlassian doesn't provide official SDKs, so you're working with community-maintained libraries or writing HTTP client code directly.

Webhooks are supported with a limit of 100 per app per tenant. For apps built on Atlassian's Forge platform, webhooks are replaced by event subscriptions defined in a manifest file. Webhook delivery is generally reliable, with bearer token authentication available for OAuth 2.0 apps.

Getting basic data out of Jira is straightforward. You can export issues to CSV or Excel, and the API provides full programmatic access to all issue data. Full site backups are available including attachments, workflows, and configuration, though backups with attachments can only be run once every 48 hours.

The real challenge is portability of everything beyond raw issue data. Custom fields, workflow configurations, automation rules, board setups, and plugin data are all deeply Jira-specific and don't transfer cleanly to other platforms. Native CSV exports are capped at 1,000 issues per operation and don't include comments or attachments, so any serious migration requires API-based extraction.

Organisations with heavy customisation report migration projects taking months. There's no built-in automated backup for Cloud (Atlassian lists it as under consideration), so most production teams rely on third-party marketplace backup tools. With the Data Center self-hosted option being sunset, the ability to run your own backup infrastructure is disappearing.

Documentation quality is generally good. The Atlassian developer portal at developer.atlassian.com is comprehensive, with method references, code examples, and guides for both API versions. The weakness is navigation. Jumping between Cloud, Data Center, Forge, and Connect documentation can be confusing, and the v2/v3 split adds to the mental overhead.

For testing, the free Jira Cloud plan (up to 10 users) provides a persistent environment with full API access, which is a genuine positive. Premium and Enterprise plans include sandbox environments that can clone your production setup. Atlassian Marketplace developers also get a free developer instance.

The biggest gap is official SDKs. Atlassian doesn't maintain client libraries for any language, which is unusual for a platform this size. The best community options are the jira Python library (pycontribs/jira on PyPI) and jira.js for Node.js/TypeScript. Both are production-quality but carry the usual risks of community maintenance. Atlassian is also pushing developers from their Connect app framework to Forge (a serverless, Atlassian-hosted platform), which means less infrastructure management but also less control.