Any best practices for project portfolio management in Jira?

Hi @Vinayak Wagh,
@Ahmet Kilic and @Tomislav Tobijas already nailed the foundation (method before tool, standardize workflows, Jira Plans for the rollup), so I'll add the thing that bites after the structure is in place.
A standardized dashboard makes reporting possible, not automatically honest — at portfolio distance, a lot of "green" is just "no one's updated it yet." Building on your "key KPIs, not everything" point: track leading indicators (predict slippage) over lagging ones (status, % done — reported after the fact). Three you can build in native Jira today:
1. Stalled work in flight — "in progress" but not moving; green on the board, stuck in reality.

statusCategory = "In Progress" AND updated <= -2w
2. Scope added after commitment — the usual reason "on track" quietly becomes "three weeks late."

fixVersion = "TARGET_RELEASE" AND created >= "2026/07/01"
(swap in your real release + the date it was committed)
3. Cross-project dependencies — a board looks healthy while its blocker sits in another team's project. Native JQL is weak here, so make it a discipline: mandate "is blocked by" links and review open blockers by owning team at your cadence.

issuetype = Epic AND issueLinkType = "is blocked by"
Meta-point: standardize the minimum that has to roll up and let teams keep their own workflows underneath — over-standardizing is where adoption dies.

I'm on the marketing side at Everview (execution intelligence over Jira + GitHub). Not pitching it — everything above is native Jira — but "leading vs lagging signals" is the lens we look through, so I wanted to share the thinking, not a tool link.

Hi @Vinayak Wagh ,

Having worked on measuring and improving KPIs for PPM and multiple teams over the years, I came to the conclusion that I was tired of creating kludgy customizations. So, I built a standalone JIRA app - Multi-team Scrum Metrics & Retrospectives.

With it, you can:

• Track:
  • Data across sprints, months, quarters, half-years or years. 
  • Several teams (including those ones sharing the same project) at once.
  • Velocity, capacity, allocation, completed story points (completed scope), planned (initial, final scopes), added and removed scopes, as well as other metrics. You can even create your own custom metrics or KPIs using JQL.
  • Trends and average metrics across periods.
• Conduct Quantifiable retrospectives.
• And many more.

3 boards/teams in the same view, 1 period selected for analysis:

3 boards/teams in the same view, all periods are clicked for average metrics and dynamics:

Answers from everyone here are all correct, lately native Jira features have improved considerably for portfolio management, but you'll need an Enterprise account to get the "Plans" feature. 

Also 3rd party add-ons are a possibility as there's almost a tool for any specific need, you can end up getting several tools to achieve what you need. 

If you're looking for options, at Millarum we specifically create add-ons on a cost effective way where you get roughly 80% of the features than others at a fraction of the cost. 

Millarum Dashboards are our alternative to Rich Filters, and it includes distribution charts as histogram and pareto that are really effective now with formula fields, also we support Sankey diagrams for 6 dimensions of data visualization in the same chart.

Millarum Roadmap is a one pager visualization where a full Program or Portfolio is monitored as swimlines and milestones, this is a unique add-on in the marketplace.

Hello @Vinayak Wagh,

I wanted to add another option to the discussion.

Just to be transparent: I'm part of the team behind Quick Filters for Jira Dashboards.

If you're looking for a lean, easy-to-configure dashboard solution, it might be worth considering.

One of its biggest advantages is cross-space reporting. It matches fields (such as Status, Components, or custom fields) by name instead of ID, making it easy to build dashboards across multiple Jira spaces without ending up with duplicate values.

With the Quick Controller, users can switch from an organization-wide view to individual Jira spaces directly on the same dashboard. This lets you maintain a single dashboard while giving different stakeholders exactly the view they need.

Another thing I like is how lightweight it is: all configuration happens directly on the dashboard. Just enter the JQL where you need it—there's no need to create and maintain saved filters, which keeps administration to a minimum.

Happy to answer any questions if you'd like to know whether it would be a good fit for your use case.

Have you also checked this article: https://www.atlassian.com/agile/product-management/portfolio-management

This is more leaned JPD, but you can tailor it to Jira as well.