JQL date filters on a Jira Product Discovery custom date field

[Peter Gray]

Hi there, running into the following challenge with creating a filtered lookup based on a custom date field from Jira Product Discovery.

Goal: I would like to build a filtered lookup that shows me all Ideas from Jira Product Discovery with an upcoming date. The date field is a custom field in product discovery that we call "Estimated Completion Date." My goal is to then use this lookup for an automation workflow.

Challenge: I am unable to use typical date filters with either Basic search or JQL when building this list. 

Basic search:

JQL search:

With JQL, I receive the error "The operator '<=' is not supported by the 'Estimated Completion Date[Interval]' field." I also get this error if I use the custom field's ID, 'cf[10300]', instead of the descriptive name.

I see the same error when trying to validate this query in the automation builder in Jira Product Discovery:

Testing in a standard Jira Project:
I do not encounter this issue when building date filters on custom date fields in standard jira projects, so I'm thinking this is an issue potentially with Jira Product Discovery? For example, here is what I see with a custom date field in a standard Jira project using Basic search and JQL:

Am I missing something simple here or anyone know of potential workarounds that can help me achieve this filtered list? Appreciate any guidance!

[Bill Sheboy]

Hi @Peter Gray -- Welcome to the Atlassian Community!

Jira Product Discovery (JPD) uses its own date format, which is a JSON value as text to include a single date, quarter, or range of dates.  That is not supported by JQL, and I do not know if they plan to add it.  (If someone from the JPD team knows of upcoming changes, please let us know.)

The workarounds I can think of are:

• Perform the filtering inside a JPD view, as it supports its own data fields
• Unfortunately...JPD does not support adding a global, date-picker field.  An alternative would be adding a text field and using an automation rule to copy the JPD date field as text (e.g., 2025-06-02) to the custom text field...and then compare to literal dates in the JQL

Kind regards,
Bill

PS: Would one of the community champions please move this question to the JPD product area?  That will make it easier for the JPD team members to provide input.  Thanks!

[Peter Gray]

Thank you @Bill Sheboy for the reply and guidance here! I like the idea of the conversion of the JPD date to a custom text field that can be used to drive the JQL filter. Will give that a whirl and see if I can get it to work.