nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Bug on filters with operator <= "date"

Felipe de Almeida Toigo

I have a filter that should show me the tasks created between 10/08/2025 and 10/21/2025.
In this case the filter is showing 2 tasks (CP-7603 and CP-7580).

But there is a 3rd task that should be presented (CP-7617) that was created on October 21st in the morning.

So probably this is a bug, the filter is not considering the "<=" operator, and considering just the "<".

How can I report this bug?

Screenshot 2025-10-27 at 10.28.09.png

Accepted answers

Gor Greyan

Hi @Felipe de Almeida Toigo

Yes, on my side, it is also working like that.

There is no difference; using < or <=, it returns the same result.

So, if I needed to include also 21, I put it like this <= 2025-10-22.

I found this, which is reported on 12/Aug/2014 3:27 PM.

https://jira.atlassian.com/browse/JRACLOUD-39509

John Funk

Hi Felipe - This is probably a timing issue. You should include one day later in your final query.

All comments

Jeroen Poismans

Hi,

I don't think this is a bug. You filter says:

... AND created <= "2025-10-21"

I assume that this will translate to

... AND created <= "2025-10-21 00:00:00"

Your issue was created at 8:07 AM so it will fall outside that JQL. You will get the work items you want by doing this:

... AND created < "2025-10-22"

Gor Greyan

John Funk

Hi Felipe - This is probably a timing issue. You should include one day later in your final query.

Marc -Devoteam-

Hi @Felipe de Almeida Toigo

@John Funk is correct here.

Measurement is the day mentioned and the operator, if you want to include the 21st, you need to use the operator <= or < 2025-10-22"

Felipe de Almeida Toigo

Ok, solutions provided in this post helped me with the correct expected result.

But as a QA, I need to consider that a bug.
Because "<=" means "minor or equal to".

So if is minor or equal to, condition to return the results is:

Timings between 00:00 and 23:59 (or 11:59PM) are still 21-10-2025. So if a task is created between this time, it should be still valid and returning the correct value.

You can think about SQL Server for an example. The same query would return the result as expected.

Anyways, I got in touch with my company support to open a ticket on atlassian to report this.

Felipe de Almeida Toigo

Hey @Gor Greyan , I agree with you.

Since I am a QA, I think that way:

Bug description: a task was created in 21/10/2025 8AM with identifier XX-1234.

Used the filter:

project = XX

created <= 21/10/2025

Expected result: task XX-1234 should be showed as filter result.

Actual result: operator "<=" does not returns task XX-1234. In fact, the operator "<=" is behaving just as "<"

Gor Greyan

Hi @Felipe de Almeida Toigo

Yes, I also consider it a bug, as in our mathematical class we learn that <= is less than or equal So the date, which is equal to the date we wrote, should be included.

Hope, one day it will be fixed.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud