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

Issue not resolved after 180 days

salman.khan1

Hi,

I want to create a filter to be used in dashboard for identifying the issues that were created over 180 days ago and are still unresolved. I can do rest of the query need help with the 180 days part

Accepted answers

carlosughini

Hello Salman,

Hope you have been fine.

I would use a JQL similar to what Trudy mentioned, but with a small change related to the resolution so we can search for tickets that don't have a value in the resolution field:

created < startofday(-180d) and resolution is EMPTY

I also recommend checking the pretty good documentation below to understand more about resolutions:

Best practices on using the "Resolution" field

Please give it a try and let me know how it goes.

Kind regards,

Carlos

All comments

Trudy P Claspill

created < startofday(-180d) and statusCategory!=Done

Florian Bonniec

I would use resolution is empty instead statusCategory!=Done

Some times with status are used in may WF and the status catagory is not "right" so resolution seems more accurate.

carlosughini

Hello Salman,

Hope you have been fine.

I would use a JQL similar to what Trudy mentioned, but with a small change related to the resolution so we can search for tickets that don't have a value in the resolution field:

created < startofday(-180d) and resolution is EMPTY

I also recommend checking the pretty good documentation below to understand more about resolutions:

Best practices on using the "Resolution" field

Please give it a try and let me know how it goes.

Kind regards,

Carlos

Welcome!

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

Quick Links

Find more posts tagged with

server

jira-software

jira-software-server