JQL instability in recent Jira version – individual conditions work, but OR combination consistently

[Cory Cai]

I’m experiencing a serious JQL stability issue in the recent Jira version and would like to check whether others are seeing similar behavior.

Scenario:
Condition A → works fine
Condition B → works fine

However:
A OR B → consistently fails with search failed: com.atlassian.jira.issue.search.vsearch.SearchInternalException: Failed to run query

This is not a syntax issue. Both A and B individually return results quickly. But when combining them using OR, the query becomes extremely unstable and frequently fails.
The behavior feels unpredictable and performance seems significantly worse compared to previous versions.From a logical standpoint, if A and B can each execute independently, the OR combination should not completely break the query engine.

[Marc -Devoteam-]

Hi @Cory Cai 

Can you provide the JQL you are using, it could be that the JQL is not formated correctly on combining both conditons?

[Arkadiusz Wroblewski]

Hello@Cory Cai 

As @Marc -Devoteam-  mentioned to help you, we need to review whether there are any errors in your JQL.

What’s happening under the hood is: Jira can run A and B independently with a small/efficient plan, but OR often forces a much larger intermediate result set (and sometimes a different query strategy). If one side is “heavy” (history fields, worklog fields, user-picker fields with lots of permissions, large text searches, big IN (...) lists, Marketplace JQL functions, etc.), the combined query can tip over into timeouts / internal exceptions.