It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Filter for Past Due Actions

I would like to develop a filter to show all past due actions for the current date.

 

Example:

1. Actions which should have started but have not.

2. Actions which should have ended but have not.

1 answer

Hi Bruce,

welcome to the community! How experienced are you using JQL? Because in general I'd say we can build the needed filter for you but we're lacking information here.

  • How does "actions which should have ended" translate to the way your Jira is configured and how you're using it? Are you using resolutions? Are you just using a specific status?
  • How does "actions which should have started" translate to the way your Jira is configured and how you're using it?
  • are you using the Due Date system field or any other field to determine what is past due and what not?

I also recommend reading the following articles and documentation:

Best, Max

Max,

 

Thanks for the response, below are responses to your questions.

 

  • How does "actions which should have ended" translate to the way your Jira is configured and how you're using it? Are you using resolutions? Are you just a specific status?
    • Response - We are using "To Do," "Working," and "Resolved."
  • How does "actions which should have started" translate to the way your Jira is configured and how you're using it? are you using the Due Date system field or any other field to determine what is past due and what not?
    • Response - We are using Start and End dates. Basically, the Start date is when we plan to start the action or Process Improvement event. 

Hey,

so from what you are saying the following query could be satisfying but you will have to check it yourself and make sure to reference the correct fields. The advanced issue search offers a great auto-complete feature to help you. It's just very important to use parentheses to glue the logical groups together 

(status = "To Do" AND "Start date" < now()) OR (status != Resolved AND "End date" <= now())

The first half translates to "Every issue in the status "To Do" with a start date earlier than now". That seems correct, right? 

And the second half translates to "Every issue which status is not equal to "Resolved" and with an end date earlier or equal to now.

Best, Max

Like Bruce Thomas likes this

Max,

 

This is what I tried but it's not working...

 

project in (PSNS, PSNSPLTEAM, SEA4X, NIP) AND issuetype in (Development, Documentation, Epic, Event, Idea, Improvement, Prototype, Story, Task) AND status in ( "To Do" AND "Start date" < now()) OR (status != Resolved AND "End date" <= now()) AND assignee in (membersOf("psns1040-psns-c/1040 team"))

As said parentheses are very important. Currently, the search will be interpreted as:

project in (PSNS, PSNSPLTEAM, SEA4X, NIP) AND issuetype in (Development, Documentation, Epic, Event, Idea, Improvement, Prototype, Story, Task) AND status in ( "To Do" AND "Start date" < now()) 

OR

(status != Resolved AND "End date" <= now()) AND assignee in (membersOf("psns1040-psns-c/1040 team"))

 

And status in ( "To Do" AND "Start date" < now())  is not valid JQL and you should get an error. :)

(project in (PSNS, PSNSPLTEAM, SEA4X, NIP) AND issuetype in (Development, Documentation, Epic, Event, Idea, Improvement, Prototype, Story, Task) AND status in "To Do" AND "Start date" < now()) OR (project in (PSNS, PSNSPLTEAM, SEA4X, NIP) AND issuetype in (Development, Documentation, Epic, Event, Idea, Improvement, Prototype, Story, Task) AND status != Resolved AND "End date" <= now() AND assignee in membersOf("psns1040-psns-c/1040 team"))

Please try that query.

Got this respionse: Operator 'in' does not support the non-list value '"To Do"' for field 'status'.

Oh yes, I wrote status = "To Do" initially and copied the mistake over from your last expression. So try that or write status in ("To Do"). And again try a) writing the expression piece py piece using auto-complete to fill in correct values and to understand how the different parts work and b) consider having a look at the documentation as well where everything is described. JQL is like the best-documented feature of Jira ;) 

By the way, if the assignee piece is relevant for the first half too, don't forget to add it there as well!

Got it to work, thanks for the advice. 

 

project in (PSNS, PSNSPLTEAM) AND issuetype in (Epic, Improvement, Prototype, Task) AND status in ("To Do") AND "Start date" < now() AND "End date" <= now() AND assignee in membersOf("psns1040-psns-c/1040 team")

Happy to hear that Bruce!

Hey Bruce,

just checking back with you. Please consider accepting answers in the community if they provide a solution to your question so other users can better identify answered questions around here. Thanks a lot! :)

Best, Max 

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted in Jira

Demo Den Ep. 7: New Jira Cloud Reports

Learn how to use two new reports for next-gen projects in Jira Cloud:  Cumulative flow diagram and Sprint burndown chart. Ivan Teong, Product Manager, Jira Software, demos the Cumulative ...

303 views 1 3
Join discussion

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you