-
Bug
-
Resolution: Timed out
-
Medium
-
2
-
Severity 2 - Major
-
Summary
When using a JQL filter with the resolutiondate field and an OR statement, JIRA does not retrieve the correct results.
Example: "resolutiondate = EMPTY OR resolutiondate >= endOfDay(-2)"
Steps to Reproduce
- Create a sample software project in the instance
- Navigate to Issues > Search for issues
- Enter resolutiondate = EMPTY as the JQL
- Note the amount of results
- Enter resolutiondate >= endOfDay(-2) as the JQL
- Note the amount of results
- Enter resolutiondate = EMPTY OR resolutiondate >= endOfDay(-2) as the JQL
Expected Results
JIRA should show issues from both statements
Actual Results
JIRA only shows the issues from the resolutiondate >= endOfDay(-2) part of the JQL query.
- is duplicated by
-
JRACLOUD-67419 JQL equals to Empty is returning incorrect results when combining with other conditions
-
- Closed
-
- is related to
-
JRACLOUD-67422 latestReleasedVersion() and earliestUnreleasedVersion() functions are not working with the operators "<" and ">".
-
- Closed
-
-
JRACLOUD-67421 Operator '=' does not show any result when used with 'createdDate'
-
- Closed
-
- relates to
-
JRACLOUD-67418 Equal Operator in the Issue navigator doesn't finds results for dates
-
- Closed
-
Hi everyone,
Thank you for previously raising this bug and bringing it to our attention.
Within our company roadmap and work capacity, we try to address or review each bug request but admit that not each one will be resolved. To continue the culture of being honest and open, we are closing this bug to focus on our upcoming roadmap for all Jira users.
As we continue to roll out features we do look at requests made by our users and if you feel like this bug is still impacting your team please let us know.
Thank you again for providing valuable feedback to our team!
Jira Cloud team