-
Bug
-
Resolution: Timed out
-
Low
-
3
-
Severity 3 - Minor
-
1
-
Issue Summary
JQL searches might time out when using the Not in clause to look for issues agains fields that contain multiple options (e.g. select list fields), specially when the site has a high amount of issue x field value associations stored.
Steps to Reproduce
- Have a select list (single choice) custom field with multiple options
- Have a high amount of issues that have values associated to that field
- One scenario where we found that problem had over 360000 issue x field value associations in the database
- Perform a search using Not in to exclude some options from the results
Expected Results
The search will work as expected.
Actual Results
The search might time out, resulting in a server error:
Workaround
Using the clause in and searching for the values that you want to return in the results instead has a lower cost, and might help achieving the desired results.
- relates to
-
-
- Closed
-
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
Hi everyone,
Thank you for previously raising this bug and bringing it to our attention.
Within our company roadmap and work capacity, we try to address or review each bug request but admit that not each one will be resolved. To continue the culture of being honest and open, we are closing this bug to focus on our upcoming roadmap for all Jira users.
As we continue to roll out features we do look at requests made by our users and if you feel like this bug is still impacting your team please let us know.
Thank you again for providing valuable feedback to our team!
Jira Cloud team