Updated · All guides
The short answer
You can build a useful portfolio dashboard in Jira with one saved cross-project filter and four or five gadgets: work by project and status, overdue and blocked lists, and created-versus-resolved trends. What it cannot show is which projects will slip and why, whether the people exist to deliver them, and how far each date can be trusted. Those need signals combined across projects, capacity and leave, which is what a software delivery intelligence layer adds on top of Jira.
Build the dashboard in Jira
-
Create one saved filter for the portfolio. Every gadget will use it, so the dashboard stays consistent.
project in (ABC, DEF, GHI) AND statusCategory != Done
If your projects share a project category,category = "Client delivery" AND statusCategory != Donepicks up new projects automatically. - Add a Two Dimensional Filter Statistics gadget with projects on one axis and status on the other. This is the closest Jira gets to a portfolio overview.
-
Add a Filter Results gadget for overdue work, sorted by due date:
project in (ABC, DEF, GHI) AND statusCategory != Done AND duedate < now() ORDER BY duedate ASC -
Add a Filter Results gadget for blocked work, adjusted to how your workflow marks blocks:
project in (ABC, DEF, GHI) AND (status = Blocked OR Flagged is not EMPTY) - Add a Created vs. Resolved Chart over the last 90 days, by week. If created stays above resolved, scope is growing faster than it is delivered.
- Add a Pie Chart by assignee on the open-work filter. One name holding a large slice across several projects is a capacity risk.
- Share the dashboard with delivery leads and leadership, and review it at the same time every week.
What the dashboard cannot show
Here is what leaders actually ask, and what a Jira dashboard can answer:
| The question | What the dashboard shows | What is missing |
|---|---|---|
| Which projects will slip? | Open and overdue counts per project | One risk measure per project, combining the signals, so projects can be ranked |
| Why? | Lists of individual issues | The main cause per project: blocked work, overload or a slipping plan |
| Do we have the people? | Issues per assignee | Allocation across projects, part-time capacity and approved leave |
| Can we trust the date? | Due dates, where they exist | How complete the estimates, due dates and assignees are behind each forecast |
| Is it getting better or worse? | Mostly today's state | The trend in each project's risk, week on week |
And one thing no dashboard does: write the summary. Someone still has to look at every gadget, decide what matters and turn it into the weekly executive status report. That is usually where the PMO's hours go.
Common workarounds, and their limits
- A "RAG status" custom field. Gives you colours on the dashboard, but they are typed in by hand, with all the problems described in project risk scoring vs RAG status.
- Exporting to a spreadsheet each week. Lets you add allocation and leave, but it is manual, goes stale within days and depends on one person.
- Jira's planning features. Depending on your Jira plan, timeline and planning views can schedule work against team capacity. They help plan the work; they do not score risk or report forecast reliability across a portfolio.
- Reporting apps from the Atlassian Marketplace. Many add better charts. Check whether they combine Jira data with allocation and leave, and whether they explain their numbers.
What to add on top of Jira
The gap is not more charts. It is combining signals per project, adding the people data Jira does not hold, and turning the result into a ranked list and a short brief. That is what software delivery intelligence does, and it works alongside Jira rather than replacing it.
Exentras connects to Jira Cloud read-only and syncs your projects and issues on a schedule. It adds a 0–100 risk score per project with the causes behind it, delivery forecasts with a separate reliability rating, team capacity across projects adjusted for approved leave, and a weekly executive brief that ranks projects by risk. Teams keep working in Jira exactly as before. See what Exentras adds on top of Jira or how the Jira connection works.