Foundation vs. Jira Plans (Advanced Roadmaps): Specialist or Native Tool?

Jira Plans is Atlassian's native roadmap tool, bundled with Jira Premium. Foundation is a Marketplace app that goes deeper on hierarchy, Sync Agents, and Gantt — and works on any Jira Cloud tier, including Free. Here's when to use which, what they cost, and where each one wins honestly.

What's the difference between Jira Plans and Foundation?

Jira Plans — renamed from Advanced Roadmaps in 2024 — is a feature Atlassian ships as part of Jira Premium and Enterprise. It is not a separate product, not sold on the Marketplace, and not available on Free or Standard plans. Foundation is a specialist Project Portfolio Management app from the Atlassian Marketplace, built on the Forge platform, designed specifically for cross-project portfolio work. The split is classic generalist-vs-specialist. Jira Plans is good at the 80% of roadmap work most teams need; Foundation goes deeper on the long tail — unlimited custom hierarchy, JQL-driven Sync Agents, inline spreadsheet editing, conditional formatting, five density modes, and baselines. If you only need a timeline and a few hierarchy levels, Jira Plans is enough. If portfolio management is a serious part of your work, Foundation is purpose-built for it.

Do you need Jira Premium to use Foundation?

No. Foundation runs on every Jira Cloud tier: Free, Standard, Premium, and Enterprise. This is a structural difference that matters to teams not already on Premium. Jira Plans requires Jira Premium at $15.25 USD per user per month (billed annually, as of April 2026) or Jira Enterprise (quote-only). If your team is on Standard or Free and wants portfolio visibility, Gantt charts, or hierarchy above Epic, your options are to upgrade the entire Jira subscription to Premium — at $15.25/user/month times every user on your site — or to install a specialist app. Foundation's free tier covers teams of 1–10 at zero cost, and paid tiers are priced per user per month well below a Premium upgrade. For mid-sized teams, the math rarely favors Premium purely to get Plans.

How does the hierarchy compare?

Jira Plans ships a fixed hierarchy: Themes → Initiatives → Epics → Stories → Sub-tasks. You can rename the levels and add one or two custom levels above Epic, but the structure is still broadly Atlassian-defined. Foundation has no hierarchy ceiling. You can build Portfolio → Program → Initiative → Workstream → Epic → Story → Sub-task, or any structure your organization actually uses — including non-Jira levels. Foundation's Flex Items are organizational folders that exist only inside a Lens: they do not create Jira issues, do not pollute your project with placeholder tickets, and are ideal for executive rollups or thematic groupings that don't belong in Jira's issue database. Sync Agents then automatically populate the leaves of your hierarchy from JQL queries, so adding a new Epic in Jira immediately appears under the correct Initiative in Foundation without manual relinking.

Which has stronger Gantt and critical path?

Jira Plans has a timeline view that is Gantt-adjacent: bars on a date axis, with basic dependency arrows if you have enabled them. It does not have critical path analysis, baseline comparison, or multiple zoom levels out of the box. Foundation's Gantt is a first-class feature with four zoom levels (Day, Week, Month, Quarter), all four dependency types (Finish-to-Start, Start-to-Start, Finish-to-Finish, Start-to-Finish) with drag-to-link creation, critical path highlighting you can toggle on and off, baselines to snapshot and compare planned vs actual, milestone diamonds, and drag-to-reschedule bar editing that syncs back to Jira in real time. For teams where Gantt is a serious planning surface — not just a visualization — Foundation's depth is a meaningful delta. For teams who just want "a pretty timeline to share with the CEO," Jira Plans is usually enough.

How do their cross-project reporting compare?

Both tools handle multi-project views. Jira Plans can combine issues from several projects into one Plan, filter by JQL, and roll up dates and progress. Foundation does the same but with three advantages buyers tend to notice once they try both. First, Foundation's Sync Agents update the hierarchy automatically as issues change in Jira — you don't re-run a plan refresh or wait for a batched recalculation. Second, Foundation's grid is closer to a spreadsheet than a read-only report: you can inline-edit status, assignee, dates, story points, and custom fields directly in the portfolio view, and changes sync back to Jira. Third, Foundation's conditional formatting lets you color-code cells or rows based on fourteen operators — overdue, at risk, blocked, unassigned — so a portfolio leader can scan a thousand issues and immediately see where to focus. Jira Plans reporting is solid but intentionally narrower.

Which is better for inline editing?

Foundation, clearly. Jira Plans was designed as a planning view on top of Jira, so editing is limited: you can drag bars to reschedule, change a few top-level fields, and that's approximately it. Anything deeper sends you back into the Jira issue detail page. Foundation's grid is spreadsheet-style: double- click any cell to edit status (with Jira transitions), assignee (with user search), dates (with a calendar picker), sprint, labels, priority, story points, text fields, and custom fields. Editing works across any number of selected rows at once, with the same Atlassian Design System inputs you already know from Jira. If your team uses the portfolio tool as a daily working surface — not just a read-out — Foundation saves roughly one click per edit times every edit times every user, which adds up to hours per week on mid-sized teams.

What does the cost calculation look like?

Consider a 20-user team evaluating the two paths. To get Jira Plans, you must be on Jira Premium at $15.25 per user per month (as of April 2026) — so 20 users × $15.25 × 12 months = $3,660 per year, and that is only the Premium upgrade delta if you are currently on Standard. Foundation is free for teams of 1–10 and, above that, charges a per-user monthly fee priced well below Premium's delta. A 20-user team running Foundation on Jira Standard typically spends a fraction of the Premium-for-Plans number, keeps the rest of their Jira configuration on Standard, and gets substantially deeper portfolio, Gantt, and hierarchy features. The comparison only inverts if you were going to upgrade to Premium anyway — in which case Plans is "free" to you at the margin.

When should you stay on Jira Plans?

Honest answer: three scenarios. One, you are already on Jira Premium or Enterprise for other reasons — advanced permissions, unlimited storage, 24/7 support — so Plans is included at no marginal cost and there is no reason not to use it. Two, your portfolio needs are genuinely modest: one to three projects, standard Epic-to-Story hierarchy, no serious Gantt work, no critical path requirement, no spreadsheet-style editing. Three, your team depends specifically on Jira Plans' Scenarios feature (branch-and-merge what-if planning), which Foundation does not yet match. If none of the three apply, Foundation is almost certainly the better specialist tool, and it is the dramatically cheaper path for teams on Standard or Free. Many teams simply run both — Plans for high-level scenarios, Foundation for day-to-day portfolio work — and the two do not conflict because they read the same underlying Jira issues.

Feature comparison table

Frequently asked questions

Where to go next

If you already decided a specialist tool is the right call, start with the alternative page to see the 30-second comparison and migration pattern. If you want feature detail, the Lenses, Gantt, and Sync Agents pages go deeper. If you are also evaluating Structure (the Marketplace incumbent), our Foundation vs Structure comparison covers that three-way decision honestly.