issueFieldMatch on labels field returns empty for certain projects

Question

The problematic queries that return no records, when a "basic" search with similar filters does return records:

* issueFunction in issueFieldMatch("project in (MyProject)", "labels", "EXISTING-LABEL")
* issueFunction in issueFieldMatch("project in (MyProject)", "labels", "EXISTING-LABEL-WILDCARD-*")

The goal here is to use the wildcard (*) and do regex for a base string in a set of labels we've defined. That is why we want to use issueFiledMatch instead of a basic query with a pre-defined checklist of labels.

The above queries fail against "MyProject", but work against other Jira projects managed by the same instance.

Karl-Frederik Maurrasse · Answer

@Brant Schroeder  If you look back to the description, the first query has no wildcard and suffers the same fate.

Do you have a proxy setup on your instance?

Will verify and get back to you.

Brant Schroeder · Answer

Thanks for the additional information.  I wonder if it is just timing out because of the wild card piece.  Do you have a proxy setup on your instance?

Karl-Frederik Maurrasse · Answer

@Brant Schroeder I dot have access to the backend logs. The Console logs show a failed POST to

/jira/secure/QueryComponent!Jql.jspa 400

both in the good and bad cases.

No errors are generated it is only blank?

It shows the standard "no issues were found to match your search" message.

Additional Info

MyProject (the problematic one) is much larger than the others, with more than 280K tickets. The other projects are in the few thousands at most.

When I submit the problematic query, the search appears to take close to 50 seconds to throw the generic message above. In the good scenarios, the query only takes a couple of seconds at most.