The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

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

dateCompare: Failed to get issues error while using ScriptRunner Enhanced Search

Rajagopal Govindaraj
June 4, 2024

I'm trying to filter the subtasks whose resolved date is greater than due date. I have created a custom field [status change] with datepicker and did an automation to store the custom field when the subtasks moved to done state.

Query used: project = Project1 AND type = Sub-task AND status = "Done" AND issueFunction in dateCompare(" ", "customfield_10061 > duedate ")

When I execute the query, i'm getting the below error:

dateCompare: Failed to get issues

 Can anyone support in resolving this issue?

Thanks !!

 

1 answer

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

0 votes
Rajagopal Govindaraj
June 5, 2024

Solution Found. subquery field in datecompare function should carry other filter details.

ex.,  issueFunction in dateCompare("project = Project1 AND type = Sub-task AND status = "Done" ", "customfield_10061 > duedate ")

DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
TAGS
AUG Leaders

Atlassian Community Events