Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Since this week, jqlTooComplex error on "worklogDate >= startOfDay(-3)"

Deleted user November 7, 2022

Hello, I've been using the API for a while now and everything has been working great until today: I now get

{"errorMessages":["jqlTooComplex"],"errors":{}}

When I haven't changed the JQL for months.

Here is my JQL:

project = OFFRES AND issuetype = "Offre" AND timespent > 0 AND worklogDate >= startOfDay(-3) ORDER BY assignee ASC

Note that even on the jira advanced issue search, the above JQL crashes the system (and does not even return an error on UI).

Any help is greatly appreciated.

1 answer

0 votes
Sunny Ape
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
November 10, 2022

Hello @[deleted] 

The following almost identical JQL search is working fine for me on Jira Cloud both via the GUI and via the REST API using the Search for Issues (GET) endpoint:

project = BPT AND issuetype = "Story" AND timespent > 0 AND worklogDate >= startOfDay(-3) ORDER BY assignee ASC

With the GUI, what do you mean by 'crashes the system'?

What other testing have you done? Have you tested altering the JQL slightly? Have you tested on another Jira Cloud instance? Does the problem happen for all projects / issue types? Does the problem go away under certain circumstances such as altering the worklogDate range? Did you try using the Parse JQL query endpoint to validate the query?

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events