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

JIRA filter on exact date

Hi there,

I just stumbled upon a problem which I haven't encountered before regarding filtering JIRA issues via JQL. Usually I like filtering for a specific period of time (i.e. issue due in the next 7 days etc.) Now a customer created a filter like

project = 'XYZ' and dueDate = '2012-02-20'

The problem is that no issues are being displayed even if they exist.

Am I missing something here?

Thx for your help


P.S. date values are set to default

4 answers

1 accepted

6 votes
Answer accepted
Mizan Ali Sayed Mar 01, 2012

Hi ,

Which version of Jira are you using ? for 4.4.4 you need to use YYYY//MM/DD format for duedate . for example duedate="2012/03/01" . dont forget the quotes :)

Andrew Frayling Mar 01, 2012

Hi Christian,

Single quotes, double quotes, /'s, -'s should all work (tested on local JIRA 5 instance). Stab in the dark, could it be an indexing problem? Is it possible to re-index and try again?


Hi, I'm usig JIRA 5.0 but we've tested the query in older version as well with no results...Single quotes, double quotes. I'll keep trying and keep u informed

I have tried re-indexig with no results. hat I wanted (as an example) are the issues created on Feb 27.

No results for this query:

createdDate = "2012-02-27"

All the relevant issues after this query:

createdDate >= "2012-02-27" and createdDate < "2012-02-28"

Like István Siroki likes this
Jobin Kuruvilla [Go2Group] Community Leader Mar 01, 2012

And we thought you were asking bout dueDate! dueDate and createdDate are different.

dueDate only stores the date and hence you can use = in the JQL to search issues due on a date. createdDate stores time as well and hence = will work only if you include the exact time. You need to use > <= symbols as you have done above to get issues created on a date.

Thank you guys. In SQL I would need something like a datepart to get the date. So now I know that "createdDate" is a timestamp... I thought of that before and tried to test the query against dueDate which didn't produce any results either. THAT must have been an indexing problem and I thought it was a general probem I was facing!



1 vote
Igor Rodrigues Feb 21, 2014

To restrict your search by a specific date you need to follow this:

DD = The actual date you want to have results for

DD+1 = The actual date you want + 1

Obviously, if DD is 31, for instance, DD+1 will be 1 and you'll need to update the MM to MM+1, same for YYYY - i.e.: Date you want: 2014-12-31; 2nd date will be: 2015-01-01

createdDate >= "YYYY-MM-DD" and createdDate < "YYYY-MM-DD+1"

0 votes
Luis Ribeiro Feb 25, 2014

Hi Cristian,

Can i suggest :

Thers a function "ExecuteQuery()" that lets you run a SQL statement.


0 votes
Ahmed Gehad Apr 10, 2019

You can send the value for field 'createdDate' in formats such as: 'yyyy/MM/dd HH:mm', 'yyyy-MM-dd HH:mm', 'yyyy/MM/dd', 'yyyy-MM-dd', or a period format e.g. '-5d', '4w 2d'.

Suggest an answer

Log in or Sign up to answer
This widget could not be displayed.
This widget could not be displayed.
Community showcase
Published in Next-gen

Introducing subtasks for breaking down work in next-gen projects

Teams break work down in order to help simplify complex tasks. This is often done iteratively, with tasks being broken down into smaller tasks and so on until the work is accurately captured in well-...

12,583 views 63 59
Read article

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