Our team uses Jira to manage tasks and track project progress, but one challenge is identifying bottlenecks early. A task can stay in "In Progress" for several days without anyone noticing that it's stuck. By the time it appears in a project status report, the delay may already affect the delivery timeline. I'm curious how other teams handle this: * Do you track how long issues remain in each workflow status? * How do you identify tasks that haven't moved for several days? * Do you use Jira dashboards, reports, automation or third-party apps for bottleneck detection? * How do project managers get a quick view of overdue, blocked and upcoming work across multiple projects? I'd especially like to hear what works for teams managing several projects simultaneously.

nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

How do you identify bottlenecks in Jira before they start delaying project delivery?

Abhishek P

Our team uses Jira to manage tasks and track project progress, but one challenge is identifying bottlenecks early.

A task can stay in "In Progress" for several days without anyone noticing that it's stuck. By the time it appears in a project status report, the delay may already affect the delivery timeline.

I'm curious how other teams handle this:

Do you track how long issues remain in each workflow status?
How do you identify tasks that haven't moved for several days?
Do you use Jira dashboards, reports, automation or third-party apps for bottleneck detection?
How do project managers get a quick view of overdue, blocked and upcoming work across multiple projects?

I'd especially like to hear what works for teams managing several projects simultaneously.

Accepted answers

Habib__Plugio__

Hi Abhishek,

Most of this is covered natively if you build it on one saved filter.

Finding stuck work. Jira keeps a statusCategoryChangedDate field. It records the last time an issue moved between To Do, In Progress and Done. statusCategory = "In Progress" AND statusCategoryChangedDate <= -5d lists everything that has sat in the in-progress band for 5+ days. For a single status use history instead: status = "In Review" AND NOT status CHANGED AFTER -3d. Save it as a filter. Everything below reads from it.

Alerting before the report. Automation → Scheduled trigger, daily. Tick "Run a JQL search" with that filter and send a Slack/Teams message or an email per issue to the assignee. That is the part that catches it on day 3 instead of in the status meeting.

On the board. Company-managed boards have Board settings → Card layout → "Days in column". Cards get age dots, so the standup sees it without a query.

Time per status. Control Chart and Cumulative Flow Diagram under board Reports show average time in each status and where the bands widen. They are historical. Use them to find the chronic bottleneck status, not for today's alerts. There is no native per-issue "time in status" field.

Cross-project view. One dashboard, every filter scoped with project in (A, B, C), and a Filter Results gadget each for overdue (duedate < startOfDay() AND statusCategory != Done), blocked (Flagged = Impediment), due this week (duedate >= startOfDay() AND duedate <= endOfWeek()) and the stale filter above. Share the dashboard with the PM group.

If four separate gadgets feel too fragmented, one possible step up is a dashboard app. Disclaimer: I work for Plugio, the vendor of Plugio Suite. It puts the same JQL on one page: counts that turn red above a threshold, and the stale list with the status-changed date as a column. It does not do per-status time history, so the Control Chart stays the tool for that.

All comments

Habib__Plugio__

Hi Abhishek,

Most of this is covered natively if you build it on one saved filter.

On the board. Company-managed boards have Board settings → Card layout → "Days in column". Cards get age dots, so the standup sees it without a query.

Tomislav Tobijas

Hi @Abhishek P ,

From experience, we tend to create some kind of automation for these cases. Basically, the automation calculates how long a specific work item has stalled in the same status. 👀 Then, based on that data, the team decides or just checks whether the process needs to be updated 🤔

