See how Timesheets brings estimated vs actual time into Jira with real-time reporting, dashboards, and portfolio rollups built for delivery teams.
Overdue task tracking
Structure PPM brings overdue task tracking into Jira so teams can plan, report, and act on the same data.
Every overdue task is a signal someone failed to send. The due date passed, the system noticed, and unless the dashboard is built to surface it, the slip stays buried in a backlog of 4,000 issues. By the time a status report flags it, the dependent work is already at risk. Tracking overdue work is what turns those silent slips into early warnings, across every project in the portfolio at once.
What is overdue task tracking?
Overdue task tracking is the practice of identifying, surfacing, and reporting on Jira issues whose due date has passed without resolution. At a single-project scale it is a filter. At portfolio scale it is a discipline – a way to detect schedule drift across hundreds of projects before it compounds into missed releases or broken commitments.
Mature tracking does three things. It surfaces every overdue issue across an organization in one view, regardless of which project or board owns it. It scores severity – an issue two days late is not the same as one two months late – so attention goes to the slips that matter. And it ties late work to the higher-level items it belongs to, so a portfolio leader sees not just that 80 tasks are late, but that 20 of them ladder up to the same critical initiative.
Benefits
Early-warning signal. Schedule drift surfaces in days, not in the next steering committee deck.
Portfolio-wide reach. One view spans every project and team, so cross-project slips are not lost in single-project filters.
Severity scoring. Days late, blocked dependencies, and parent-issue impact get weighted, so the worst slips rise to the top.
Accountability without micromanagement. Owners see their own late lists; leaders see aggregate trends, not individual call-outs.
How to put it into practice
Start with the criteria that count as overdue in your environment. Most teams treat a passed due date as the trigger, but some weight by sprint commitment, others by milestone date, and others by SLA. Align the definition before the report goes live, otherwise the data will spark debate instead of action.
Build the view at the portfolio level. A single project's late list is a daily standup tool. The portfolio version is what PMOs and program leaders need – every late task, grouped by program, sponsor, or business unit, sorted by severity. The view should answer "where is schedule drift accumulating fastest?" in one glance.
Pair the view with a routine. Late lists do not fix themselves. Most organizations review them weekly at a program level and monthly at a portfolio level, with explicit ownership for resolution. The discipline matters more than the tool.
Managing it with Tempo Structure PPM
Structure PPM is built on the idea that Jira's flat project model breaks down at portfolio scale. Custom hierarchies let teams organize work the way the business thinks about it – initiative, program, project, epic, story – with late tasks visible at every level of the tree.
Hierarchies make portfolio-wide tracking practical. Instead of running 30 project-scoped filters and reconciling them in a spreadsheet, a Structure view rolls every late task in the organization into one navigable hierarchy. Collapse the tree for a high-level count of late items per program. Expand it to drill into the specific tickets blocking a release.
Generators automate hierarchy population. Define the rule once – every issue in projects A, B, and C, grouped by epic, then by component – and Structure pulls in matching issues continuously. New late tasks appear in the right place in the tree without manual rebuilds.
Formulas turn the hierarchy into a reporting surface. A formula can flag any issue with a due date in the past, count late children for each parent, sum the days late at the program level, or compute a severity score that combines days late with priority. The Structure Formula Assistant, a Rovo agent, generates these formulas from natural language for teams that do not want to learn Structure's formula syntax.
Pair Structure with Custom Charts for Jira to render the same data as a portfolio dashboard – a stacked bar chart of late counts per program is one view away.
Structure PPM
Align your entire organization
Manage products, projects, and programs in a single spreadsheet-like view. By providing a clear, real-time view of project progress and resource allocation, Structure helps teams meet deadlines and adapt swiftly to changing priorities.
Start a Free TrialFrequently Asked Questions
Couldn't find what you need?Go to our documentation
Native Jira treats an issue as overdue when its due date is in the past and its status is not resolved. The native filter is project-scoped and binary. Tools like Tempo Structure PPM extend this with hierarchical roll-ups and formula-based severity scoring, which is what most portfolio teams need beyond the basic filter.
Yes – this is one of the primary reasons portfolio teams adopt Structure PPM. A single Structure can pull issues from any number of Jira projects, organized by hierarchy, with overdue items surfaced consistently across the whole tree. No JQL gymnastics, no per-project dashboards, no spreadsheet reconciliation.
Generators automatically populate a Structure hierarchy based on rules – issues from selected projects, grouped by epic, filtered by JQL, and so on. For overdue tracking, this means a portfolio-wide view that updates itself as new issues are created or pass their due date, without anyone manually re-curating the report.
Structure formulas can score and flag overdue items, and Custom Charts dashboards can surface them visually for review meetings. For automated notifications and escalation workflows, customers typically pair Structure with Jira automation rules, which can fire on the same conditions a Structure formula evaluates. Together they cover both visibility and active escalation.
Related articles
Not every delayed dependency is a program risk. Learn the 4 conditions that trigger escalation, and spot exposure before it reaches leadership.
Learn how Financial Manager delivers project revenue reporting for Jira teams — real-time reporting, dashboards, and portfolio rollups in one view.
Visualize cross-team dependencies in Jira. Spot risk before it becomes delay with Gantt Charts for Structure PPM.
Connect delivery, capacity, and financial data in real time with Tempo's Custom Charts, Structure PPM, and BI Connectors.
Plan, balance, and forecast portfolio capacity with Tempo's Capacity Planner and Structure PPM – built for enterprise PMOs.
Learn how lead time vs cycle time reveals where work slows down, and why tracking both is essential for reliable delivery and strategic forecasting.
Plan sprints inside a longer schedule. Connect agile execution to portfolio delivery dates with Gantt Charts for Structure PPM.
Gantt Charts for Structure PPM slice-based configurations allow you to create custom rules for specific sets of issues.
