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

remainingEstimate and JQL

Randy O'Neal

I thought it would be clever to have a quick filter on my team's story board to look for issues that had been accepted but still had time remaining on them. So, I wrote this nifty little quick filter... but it doesn't work (and I'm struggling to understand why it doesn't work):

Status = Accepted AND remainingEstimate > 0m

If I add a couple of items and put the following into advanced search, I get 45 issues across the org across all sprints:

Status = Accepted AND remainingEstimate > 0m order by Project DESC

I should say I have 2 issues in my current sprint which have been accepted, each have 5 minutes remaining. Neither show up in the advanced search results above. We do have time tracking enabled.

Any ideas why my query won't find my 2 issues, but the same core JQL finds countless other issues across my organization/across all sprints?

Accepted answers

Nic Brough -Adaptavist-

Do the issues appear on your board before you apply the quick filter?

All comments

Jack Brickey

The two issues you speak of have a status of acceptance and the remaining time is non zero then I would expect them to show up to be honest.

What does accepted represent? Is that the final status like done? If your ultimate goal is to ensure remaining time is always zero for any issue that is transitioned to accepted/done status then consider using a post function on the transition.

Nic Brough -Adaptavist-

Do the issues appear on your board before you apply the quick filter?

Randy O'Neal

Accepted is our final status; Done represents everything completed but not yet accepted by our Product Owner. Upon final review, the PO will accept the issue.

The #1 concern is with our integration with GITHUB, there are some final merges to production which need to occur only following acceptance; this results in subtasks still having time left on them until the final production merges have taken place, at which time the developer zeroes out his/her remaining time on the subtask. This is why I can't set automation to zero out any remaining time when transitioning to Accepted.

I need/want to see these, and a board quick filter seemed the best way to accomplish this... but I can't seem to get it to work.

Randy O'Neal

Yes, they do... and they show up if I remove the "AND remainingEstimate > 0m" from the JQL. I also tried substituting != 0 for the > with no changes in results.

Nic Brough -Adaptavist-

Ok, so assuming that your quick-filter is what you said before ( Status = Accepted AND remainingEstimate > 0m ), can you tell us what the board filter is?

Randy O'Neal

Board filter is as follows:

project = RACE AND issuetype in ("Automation Story", Bug, Epic, "Implementation Plan", "QA Story", Story, "Team Admin Support", "Test Execution") ORDER BY Rank ASC

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