How to Access Advanced Roadmaps in Jira

If your team is managing multiple projects, tracking cross-functional work, and trying to keep everyone aligned — Jira’s Advanced Roadmaps feature might be the single most powerful tool you’re not using.

Studies show that only 35% of projects are completed on time, on budget, and with all original features (PMI Pulse of the Profession). Visibility gaps between teams are one of the biggest culprits. Advanced Roadmaps in Jira was built to fix exactly that.

This guide walks you through everything — from understanding what Advanced Roadmaps actually does, to accessing it, setting it up, and making it work for real teams across real projects.

What Are Advanced Roadmaps in Jira?

Advanced Roadmaps (previously called “Portfolio for Jira”) is a premium planning feature inside Jira Software that gives you a high-level, multi-project view of your work. Instead of looking at one backlog at a time, you see dependencies, timelines, and capacity across every team — in one place.

Think of it like this: Jira’s standard roadmap shows you what your team is doing. Advanced Roadmaps shows you how everything fits together across the entire organization.

Key capabilities include:

• Cross-project planning — manage epics, stories, and initiatives spanning multiple teams
• Dependency mapping — visualize blockers and connections between issues before they become problems
• Capacity planning — see who’s overloaded and who has bandwidth before you commit to a sprint
• Scenario planning — test “what if” timelines without touching live project data
• Hierarchy levels — work with Initiatives, Epics, Stories, and Tasks in a single timeline view

According to Atlassian’s own research, teams using Advanced Roadmaps report up to 40% reduction in planning time compared to teams using manual spreadsheet-based planning.

Who Gets Access to Advanced Roadmaps?

This is where most people get confused. Advanced Roadmaps is not available on every Jira plan. Here’s the breakdown:

Jira Software Cloud:

• Free plan — ❌ Not available
• Standard plan — ❌ Not available
• Premium plan — ✅ Included
• Enterprise plan — ✅ Included

Jira Software Data Center:

• Available as a bundled feature on Data Center versions 8.15 and above

If you’re on a Free or Standard plan and want Advanced Roadmaps, you’ll need to upgrade to Premium or Enterprise. Atlassian positions Premium at around $15.25 per user/month (billed annually) as of recent pricing updates — though exact pricing should always be confirmed on their official site.

Over 10 million users work inside Jira daily (Atlassian, 2023), and the Premium tier has seen significant growth as distributed teams increase demand for cross-team visibility tools.

How to Access Advanced Roadmaps in Jira (Step by Step)

Check Your Plan First

Before anything else, confirm you’re on a Premium or Enterprise Jira Software Cloud plan. Navigate to Settings → Billing in your Atlassian admin panel. If you see “Jira Software Premium” in your active products, you’re good to go.

Navigate to the Plans Section

Once confirmed:

1. Open Jira Software from your Atlassian homepage
2. In the top navigation, click Plans (you’ll find this in the left sidebar or top menu depending on your layout)
3. If it’s your first time, you’ll land on a “Create a plan” screen
4. Click Create plan

If you don’t see the Plans option in your navigation, your account may not have the correct permissions — you’ll need your Jira admin to grant access.

Create Your First Plan

When creating a plan, Jira will walk you through a short setup wizard:

Step 1 — Name your plan
Give it a clear, descriptive name (e.g., “Q3 Product Launches” or “Engineering Roadmap 2025”).

Step 2 — Add issue sources
This is where the power lies. You can pull issues from:

• Specific Jira boards
• Projects (by name or filter)
• Pre-existing Jira filters

You can mix and match sources — pulling work from your design team’s project and your engineering team’s backlog into the same plan.

Step 3 — Set your hierarchy
Choose the levels you want to see. The default includes Epics and Stories, but you can add Initiatives or Sub-tasks depending on your team’s structure.

Step 4 — Configure your date range
Select the timeframe you want your roadmap to cover — from a single sprint to a full fiscal year.

Step 5 — Save and open
Click Create and your plan will generate automatically, pulling in all matching issues from your chosen sources.

Key Features to Explore Once You’re Inside

The Timeline View

The timeline is the heart of Advanced Roadmaps. It shows all your epics and stories laid out against a calendar. You can drag and resize bars to adjust dates, and Jira automatically flags scheduling conflicts.

Pro tip: Use the zoom controls to switch between day, week, month, and quarter views depending on how granular you need to be.

Dependency Mapping

Jira Advanced Roadmaps lets you draw dependency lines directly on the timeline. When issue B can’t start until issue A is done, you link them — and the roadmap will visually alert you if the sequence becomes impossible due to date changes.

Research by the Project Management Institute shows 48% of projects experience scope creep — most of it caused by undocumented dependencies catching teams off guard. Dependency mapping directly reduces that risk.

Capacity and Workload Planning

Navigate to the Workload view inside your plan. This shows you:

• How many story points each person is assigned per sprint
• Where team members are over-capacity
• Which sprints have unallocated bandwidth

