jira:jqlFunction custom functions appear in JQL autocomplete but fail with "Unknown function" at query execution — for every function, on every environment reset

Forge Forge Modules and Product Triggers
1

I have a Forge app (jira:jqlFunction module, static declaration, endpoint/remote-backed) with 61 registered custom JQL functions. All 61 correctly appear in GET /rest/api/3/jql/autocompletedata (visibleFunctionNames) and in the issue navigator’s own autocomplete-as-you-type suggestions. But using any of them — including the very first and simplest one, a pure scalar function with no external calls — in an actual JQL query fails immediately with:

JQL error
Unknown function: jqlx.hasComments
We can't suggest a fix for this query yet.

This is not a partial/some-functions-work issue: every function I’ve tried, from the simplest (jqlx.startOfQuarter(), zero REST calls) to the most complex, fails identically. No search has ever returned real results from any of these functions.

2

Hi @celestecs.supp,

The dot is fine. Tested today on a dev site with a dotted and a plain function side by side, both autocomplete, both return issues quoted or unquoted and both get a precomputation stored.

What did break mine was a bad fragment. My first resolver returned key is not EMPTY, which isn’t valid JQL (/rest/api/3/jql/parse says ‘is not’ isn’t supported on key), and no precomputation got stored. I’d run each function’s returned fragment through jql/parse, probably the quickest check across 61.

Also not in. Jira runs the returned fragment as-is, so the resolver has to handle the negation itself.

Two gaps on my side: no literal “Unknown function” text, and only plain Forge resolvers, no endpoint-backed ones. Do the forge logs or endpoint logs show the call arriving when the query runs?