For the executive who has to defend the number.
Atlassian Align, formerly Jira Align, sits above Jira and connects delivery work to portfolio and program commitments across many teams, with the planning constructs that scaled frameworks expect. Our work is deciding whether you need it, and building the hierarchy and data model that make a portfolio roll-up traceable.
Jira Align connects delivery work to portfolio commitments at scale. We decide first whether you need it, then build the hierarchy underneath it so the roll-up is a read rather than a reconstruction.
What it is
Atlassian Align, formerly Jira Align, sits above Jira and connects delivery work to portfolio and program commitments across many teams, with the planning constructs that scaled frameworks expect.
It is for organizations large enough that the roll-up cannot be assembled by hand, and disciplined enough that the data underneath it is consistent. Where either is untrue, it makes the problem legible and expensive rather than solved.
What it does
Delivery connected to commitment
Work items roll up to the programs and portfolio items they belong to, so a status is derived rather than written.
Planning constructs at scale
The structures scaled frameworks assume, for organizations that genuinely run at that size.
A trace back to the work
Any figure can be followed down to the items that produced it, which is the only version that survives a question.
Where it fits
L3, governance and change. Portfolio reporting is a governance instrument before it is a reporting one: it decides what gets funded and what gets stopped. It also depends entirely on the layer below, because a roll-up over inconsistent workflows and fields is a guess with a chart on it.
What we do with it
Deciding whether you need it
Jira Align, the Strategy Collection, and native hierarchy solve overlapping problems at different scales. Choosing wrong is expensive in both directions.
Hierarchy and roll-up design
Focus areas, hierarchy, and the standardization that has to happen underneath before any of it reports honestly.
Standardizing delivery data
Workflows, fields, and prioritization made consistent across teams, which is the unglamorous prerequisite.
Keeping it current
Portfolio structures drift as reorganizations happen. Maintaining them is an operation.
Where it earns its place
An organization moving to quarterly planning
Annual project cycles hide inconsistency. Quarterly planning exposes it within one cycle.
A portfolio assembled by hand each quarter
If a status still requires a person to compile it, the hierarchy is unfinished regardless of which tool holds it.
A leadership team that cannot trace a figure
The question is never the dashboard. It is whether the number can be followed back to work items.
Proof
Strategy Solutions Finalist, 2026
Atlassian Partner Awards, 2026
Questions we get
Do we need Jira Align or the Strategy Collection?
Our delivery data is inconsistent. Start there or here?
How much change does this ask of delivery teams?
Licensing
Jira Align is a significant line item and is often bought before the question of whether the estate needs it has been answered, so the review is worth doing before the renewal. That reconciliation sits with the rest of the estate in licensing and renewals.