This view is especially valuable before sprint planning. Instead of discovering mid-sprint that your two senior contributors are booked solid, you spot it in advance and redistribute work.

Scenario Planning

This is one of Advanced Roadmaps’ most underused features. Scenarios let you model “what if we moved this epic by two weeks?” without changing your actual live plan.

To use it:

1. Click Scenarios in the top right of your plan
2. Create a new scenario
3. Make adjustments — move dates, reassign work, remove or add issues
4. Compare the scenario against your current baseline

Teams use this to stress-test delivery dates before presenting commitments to leadership, customers, or other departments. It’s a low-risk way to have high-stakes planning conversations.

Auto-Scheduling

Advanced Roadmaps includes an Auto-schedule function that automatically assigns dates to unscheduled work based on team capacity, sprint velocity, and existing commitments. For large backlogs, this can save hours of manual planning.

Managing Permissions and Team Access

Not everyone on your team needs full edit access to the plan. Jira Advanced Roadmaps supports role-based access:

• Viewers — can see the roadmap but cannot make changes
• Editors — can modify the plan, add issues, change dates
• Admins — control plan settings and permissions

To adjust permissions, go to Plan Settings → Permissions inside your plan. Here you can assign access by individual user, team, or Jira group.

A common setup is to give product managers editor access while keeping other stakeholders as view-only — so leadership can review the roadmap without accidentally breaking the plan.

Syncing Changes Back to Jira

One important detail: changes you make in Advanced Roadmaps don’t automatically update your live Jira projects. They stay in a “review” state until you explicitly review and save them.

Here’s how to commit changes:

1. After making edits, look for the Review Changes button (top right corner)
2. Jira will show you a summary of every change made — date shifts, new assignments, status updates
3. Review each item and either confirm or discard
4. Click Save to push confirmed changes into your live Jira projects

This two-step process is intentional. It prevents accidental updates and gives you one last checkpoint before anything goes live.

Common Issues and How to Fix Them

“I can’t see the Plans option in my navigation”
This usually means either (a) you’re on a Free or Standard plan, or (b) your Jira admin hasn’t granted you access. Check your billing tier and ask your admin to enable access.

“My issues aren’t appearing in the plan”
Make sure the issue source is configured correctly. If you added a board but the board has a filter that excludes certain issue types, those won’t appear. Go to Plan Settings → Issue Sources and verify your filters.

“Changes I made didn’t show up in my Jira project”
You likely didn’t complete the Review Changes step. Return to your plan, click Review Changes, and commit the updates.

“The capacity view shows wrong numbers”
Capacity calculations depend on your team members having accurate working hours set. Go to Plan Settings → Teams and confirm daily working hours are configured per person.

“Dependency lines aren’t showing up”
Dependency visualization can be toggled. In the timeline view, click the eye icon or View Settings and make sure “Dependencies” is turned on.

Advanced Roadmaps vs. Basic Roadmap: What’s the Difference?

If your team is small, working on a single project, and doesn’t need cross-functional alignment, the basic roadmap might be enough. But once you’re coordinating work across two or more teams — or managing initiatives that span multiple quarters — Advanced Roadmaps becomes genuinely essential.

Teams that move from basic roadmaps to Advanced Roadmaps report a 30% improvement in on-time delivery rates according to workflow efficiency studies on enterprise Agile adoption.

Tips to Get the Most Out of Advanced Roadmaps

Start with one plan, not many. It’s tempting to create a plan for every project. Resist this. One cross-team plan that pulls from multiple sources is far more useful than five siloed plans.

Keep your hierarchy clean. Advanced Roadmaps works best when your issue hierarchy is consistent. If some teams use Epics differently from others, the roadmap becomes confusing fast. Align on definitions before building your plan.

Use labels and components for filtering. Inside your plan, you can filter by labels, teams, or components. This lets you quickly toggle between views — “show me only the mobile team’s work” or “show me only work tagged as critical.”

Review your plan weekly, not monthly. Advanced Roadmaps is a living document. Checking in weekly during sprint planning ensures the data stays accurate and the plan remains a trusted source of truth.

Train your team on Review Changes. The most common mistake new users make is editing their plan and not committing the changes. A 10-minute walkthrough with your team on the Review Changes workflow prevents a lot of frustration.

Conclusion

Advanced Roadmaps in Jira closes the visibility gap that causes most team delivery problems. Once you have access through a Premium or Enterprise plan, the setup is straightforward — create a plan, connect your issue sources, define your hierarchy, and start working in a timeline view that shows the full picture.

The statistics are clear: teams with proper cross-functional planning tools deliver faster, miss fewer deadlines, and communicate better. Advanced Roadmaps is the mechanism that makes that possible inside Jira.

Start with one plan. Pull in two or three key projects. Map your dependencies. Run one scenario before your next sprint planning session. That’s all it takes to feel the difference.

The teams that win aren’t the ones who work harder — they’re the ones who can see further