Cannot filter out issues where custom date field is bigger than exact date or EMPTY

Dagmara_Rosińska

Hello,

I have a problem with below query:

project = ABC AND (labels not in (test) OR labels is EMPTY) AND (created >= "2018/04/23" AND ("Baseline Start Date" >= "2018/04/23" OR "Baseline Start Date" is EMPTY)) AND component not in ABC

It should return issues where:

1. "Baseline Start Date" (custom field of date type) is EMPTY.

2. Where "Baseline Start Date" (custom field of date type) is "bigger" than 2018-04-23.

 

Problem: It returns issues created after "2018/04/23" with "Baseline Start Date" with value before "2018/04/23" instead of eliminating those. Jira version: JIRA Project Management Software (v7.5.3).

 

Any solution? Thank you,

Dagmara

Andy Heinzer

Can you replicate this problem of these unexpected issues being returned if you ran a more simple JQL query such as just

Project=ABC and "Baseline Start Date" >= "2018/04/23"

 I suspect that you can.  And if you can, I would be interested to see the values for that specific Baseline Start Date field in those issues?  Are they by chance also including only issues that have a start date of 2018/04/22 ?

If so, it's possible that you might be seeing this problem because of the way that Jira will store date values.  Even for fields like this that are only a date, Jira can store this data in a date AND time format when it comes to the SQL database where this information is stored.   This usually is not a problem when all your Jira users are in the same timezone, but when the Jira system time is even 1 hour ahead of your own timezone, values to these date fields can appear to lose 1 hour (and in turn 1 day) when Jira tries to represent this data to your profile.  There is a documented bug on this in https://jira.atlassian.com/browse/JSWSERVER-12880

The current work-around is to set your timezone to be the same as the Jira system timezone to avoid this problem for the time being.

 

However with the information I have right now, this is largely a hunch that this is the problem.  I might be way off.  If so, please let me know some more details about the values you see in that other query, and perhaps let me know if this custom field is a date field, text field, or a date/time field in Jira.

Thanks

Andy