Jira is a delivery tool, and on its own it covers only part of project portfolio management (PPM). Jira PPM needs Jira for the delivery work plus somewhere to decide which projects get funded, record those decisions, and check whether the money paid back.
That second half is where many PMOs on Jira end up with spreadsheets, slide decks and email threads. This guide maps what Jira Cloud does natively, what PPM adds, and the options for filling the gap. If you want the longer method behind it, Tollgate's guide to Jira project portfolio management covers it in depth.
Tollgate is a Forge app for Jira Cloud, listed on the Atlassian Marketplace, that adds investment governance to Jira projects. It is built by Softwired, a Brisbane consultancy.
What Jira Cloud does natively
Jira is very good at the question your delivery teams ask every day: what is being worked on, by whom, and is it moving?
Work items carry the detail, boards show how work flows, and timelines show when it is due. Every status change is time-stamped, so Jira holds an accurate history of what the team did and when.
Atlassian also offers Plans, included with Jira Premium and Enterprise. According to Atlassian's own documentation, Plans let you combine work items from boards, spaces and filters into a plan that spans multiple teams. You can use a plan to estimate release dates for work across teams, answer staffing and resource questions, and map out yearly goals. Plans add hierarchy levels such as initiatives, show dependencies, let you try changes in a sandbox before saving them to Jira, and schedule work at a pace your teams can handle.
That is a strong set of delivery and planning features. If your question is "when will this work land, and do we have the people to do it?", Jira and Plans answer it well.
What PPM adds on top of Jira
Portfolio management asks a different question: should this work be funded at all, and is it still worth the money?
The sponsor asks that question at a slower pace than the team, usually at monthly or quarterly steering committees. Answering it needs records that Jira has no native home for.
Intake
Ideas and requests arrive from everywhere. PPM gives them one way in, with enough information to judge them side by side. Without it, the loudest request gets started first. Tollgate's guide to project intake sets out a five-step process from request to funded project.
The business case
A business case states the problem, the outcome you expect, the cost, and the return you are underwriting. It becomes the baseline every later decision is measured against. In Jira, a business case usually lives as an attachment, if it lives anywhere.
Gate decisions
A gate is a point where someone with authority decides whether a project continues, changes or stops. PPM records who decided, what they decided, the conditions attached, and the evidence in front of them at the time. Jira records that a work item moved. It does not record that a sponsor approved the spend. Tollgate's guide to stage gates in Jira covers how a gate review works when delivery runs in Jira.
Change control
Once a business case is approved, changes to scope, cost or time should be raised, assessed and decided, then measured against the original baseline. Jira shows that the backlog changed. PPM records why it changed, who agreed to it, and what it did to the cost and the date. Without that record, a project can drift a long way from its business case through a series of small, reasonable-looking decisions, and nobody can say afterwards when the drift happened.
A portfolio view of investments
A portfolio view compares investments: what each one costs against its baseline, where it sits in the lifecycle, how confident its owner is, and which ones need a decision. That differs from a view of work items across teams.
Benefits
After delivery, someone should check whether the investment delivered what the business case promised. This step is often skipped, yet it is the one that teaches the organisation most about its next round of funding decisions.
How the gap shows up in practice
When a PMO runs on Jira without these records, a familiar pattern appears. Before each steering committee, someone exports data from Jira, pastes it into a slide deck and writes the commentary. The numbers are out of date by the time the meeting starts. Decisions are recorded in minutes, if at all, and are hard to find at the next gate.
None of this is a failing of Jira. Jira was built to manage work, and it does that well. The governance records simply need a home, and the further that home sits from Jira, the more copying it takes to keep it current. Tollgate's guide to project status reports looks at that weekly rebuild in detail.
Public-sector programs show why the gap matters at scale. The UK government publishes delivery confidence ratings for its major projects every year, and the NISTA Major Projects Annual Report 2025-26 records 34 of 189 projects rated red at 31 March 2026, each rating published against the project. Tollgate Data's analysis of how many UK major projects are rated red explains what those ratings mean.
Your options for Jira PPM
There are four broad options. Each suits a different organisation, and many PMOs combine two of them.
Jira and Plans on their own
If your portfolio questions are mostly about scheduling, capacity and dependencies, Plans may be enough. You keep everything in Jira, and there is nothing extra to buy if you already have Jira Premium or Enterprise. Business cases and gate decisions will still need a home somewhere else.
Jira Align
Atlassian describes Jira Align as connecting enterprise strategy to team-level delivery, across portfolios, programs and value streams. Atlassian positions it as an app in its Strategy Collection for enterprise leaders. It suits large organisations running scaled planning across many teams.
Marketplace portfolio apps
The Atlassian Marketplace lists several portfolio and planning apps that extend Jira in different directions, such as hierarchy, resource planning or reporting. Read each vendor's own documentation, and check what it adds against the five PPM needs above.
A standalone PPM platform
Some organisations run a separate PPM system and connect it to Jira. This can work well where the PMO governs more than Jira projects. The cost is the connection: data has to flow between two systems, and someone has to keep it accurate. Ask how often the link updates, which fields it carries in each direction, and who fixes it when the two systems disagree. Those answers decide whether the steering committee sees current figures or last week's.
Questions to ask before you choose a Jira PPM option
The right option depends on the questions your sponsors and steering committees actually ask. Work through these with your PMO before you look at any product.
- Who approves funding for a new project today, and where is that approval recorded?
- What does a business case contain, and where does it live once it is approved?
- How many gates does a project pass through, and who decides at each one?
- Do your approvers have Jira licences, or do some of them never log in?
- How long does it take to prepare the steering committee pack each cycle?
- Where are risks, decisions and change requests recorded, and can you find last quarter's?
- Does anyone check benefits after delivery, and against what baseline?
If most answers point to Jira, you may only need Plans. If most point to spreadsheets, email and slide decks, the governance half of PPM is where to look first.
What to keep in Jira, whichever option you choose
Whatever you add, keep the delivery work where it is. Teams should keep their boards, work items and sprints, because that is where the most accurate evidence about progress lives.
The governance layer should read that evidence, never ask teams to re-enter it. A PPM setup that makes delivery teams update a second system each week tends to go stale within a few cycles. The better test of any option is how little it asks of the teams doing the work, and how much of the steering committee's information it can draw from Jira directly.
Keep one more thing in mind. A portfolio tool can show where every investment stands, but it can't make the decision. The value comes from a sponsor deciding on current evidence, and from that decision being written down where the next gate can find it.
Where Tollgate fits in a Jira PPM setup
Tollgate adds the governance records Jira has no home for, inside the Jira project itself. It treats each project as a funded investment moving through a gated method. Its default method, SAM, groups six stages into three acts: Commit, Run and Realise.
Each project gets an investment thesis (the problem, the outcome and the return you underwrite) and a business case. Gate approvals are made by named governance seats, such as the sponsor, and a seat can be filled by someone without a Jira licence. Risks, decisions and changes are separate registers, each with its own workflow. A decision is never edited away; you correct it with a note. The financial case computes a forward ROI target using NPV, IRR and payback. Tollgate does not keep a live realised-ROI score, and the benefits verdict is the sponsor's call at the end.
Tollgate works alongside Jira Plans. Plans answers when work will land across teams. Tollgate answers whether each investment should continue and records who decided. Tollgate's comparison of Jira Plans and a portfolio governance app sets out what each does.
Frequently asked questions
Is Jira a PPM tool, or do I need an add-on?
Jira manages delivery work well, and Plans in Jira Premium and Enterprise adds cross-team planning. For business cases, gate decisions, a portfolio view of investments and benefits tracking, many PMOs add an app or another system.
What is the difference between Jira Plans and PPM?
Plans schedules work across teams, at a pace teams can handle, taking dependencies into account. PPM decides which work gets funded, records the decisions at each gate, and checks whether the investment paid back.
Can you do portfolio management in Jira without Jira Align?
Yes, many organisations do, using Plans for scheduling and a Marketplace app or a lightweight process for business cases and gate decisions. Jira Align suits large organisations running scaled planning across many teams.
What does PPM stand for?
PPM stands for project portfolio management, the practice of choosing which projects to fund, governing them through gates, and checking whether they delivered the benefits promised.
Does Tollgate replace Jira Plans?
Tollgate works alongside Plans. Plans answers when work will land, and Tollgate holds the business case, the gate decisions and the risk, decision and change registers for each investment.
Tollgate is free for up to 10 users. Install free for up to 10 users.
Want to talk through how this applies to your team? Book a call with Softwired.
