Date/Time custom field with unexpected behavior in JQL

[Durell Demartini]

Hello,

We have a custom field of type Date/Time called "Planned Start Date." I'm trying to write a JQL statement that will include all issues that meet the criteria of having a "Planned Start Date" that will occur within the next 2 hours. When I start from a Basic search, select the custom field and select "Within the last 2 hours," the Advanced JQL looks like this: "Planned Start Date" >= -2h 

However, the JQL is also including issues that have a Planned Start Date beyond the next two hours as well as including issues where the Planned Start Date has already passed. Is there a more precise way to write the JQL? 

Thanks in advance for your assistance.

[Trudy P Claspill · Accepted solution]

Hello @Durell Demartini 

This statement:

"Planned Start Date" >= -2h 

...is interpreted as "give me any issue where the Planned Start Date is later than 2 hours before now.

If "now" is 2024-01-04 16:00 then issues will be included if their Planned Start Date is in the future with regard to that date time. That means they have a Planned Start Date of any time after 14:00 2024-01-04, including items that have a Planned Start Date later than now (i.e. 18:00 2024-01-04, or any time on any future date after today).

If you want the items that have a Planned Start Date within only the past 2 hours then you need this

"Planned Start Date" >= -2h  and "Planned Start Date <= now()

[Durell Demartini]

Hi @Trudy P Claspill thank you for the input. I tried your exact suggestion, and for some reason it didn't quite work as expected. However, I modified it a bit and it works exactly as we expect when I use this:  "Planned Start Date" >= now() AND "Planned Start Date" <= 2h

Thanks very much :)

[Trudy P Claspill]

Your modification would give you all issues due within the next two hours.

The option you posted about in your message was finding the issues "Within the last 2 hours", which means the two hours before now. My solution matches that scenario.