Jira Align is Atlassian’s enterprise-level agile planning product — a separate app, sold as part of the Strategy Collection, that sits above ordinary Jira and coordinates the work of many teams into program, portfolio, and enterprise-level plans. It is not a Jira plan or feature you unlock by upgrading; it’s a distinct purchase built for organizations running dozens of Jira teams at once, not a single team’s board. This page pulls together what Atlassian’s own docs and named third parties say it actually is and does — Crosstown Tech has never run Jira Align and isn’t pretending otherwise.

What is Jira Align, in one sentence?

Per an Atlassian Community explainer that’s drawn 12,268 views, Jira Align is “an enterprise-level agile planning software that enables large organizations to connect their strategic goals with day-to-day development work.” Atlassian’s own product page frames the same idea as a pitch: Jira Align exists to “connect enterprise strategy to team-level delivery” by helping organizations “plan and deliver across portfolios, programs, and value streams.” Either description points at the same gap it’s built to close — the space between a company’s stated strategy and the hundreds of individual Jira tickets that are supposed to deliver it.

Is it “Jira Align” or “Atlassian Align”?

Worth resolving before you search or cite anything else on this page, because the answer is genuinely split right now — verified live today. Atlassian’s licensing docs, its Advanced Roadmaps vs. Jira Align comparison page, and the Jira Align help center at help.jiraalign.com all consistently use “Jira Align.” But the marketing page at atlassian.com/software/jira-align currently carries the HTML <title>Atlassian Align | Enterprise Portfolio Execution” — and, checked live today, that page’s own on-page heading now also reads “Atlassian Align,” not just the title tag. That’s a step further than what a late-August 2026 check of this same page found, when the title had drifted but the navigation and body copy still said “Jira Align” throughout.

Nothing else in Atlassian’s docs has followed the marketing page’s lead yet. For now, treat “Jira Align” as the name to search, buy, and document under — it’s what the product docs, licensing terms, and help center all still call it. “Atlassian Align” looks like a rebrand in progress on one page, not a completed one across the product. (This product has been renamed before: it started as AgileCraft, became Jira Align after Atlassian’s 2019 acquisition, and was folded into the Strategy Collection bundle in 2024 — so don’t be surprised if “Atlassian Align” eventually becomes official everywhere.)

What Jira Align is used for

Atlassian’s own help documentation centers Jira Align on managing Program Increments (PIs) — the multi-sprint planning cycles scaled-agile frameworks like SAFe run on. Per help.jiraalign.com, the product’s “program room” is the tool teams use to “manage PI planning” as a single command center, and a separate article covers the “program increment roadmap” — a scrolling timeline view of PIs and release vehicles that product owners, Release Train Engineers, and Scrum Masters use to forecast and report upward to stakeholders.

Beyond PI planning specifically, Atlassian’s product page lists the broader capability set:

  • Portfolio and program roadmapping across multiple teams and initiatives
  • Cross-team dependency and risk tracking — surfacing where one team’s delay blocks another’s plan
  • Capacity mapping and investment prioritization at the program and portfolio level
  • Framework support for SAFe, Scrum@Scale, Spotify, Disciplined Agile, LeSS, and custom/hybrid models
  • Integration with Jira and Azure DevOps, pulling team-level work up into the higher-altitude views above

The common thread: Jira Align doesn’t replace the day-to-day work happening in Jira tickets — it aggregates and re-presents that work at a level no single Jira project was built to show.

Who Jira Align is actually built for

Not a single team, and not most mid-size companies. Atlassian’s own comparison page draws the line explicitly against Advanced Roadmaps (the roadmapping feature built into Jira Software Premium/Enterprise): Advanced Roadmaps “works best for collections of up to 20 agile teams working together (about 50-150 people at a time),” while Jira Align is built for “hundreds to thousands of users at multiple levels within an organization.” A separate, heavily-viewed Atlassian Community thread (11,686 views) puts a rougher headcount on where that shift tends to happen, with one reply citing organizations of “500+ developers” as the typical adopter — using Jira Align as a coordination layer sitting above dozens of individual Jira instances, where the actual sprint-level work still happens.

If that’s not your organization’s shape yet, it’s very likely Advanced Roadmaps you want, not Jira Align — it’s included in Jira Software Premium/Enterprise rather than being a separate five-to-six-figure purchase. The full side-by-side, pulled from Atlassian’s own comparison page, is on Jira Align vs Jira.

Is Jira Align part of Jira, or a separate product?

A separate product entirely — this is the single most common point of confusion this page exists to clear up, and Jira Align vs Jira covers it in full, with two named Atlassian Community Champions confirming it from the buyer’s side (“truly separate products,” “can be used together, or standalone”). Short version: paying for a Jira Software plan — Free, Standard, Premium, or Enterprise — doesn’t include Jira Align. Per Atlassian’s own Strategy Collection licensing page, Jira Align ships bundled with two other apps, Focus and Talent, and “the Strategy Collection is sold as a single offering, including 3 apps. The apps cannot be purchased separately.” Getting Jira Align means a separate purchase, a separate sales conversation, and — per Jira Align pricing: what it actually costs — a price Atlassian doesn’t publish, with named third-party breakdowns putting real-world spend in the tens of thousands of dollars a year before implementation.

If you’re not sure you need Jira Align at all

Jira Align is priced and built for a specific buyer: an enterprise running 50-100+ teams that needs one shared view spanning strategy, programs, and delivery. If your actual problem is smaller — you just need a readable, accurate Jira status that reaches people who don’t have a Jira seat, not an enterprise portfolio-planning platform — that’s a much narrower and cheaper problem. Jira reports for stakeholders who don’t use Jira and a Jira status report without a login cover that need directly, and are worth checking before a Jira Align conversation with sales even starts. And if you’re already sold on Jira Align but unsure how its hierarchy actually works, Jira Align hierarchy levels: what they mean covers both its organizational and work-item structures.