Short answer: In Portfolio by HeroCoders, you can filter a whole Jira portfolio by the signals that actually predict trouble: capacity alerts, delivery alerts, time in status, forecasted start and end dates, your own formulas, and planned or actual cost and revenue. Combine them, save the view, and you have a standing list of at-risk work instead of a status meeting.
Most Jira filters answer "which work items match these fields?" That's useful, but it isn't the question a portfolio lead asks on a Monday morning. The real question is "what's about to slip, and why?" This post shows how to build filters that answer it.
Why a list of work items isn't a risk view
A JQL filter can tell you that an epic is in progress, assigned to Priya and due on the 30th. It can't tell you that Priya is booked for 60 hours that week, that two of the epic's stories end after the epic does, or that the work has been sitting in review for nine days.
That information lives in Portfolio by HeroCoders, our PPM and capacity planning app for Jira. Portfolio works out workload from your estimates and each person's availability, compares child dates against parent dates, tracks how long work stays in each status, and rolls numbers up your hierarchy. Filtering on those signals is what turns a portfolio from a list into an early-warning system.
Step 1: Set the right scope
Every portfolio starts with a scope: the slice of Jira you're planning. A scope can pull in several projects, individual work items from other projects, chosen work item types and status categories, and a time range. If you prefer, write JQL instead.
Scopes can also include conditions on Jira fields and custom fields. That means a scope can be "all epics in our three delivery projects where Customer is Acme", or "everything tagged to the Q4 platform initiative", without maintaining a separate saved filter in Jira.
You can keep several named scopes in one portfolio. Each appears as its own tab and has its own group in the table, so you can compare, say, two product lines side by side.
Step 2: Filter on what Portfolio knows
Once the scope is set, advanced filtering in the Table view works on Portfolio's own insights, not just on Jira fields. Here's what each one lets you find.
| Filter on | The question it answers |
|---|---|
| Capacity alerts | Which work is assigned to someone who's overbooked? |
| Delivery alerts | Which parents have children ending after them, or are past their dates with no progress? |
| Time in Status | What has been stuck in review, blocked or waiting for too long? |
| Calculated start and end dates | When are those workstreams supposed to start or finish? |
| Custom formulas | Anything you can calculate: days overdue, estimate accuracy, budget remaining |
| Planned and actual revenue and cost | Which epics or initiatives are over budget, or below the margin you planned? |
You can apply several filters at once and switch each one on or off without rebuilding the view. Quick filters sit alongside them for the toggles you use every day.
Five at-risk views worth saving
Here are the views we'd build first. Each takes a minute or two to set up, and each replaces a question someone currently asks in a meeting.
1. Work Items with overbooked resources
Add the Capacity Alert column and filter to work items that have an alert. You now have every piece of work assigned to someone who doesn't have the hours for it. Hover an alert to see which days are overbooked, then click it to open the capacity plan and reschedule or reassign the work.
Capacity is worked out from the estimate field you choose, each person's working hours and days, their holiday calendar and their booked time off. The Capacity Planner shows the same picture by person, colour-coded so overbooked people stand out. For a deeper look at the planner itself, read Portfolio by HeroCoders: Your New Jira Capacity Planner.
2. Parents at delivery risk
Group by hierarchy, add the Delivery Alert column and filter on it. You'll see every epic or initiative where a child ends after its parent, or where the work is past its start or due date with no progress. These are the items where the plan and the work have quietly drifted apart.
3. Stuck in a status
Add Time in Status, choose the statuses you care about (for example In Review and Blocked), and filter for anything above your threshold.
4. Forecast to miss the window
Calculated start and end dates show the earliest start and latest end across each group's work. Filter on the calculated end date to list every initiative now forecast to finish after the end of the quarter. Because the dates come from the work underneath, the forecast moves as soon as the plan does.
5. Over budget
Plan revenue and costs on your portfolio items, then use Custom formulas to compare them with actuals. A formula like this.plannedCost - this.clockwork_cost gives the budget remaining. Filter it for values below zero and you have a list of everything that has overspent.
Planning revenue and cost works in every edition. Actual cost and revenue come from worklogs in Clockwork Pro and need the Portfolio Advanced edition. We cover the setup in Show Me the Money: Viewing Costs & Revenue in your Jira Portfolio.
Combine filters for sharper answers
Each filter is useful on its own. Combined, they answer the questions that matter most:
- Overbooked and forecast late: capacity alert plus a calculated end date after your deadline. Fix these first.
- Stuck and over budget: time in status above your threshold plus negative budget remaining. These cost money every day they wait.
- One customer at risk: a scope condition on your Customer field plus a delivery alert. That's the list to review before the account call.
Formulas make combinations even more flexible. For example, DATEDIF(this.duedate, TODAY(), "D") returns how many days a work item is past its due date. Add it as a column, filter for anything over five days, and you have a "seriously overdue" view that ignores work that's only a day late.
Formulas can also aggregate up your hierarchy. SUM#children { this.storyPoints } totals story points from each item's direct children, so you can filter for parents carrying more points than a team can take on.
Act on what you find
A risk view is only useful if it leads to a decision. Portfolio keeps the next step close:
- Fix it in place. Edit work items inline or in bulk, or open the capacity plan from an alert to reschedule and reassign. Changes sync straight back to Jira.
- Make it obvious. Use conditional formatting to colour fields or whole rows, so at-risk work stands out even when no filter is applied.
- Share it. Give stakeholders Viewer or Editor access, share a link, or export the table to Excel or CSV.
- Put it on a dashboard. Save the Table view and add it to a Jira dashboard with the Portfolio gadget, so the risk list is always visible.
- Ask about it. If your Jira plan includes Rovo, the Portfolio Insights Rovo agent can tell you which work in a project has a capacity or delivery alert, and suggest how to resolve it.
Works on the Jira plan you already have
Portfolio by HeroCoders' portfolio views and capacity planning work on Jira Free and Standard as well as Premium and Enterprise. You don't need to move your whole site up a tier to see who's overbooked or which initiatives are drifting. Advanced filtering, scopes, alerts and formulas are part of the Table view, and the Advanced edition adds actual cost and revenue, resource requests and the Gantt chart.
If you're coming from Jira Plans, see how the two compare in Portfolio by HeroCoders vs Jira Plans: Complete Feature Comparison.
FAQ
Can you filter Jira work by capacity or delivery risk?
Yes, with Portfolio by HeroCoders. Its advanced filtering includes capacity alerts, which flag work assigned to overbooked people, and delivery alerts, which flag parents whose children end after them or that are past their dates with no progress.
Can I filter a Jira portfolio on a custom formula?
Yes. Add a formula column in Portfolio by HeroCoders, such as days overdue or budget remaining, and filter on its value like any other field.
Can a Portfolio scope use Jira custom fields?
Yes, scopes can combine projects, work item types, status categories, filtered with Jira and custom fields or you can use a JQL to define them.
How do I find work that's stuck in a status?
Add the Time in Status column, choose the statuses to track, and filter for anything above your threshold.
Do I need Jira Premium to use these filters?
No. Portfolio by HeroCoders' portfolio views and capacity planning work on Jira Free, Standard, Premium and Enterprise.
Does filtering on actual cost need Clockwork Pro?
Yes. Planned revenue and cost work in every Portfolio edition. Actual cost and revenue come from Clockwork Pro worklogs and need the Portfolio Advanced edition.
See your risks before your stakeholders do
Portfolio by HeroCoders filters your whole Jira portfolio on the signals that matter: who's overbooked, what's drifting, what's stuck and what's over budget. Save the view once and check it every week.
