Issue Summary

When using the category field reference in your JQL query, this is considered to be a complex query that has performance implications and significantly limits the number of issues a search can handle.

Steps to Reproduce

1. Go to the issue navigator and run a simple search like using an existing Project category (e.g. category = "Project Category 1")
2. Open your browser's Developer Tools (inspect)

Expected Results

You should see a successful API call executing the search query towards /secure/QueryComponent!Jql.jspa:

Actual Results

Instead, we see a 400 response followed by a jqlTooComplex error.

Response

{
    "errorMessages": [
        "jqlTooComplex"
    ],
    "errors": {}
}

Despite the error, most times we actually still get the search results in Jira and wouldn't notice the error. This issue only becomes noticeable when you have a high amount of Projects and Issues that match the query which causes several problems:

• Slow performance while searching
• 500 internal server errors in Advanced Roadmaps if you're using this as a filter
• Errors when exporting the results

Workaround

Currently, there is no known workaround for using the Project category field in your searches under these circumstances. Instead, you should substitute this field with another (e.g. Components) or directly use the Projects in your JQL (e.g. project in (JRACLOUD, JSWCLOUD, JWMCLOUD)).