issueFieldMatch on labels field returns empty for certain projects

[Karl-Frederik Maurrasse]

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.

[Brant Schroeder]

@Karl-Frederik Maurrasse 

The syntax that you have is correct so it has to be something with the project.  Are all the labels you are searching for used in MyProject?  Do you have the same permissions on MyProject as the other projects?  Have you tried reindexing myProject?

[Karl-Frederik Maurrasse]

Are all the labels you are searching for used in MyProject? 

Yes, I have done both a manual lookup and a Basic Filter to confirm that the labels exist, and thus the query should have returned something.

Have you tried reindexing myProject?

I had it re-indexed by admins, to no avail.

Do you have the same permissions on MyProject as the other projects?

Unclear. I should be a developer in all of the projects. That said, my admin couldn't successfully execute the query either.

[Brant Schroeder]

@Karl-Frederik Maurrasse if you are able to see the labels in a different query then it sounds like access is not an issue.  No errors are generated it is only blank?  Are you seeing anything in the Jira logs?

[Karl-Frederik Maurrasse]

@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.

[Brant Schroeder]

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]

@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.