Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,644,556
Community Members
 
Community Events
196
Community Groups

Filter Issues by Due Date

I have three filters on a dashboard that list tasks due within 1d, 1w and 2w respectively; however using the JQL 'duedate <= 1d' etc means that an issue due within 1d will appear in all three filtered lists.

As issues cross filter date boundaries I want them to appear in only one of the three lists. So if an issue is due within one day I only want it to show in the filter that says duedate <=1 and not in the one that says duedate <= 1w or duedate <=2w (even though technically the condition is met in all cases so JIRA is displaying the correct logical result).

I can't quite work out the syntax required to filter issues between dates in this way and I may be asking for the impossible - anyone else managed to crack this or am I the only one with this particular use case?

Any assistance appreciated.

Andy

3 answers

1 accepted

8 votes
Answer accepted
Marc Minten _EVS_
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
Mar 09, 2016

Your filter for 1w should say : duedate <=1w and duedate > 1

Your filter for 2w should say : duedate <=2w and duedate > 1w

 

Thanks Marc - absolutely nailed it - spot on

Andy

Does this filter include due dates for sub-tasks? 

Hi all, i have tried it this way 

status="In Progress" AND status != Closed and due <=1w and due >1

however the system filters some random issues and overdue as well from 2018.

Is this the right way, please?

How would you query filters for issues without a due date for more than a day in jira. 

 

To translate, "A jira issue created and due date field is EMPTY for more than 1 day"

We are looking to pull up issues which are created and after a day, the report will show if the due date has been left empty or not added after 1 day.

 

Thanks

Dave Liao
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Oct 07, 2020

@Henry Bada - for the record (and I'm sure you figured it out by now!), the JQL to show Jira issues created more than a day ago, and where the Due Date field is empty is:

created <= -1d and duedate is EMPTY order by created DESC

Hope that helps others who have the same question!

I am curious how to query if the DUE date is not filled in, we don't do this until we're ready to commit to the work but need to see the work presently in the backlog.   

duedate is EMPTY or due is EMPTY should do the trick!

Like Dave Liao likes this

Thank you William. That was just what I needed.   Bob.

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events