One more thing you could try (if you're asking for yourself/your team) is to ask Rovo or another AI through MCP to pull this data directly from a specific pool of work items. Automation is 'robust' but follows the same principle, while AI can probably give you additional context 💡

Cheers,
Tobi

Lucija Maric

Hi @Abhishek P,

I think the suggestions already shared cover most of the key points, so I'd just like to add one more, perhaps less obvious, option.

You could create a filter with a JQL query to identify items that have been sitting in a particular status without any updates for a defined period. For example:

status = "In Progress" AND updated <= -3d

You can then subscribe to that filter yourself and include other interested team members in the subscription. Jira will periodically send an email with all items matching the criteria, making it an easy way to spot tasks that might need attention before they turn into bigger bottlenecks.

It's a simple solution, but it might still come in handy. 🙂

Khrystyna_Dzhus_SaaSJet_

Hi @Abhishek P,

The native options suggested above are a good starting point: Days in column helps flag aging work on the board, while saved filters and scheduled automation can bring work items needing attention to your team’s notice.

Jira records status changes in work item history, but getting a report of time spent in each status requires additional calculation or tooling. For reporting across projects, a Marketplace app such as Time in Status by SaaSJet is another option. Disclosure: I’m part of the SaaSJet team.

You can build a report from a JQL query or saved filter covering multiple projects, group results by project, sort or filter status durations to find long-running work items. A work schedule excludes nights and weekends, and the Accurate Time in Status gadget displays the results on a Jira dashboard.

A custom field can also show time in the current status directly on board cards and make that value available in JQL. With a work schedule applied, you can use it to identify work items exceeding your working-time threshold and configure scheduled automation to notify the assignee.

Hope this helps!

Birkan Yildiz _OBSS_

Hi @Abhishek P,

Identifying bottlenecks before they impact delivery timelines comes down to moving from reactive reporting to proactive workflow monitoring. Standard Jira board views show what is currently assigned, but they don't easily highlight where work is silently sitting still.

Here is how high-performing teams handle this:

Track Status Durations (Time in Status): Instead of waiting for cycle time reports after work is completed, measure the exact duration issues spend in specific active states (e.g., In Progress, In Review, Waiting for QA).
Automate Stalled-Work Alerts: Set up threshold alerts (e.g., automated pings via email, Slack, or MS Teams when an issue spends >3–5 days in an active status without moving) so PMs don't have to scan boards manually.
Build Multi-Project Dashboard Gadgets: Aggregate status duration metrics across multiple projects on a central Jira dashboard to give project managers a single-pane view of overdue, blocked, and stalled work.

How to do this with Timepiece

If you are open to using a Marketplace app, Timepiece - Time in Status for Jira is designed specifically to solve this visibility problem:

Status Duration Reports: Instantly visualize how long work items spend in every workflow state across single or multiple projects.

Scheduled Reports & Alarms: Automatically send notifications to Slack, Teams, or Email the moment an issue exceeds a stalled-time threshold.
Custom Working Calendars: Exclude weekends, nights, and public holidays so your bottleneck data reflects true working hours instead of continuous 24/7 calendar time.
Interactive Dashboard Gadgets: Pin live reports to your Jira dashboard. PMs can click on any aggregate bar or number to instantly drill down and view the exact tickets behind the delay.

For a step-by-step walkthrough on structuring your dashboard for bottleneck detection, check this article out: Where is Work Waiting?

Full disclosure: I am on the team that develops Timepiece. Hope this helps you catch bottlenecks early and keep your projects on schedule!

Lukas Maczejka _Appfire_

Hello @Abhishek P,

The native combination of a statusCategoryChangedDate filter, a scheduled automation rule and a shared dashboard covers the "what's stuck right now" part well. There is one gap though, as @Habib__Plugio__ pointed out: Jira has no per-work-item "time in status" value, so it's hard to see how long each item spent in each status, or to sort a cross-project list by it.

If you're open to solutions from the Atlassian Marketplace, JXL for Jira is one option. It gives you a spreadsheet-style view (a "sheet") over any JQL scope, so one sheet can span all your projects. For bottlenecks, the useful parts are:

History columns such as Time in status, Time since status changed and Time between statuses. You pick the statuses and how repeated visits count (total, latest, average, median, longest).
Work calendars, so durations reflect working hours rather than nights and weekends.
Sorting and filtering on those columns, e.g. "In Progress for more than 3 days".
Conditional formatting to color rows that cross a threshold, next to columns like due date and Flagged.
Grouping by project, assignee or status, so a PM can see where work piles up.

Filtering by status and time since status change

I'd still keep the scheduled automation for the daily nudge to assignees and use the sheet for the overview and the trend.

Disclosure: I'm on the team that builds JXL.

Hope this helps,
Lukas

Danut M _StonikByte_

Hi @Abhishek P,

Jira dashboards can show how long an issue has stayed in a column, which you can activate in board settings, but they don't provide a way to highlight issues that have been there for too long.

In my opinion, the best way to identify such issues or tasks is to use a WIP Aging Chart, which can highlight issues that have spent too much time in a workflow status or board column.

Unfortunately, Jira doesn't offer a built-in WIP Aging Chart, but if you're willing to try an app, I recommend taking a look at the WIP Run Chart gadget included in our Great Gadgets plugin.

This gadget lets you display issues from a filter or board, grouped by workflow status or board column, and by their age on vertical oY axis (time spent in the current status or column, or time since creation, depending on your configuration).

It also allows you to display percentiles or set a custom threshold to easily identify issues that are taking too long. The ones over the threshold (breaches) will be displayed in red color, but you should also pay attention to the ones that are close to the threshold, because they are about to become breaches.

Hovering over an issue immediately displays its details, while the gadget's Data tab highlights threshold breaches in red.

The same app also offers many other useful gadgets, such as the Control Chart, Cycle Time Trend, and Time in Status gadgets, which could be particularly helpful for your needs.

Hope this helps

Danut.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

trello

jira-software

jira-cloud

jira-service-management