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 to perform a punctual extraction of expiring tasks and sub-tasks?

Alessandro Pappalardo_xizi8o

Having tasks and sub tasks in which in some there is only the end date and in others there is the “end date” and another field related to the “rescheduled end date”, how do I extract only those that have a “rescheduled end date” expiring in the next 60d and therefore should not be considered the “end date”. and those that do not have a “rescheduled end date” but that have an expiring “end date” always in the next 60d?

I used this query:

resolution = Unresolved AND ("rescheduled end date" <= 60d OR "rescheduled end date " is EMPTY AND "end date" <= 60d)

Accepted answers

Kristopher Perez

I would try an extra set of parenthesis in here:

Original Query:

resolution = Unresolved AND ("rescheduled end date" <= 60d OR "rescheduled end date " is EMPTY AND "end date" <= 60d)

Revised Query:

resolution = Unresolved AND ("rescheduled end date" <= 60d OR ("rescheduled end date " is EMPTY AND "end date" <= 60d))

See if that get's you closer.

Kris

All comments

Kristopher Perez

I would try an extra set of parenthesis in here:

Original Query:

resolution = Unresolved AND ("rescheduled end date" <= 60d OR "rescheduled end date " is EMPTY AND "end date" <= 60d)

Revised Query:

resolution = Unresolved AND ("rescheduled end date" <= 60d OR ("rescheduled end date " is EMPTY AND "end date" <= 60d))

See if that get's you closer.

Kris

Alessandro Pappalardo_xizi8o

Thanks Kris for the answer, unfortunately even trying your query I get the same incomplete results

Kristopher Perez

Are you sure that there are issues which meet the criteria?

The next thing I would do to troubleshoot, is create a filter with a few examples of parents and sub tasks that you expect to see, using the following:

Key in (KEY-1, KEY-2, …. KEY-10)

Then, once the filter is saved, make sure to expose all of the custom fields you are referencing in your attempted query. This is just to make sure that you are seeing values in each of the issues, and to make sure you are using the proper names for each of the custom fields. Sometimes custom fields may be sharing the same name, but with a different casing, and that would impact your query results if you are using the wrong version of the correct custom field name.

Share a few screenshots so we can see where you have gotten and maybe there will be some nuance that we are both missing.

Kris

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-cloud