Jira project portfolio management is the practice of planning, tracking, and governing many projects at once inside Jira. This guide covers what native Plans does, what roadmap apps add, and the investment record that neither keeps.
Jira project portfolio management is the practice of planning, tracking, and governing many projects at once inside Jira, so that an organisation can see where its delivery capacity is going and decide whether the spend is still justified. A single Jira project answers for its own backlog. A portfolio answers for the money.
Jira began as an issue tracker for one team’s work, and it remains very good at that job. Everything portfolio-shaped arrived later, in layers. If portfolio management has landed on your desk, because you lead the PMO or because you own Jira and the CFO wants to know what the licences produce, you are evaluating three layers. The first is what Jira ships natively, the second is what Marketplace roadmap apps add, and the third is the governance layer that neither keeps. Most of what is sold as Jira PPM sits in the first two.
Start with what you already pay for. Every Jira project gives a team a backlog, a board, and a workflow. Dashboards and saved filters let you assemble cross-project views by hand and JQL slices issues any way you like, so for a small portfolio a dashboard of filter gadgets is a legitimate answer, and plenty of PMOs run on exactly that.
The purpose-built layer is Plans, previously called Advanced Roadmaps, which Atlassian includes in Jira Premium and Enterprise, and which pulls issues from multiple projects and boards into one timeline, models dependencies between them, adds hierarchy above the epic, and sketches capacity against teams and sprints. It also supports scenario planning. You can test a reshuffle before you commit to it. For the scheduling half of portfolio management (what is happening, in what order, blocked by what) Plans is a serious tool, and most organisations use less of it than they have paid for.
It holds the delivery schedule. It records when epics start and finish. It has no field for what any of them cost, what benefit was promised in exchange, or who approved the spend, because Jira gives those facts no native home.
The Atlassian Marketplace has a mature category of portfolio and roadmap apps, and they extend the same scheduling layer. They add richer cross-project timelines and Gantt views, deeper work hierarchies, program boards, capacity and resource planning down to the individual, and portfolio views on Jira tiers that do not include Plans. Teams that have outgrown the native tooling, or never had it, generally find what they need here.
These apps do their job well. They answer delivery questions at portfolio scale: who is working on what, where dependencies collide, and whether the plan survives contact with real capacity. If the roadmap no longer fits on one screen, these apps fix that.
The apps share a frame with native Plans. Both are delivery instruments, and their unit of interest is a piece of work with its dates. An investment and its business case sit outside that frame.
Portfolio management exists because someone is paying for the portfolio, and the people paying ask different questions from the people delivering.
Delivery tooling answers one question well. Are we shipping? Boards, timelines, velocity charts, and burndowns all serve it, and between native Jira and the roadmap apps it gets a thorough answer.
The funding side brings three questions of its own.
A project can be green on every delivery measure and still be a bad investment, because the team ships, the sprints are healthy, and the timeline holds while the business case that justified the spend eroded two quarters ago. That possibility is why portfolio governance exists as a discipline separate from delivery management.
In most organisations running Jira, the answers to those three questions live outside Jira. The business case is a slide deck from the approval meeting, the approval is an email or a minute in a document nobody can find, benefits were estimated once in a spreadsheet and never revisited, and stage gates happen in meetings whose outcomes are recorded inconsistently or not at all.
The gap runs between two kinds of record. The delivery record in Jira is thorough, with every status change, comment, and estimate revision timestamped and attributed. The investment record depends on memory, which is a poor place to keep it. When an auditor, a sponsor, or a new CFO asks who approved this spend, on what numbers, and what has changed since, someone goes digging through old decks. Roadmap apps do not keep this record because it was never their job, and native Jira does not keep it either.
Tollgate is a Forge app built by Softwired that keeps the investment record inside Jira, beside the delivery record.
Each initiative carries a business case, and the financial case computes NPV, IRR, and payback from the cashflows you enter. Work packages link to Jira epics, which ties the investment view to the delivery view without duplicate data entry. Risks & Opportunities sit with the initiative they belong to. Decisions and Changes record approvals and scope changes with an audit trail. Finding who approved what, when, and on what numbers takes one lookup. Investment Health and Tollgate Portfolio summarise all of it with RAG status, so a steering committee can see the state of every investment in one place.
Tollgate works alongside roadmap tools. Keep Plans or your roadmap app for schedule, dependencies, and capacity. Use Tollgate for the case, the gates, the risks, and the record. The two layers answer different questions and coexist on the same Jira site.
Tollgate is built on Forge, Atlassian’s app platform, so it runs on Atlassian infrastructure with no Softwired server in the path. That shortens the security review, because there is no additional third party to assess. It is free for up to 10 users and priced per user through the Atlassian Marketplace above that, on the same bill as Jira itself.
If the investment record is the layer your portfolio is missing, view Tollgate on the Atlassian Marketplace.
Tollgate keeps the business case, the gate decisions and the payoff in one record, next to the delivery they pay for.