Jira portfolio management: how to build a cross-project roadmap your stakeholders will actually read

[#1]

An HPD I’ve interviewed couple of weeks ago has recently taken up his position at a major EU energy company. He is in a process of streamlining project management for 100+ people working across 34+ growing projects. His portfolio is worth nine figures. And his board reporting process familiar to many of us: exporting data from each Jira project, manually aggregating it in spreadsheets, building presentation slides every single month.

“If I can use a live dashboard — clean, informative and readable,” he told me, “I save 20 hours a month.”

This guide is for you if you manage multiple Jira projects and spend too much time stitching together a portfolio view that should already exist. You’ll learn the native route (Jira Plans) and the visual one—plus the data foundation you need before either one works.

Getting your Jira data portfolio-ready

Every Jira portfolio management tool reads from the same source: the data inside your Jira spaces and issues. If it is incomplete or unreliable, your portfolio view will be too. First of all, planning means placing things on a calendar. To find which epics are missing dates, run this query:

JQL audit query

type = Epic AND (startDate is EMPTY OR dueDate is EMPTY)

Then, make sure all of your projects share the same issue type structure. If some projects use Epics while others only have Tasks, there is no way to group them consistently.

Same with teams: if you plan to group or filter by team, create your Jira teams and assign members before you start.

Initiatives: grouping epics under strategic goals

Standard Jira uses Epic → Story → Subtask. At the portfolio level, you will probably need one more layer: Initiatives. It is an issue type above Epics that groups related work across projects. Say we’re opening a new office in Berlin. Underneath one Initiative we've got 'Sign the lease' in our Operations project, 'Hire local staff' in HR, and 'Set up IT infrastructure' in IT. That’s three teams, three projects and without Initiatives, they will look completely unrelated in Jira.

Initiatives are available in Jira Plans (Jira Cloud Premium and Enterprise). To set them up, a Jira admin creates the Initiative issue type, adds it to the work type scheme, and maps it above Epic in the hierarchy settings.

Should I use Jira Plans?

If your org pays for Jira Premium, Jira Plans is the native portfolio tool. The setup flow looks like this:

1. Create a plan and add your Jira projects as issue sources.
2. Configure hierarchy — map issue types to plan levels (Epics by default; add Initiatives if needed).
3. Set dependencies between epics to visualize blockers across projects.
4. Configure capacity — assign teams, set velocity or hours per sprint.

It's powerful for large orgs and SAFe shops — but requires Premium pricing (~$18.30/user/month), admin setup, and operates as a sandbox where changes must be committed back to Jira. For teams that need something faster or run on Standard/Free, there's a visual alternative.

The visual alternative—portfolio management without the complexity

Remember the PMO lead from the intro? His requirements: all projects on one timeline, grouped by team, milestones visible, readable for executives—and no four-hour setup. This is where Planyway comes in.

Connect, group, plan

Install Planyway from the Atlassian Marketplace. Add your Jira spaces as sources (you can also connect boards or JQL filters if you want to keep things focused). Open the timeline and set Group by Space — that's your portfolio view. (See the Getting started guide for the full setup.)

Need more detail? One click switches you to Group by Epic, Team, or User.

A key difference from Jira Plans: in Planyway, dragging a task onto the timeline is how you set its dates. Move a card, and Jira updates instantly — like Google Docs, always saved, always visible to everyone. No sandbox, no "Review changes" button.

Layer in the details your board cares about: milestones (including Epic Milestones that that break down epics into key deadlines), sprints to align delivery cycles with your roadmap, releases to track progress by Jira Fix Versions, and dependencies between tasks to spot blockers before they hit. All of this lives on one timeline. And you can share it with stakeholders via a link (they'll see exactly what you see) or export to PDF/Excel for offline reporting.

At any moment you can switch from the high-level project overview into the workload view to see what really stands behind your plan. It shows team members with their tasks across all connected projects. When someone is overloaded, you’ll see it instantly. Just drag a task to someone else to rebalance. Simple as that.

Making difference at board meetings

Before: the Sunday slide deck	After: the live portfolio view
Export Jira data from each project manually	All projects on one live timeline
Aggregate status in a spreadsheet	Group by project, epic, or team—one click
Build a slide deck	No slides — open one timeline instead
Reschedule = re-export + rebuild slides	Drag to reschedule; Jira updates instantly
Present static slides, schedule follow-ups	Show the dashboard live, drive decisions in the room

🎯The three questions your board will always ask

Every steering committee meeting comes down to three questions:

1. Where are we on each project? (timeline + milestones)

2. Are our people overloaded? (resource utilization)

3. Are we on track vs. the original plan? (progress against baseline)

Choosing your path: Jira portfolio management tools compared

Here’s how the main options stack up. This isn’t exhaustive—for a full comparison of eight portfolio plugins, see our detailed breakdown.

Tool	Portfolio view	Resource mgmt	Min Jira plan	Starting price
Jira Plans	Cross-project timeline + scenario planning	Team-level capacity (no individual drill-down)	Premium	~$14.50 /user/mo
Planyway	Multi-project timeline + shareable views (link, PDF, Excel)	Visual workload per person across all projects, vacations and holiday management	Free / Standard	Free (≤10); $3/user/mo
BigPicture	Gantt + Kanban + SAFe program board	Resource sheets + risk matrices	Standard	From $5.21/user/mo
ActivityTimeline	Resource-focused timeline (integrates with Jira Plans for roadmap layer)	Deep: individual + team capacity, skills, leave management	Standard	From $1/user/mo
Structure	Hierarchy views (Gantt requires Advanced tier)	Computed rollups, no visual workload	Standard	From $4.73/user/mo

The comparison table gives you the overview, but the right choice depends on your situation: how big your org is, what Jira plan you're on, and whether you need enterprise-grade features or just want portfolio visibility working this week.

Conclusion: the best portfolio tool is the one your team actually uses

The PMO lead from our opening story didn’t need the most powerful tool. He didn’t need SAFe-grade forecasting or velocity-based capacity models. He needed to walk into a board meeting, open a dashboard, and answer questions on the spot—without having spent 20 hours preparing slides.

That’s the real benchmark for any Jira portfolio management setup: does it let you stop reporting and start deciding? Whether you go with Jira Plans, Planyway, or something else entirely, start with clean data, pick the path that fits your org’s complexity and budget, and—most importantly—actually use it. Because the most expensive portfolio tool is the one that collects dust while you go back to building slide decks on Sunday night.

Ready to build your first portfolio roadmap? Get started