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; } } }

Use Story Point Estimates to identify 'at risk' issues

Calahan Larson_6wfymc

I am trying to use JQL queries to compare the time that a ticket has been 'active' against its story point estimate. Is this possible with OTB JIRA?

I would like to quickly identify issues that haven't been updated within a certain amount of time relative to their point estimate.

Accepted answers

Kristján Geir Mathiesen

Hi @Calahan Larson and welcome to the Community

You will need to use Atlassian Analytics (which is in Beta now) in order to find out how long a ticket has been in a certain status or a 3rd party app. It is not possible with OTB Jira JQL search/filter.

HTH,
KGM

All comments

Kristján Geir Mathiesen

Hi @Calahan Larson and welcome to the Community

HTH,
KGM

Meghan LaClair

Hi @Calahan Larson

There isn't a native option for this at the moment, but if you are open to 3rd party solutions we have solved for this at minware. We combine Jira ticketing, code sources, and calendar data to provide a global view of the entire SDLC.

Our Sprint Insights report includes a time estimate analysis. We calculate velocity at the task level so that you and your team can understand where your estimates are falling short, and improve your process.

Low Velocity - Time Analysis View for Jira.png

We also provide notifications based on your organizations settings, so that tickets that are behind schedule are automatically pulled out and flagged. This helps you dig in and help remove bottlenecks.

Low Velocity Notification for Jira.png

We offer a free trial, let me know if you would like to check it out!

Disclaimer: Atlassian Marketplace Partner

Maksym Babenko_TypeSwitch_

Hello @Calahan Larson

Yes, you can achieve this in Jira using JQL, though it has some limitations. Jira doesn't support direct calculations with Story Points, but you can use JQL to filter issues based on their last updated time and Story Point values.

A basic JQL query to find issues that haven't been updated in a while could look like this:

storyPoints >= 5 AND updated <= -7d

This finds issues with 5+ Story Points that haven't been updated in the last 7 days.

For a more advanced solution, you might need Jira Automation or a third-party app like Risk Radar for Jira, which helps identify high-risk issues based on multiple factors, including inactivity and complexity.

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-software

jira-software-cloud