Scriptrunner: using multiple issueFunction clauses in the same JQL query

[Aquarius]

Dear Experts,

I am using the query  that works fine and Returns Result. 

project = AAA AND type = Epic AND component in (XXX)
AND issueFunction in dateCompare("", "Target end > duedate")

But as soon as I change it to:

filter= YYY
AND issueFunction in dateCompare("", "Target end > duedate")

,where YYY = issueFunction in portfolioChildrenOf("filter = 'ZZZ'")

it works fine but returns No Result

Can you tell me what is wrong and which workarounds are possible?

[Trudy P Claspill]

Hello @Aquarius 

If you execute just:

filter=YYY

...do you get results?

And, if so, have you confirmed that within those results there are issues that meet the criteria of ...?

issueFunction in dateCompare("", "Target end > duedate")

[Aquarius]

Yes, sure @Trudy P Claspill 

[Trudy P Claspill]

Does that mean you did test the YYY filter by itself, and you did confirm it has results that meet the criteria of the dateCompare function?

[Aquarius]

Yes of course, @Trudy P Claspill 

[Trudy P Claspill]

What is the JQL of your filter ZZZ?

I recreated the structure of your filters, and I did not encounter the same problem, but that could be because my filter TrudyTestFilterZ is not comparable to your filter ZZZ.

issueFunction in dateCompare("", "Target start >= Target end")
I found two issues with this filter where the issues are Epics that are children of a higher level issue - ABC-123

TrudyTestFilterZ:
key=ABC-123

TrudyTestFilterY:
issuefunction in portfolioChildrenOf("filter='TrudyTestFilterZ'")

Final filter:
filter='TrudyTestFilterY' and issueFunction in dateCompare("", "Target start >= Target end")

The final filter returned 2 issues

I am working with Jira DC 9.12.12 and Scriptrunner 8.35.0.