Indicators of performance issues and the hints displayed
• Missing Project or Tracker filter
If only a general filter is applied for example on Status, without filtering on a given Tracker of Project, the following warning is displayed:
The following warning is displayed:
 |
For better performance limit the scope of your search to a single project or tracker.
|
• Several AND/OR conditions
The application of two or more OR condition activates the user hint.
The following warning is displayed:
The underlying query uses the OR operator multiple times which can lead to poor performance. You may have selected several meaning options or choice options from multiple trackers.
• ORDER BY or GROUP BY clauses
Using a GROUP BY or an ORDER BY clause activates the warning. The joint usage of GROUP BY and ORDER BY also activates the hints.
The following warning is displayed:
For better performance add more filter criteria to your grouping query.
• LIKE or NOT LIKE operators
Performance warnings are always displayed when applying the LIKE or NOT LIKE operators.
The following warning is displayed:
For better performance avoid using the like operator. If you know the exact text you are looking for, use equals instead.
• Complex upstream or downstream reference filters
Applying further filters for example on Summary, Description, and so on within the active upstream or downstream reference filters, displays the following warning:
For better performance limit the scope of your search to a single project or tracker and For better performance consider using simpler reference filters.
• Historical filters
Using a Historical filter automatically activates the performance warning.
The following warning is displayed:
Using historical filters may lead to poor query performance.
The following warning is displayed after switching to the Expert mode:
Historical filters do not appear in cbQL expressions, but still saved with the Report in Expert mode.
 |
Filtering performance warnings disappear when the specific filters that activate the warnings are removed.
For instance:
• Removing the Historical filter
• Using the EQUALS/NOT EQUALS operators instead of the LIKE/NOT LIKE operators • Using Revert changes when the warning appears after the last modification. Select  and then click  to revert the changes.• Besides the active GROUP BY or ORDER BY clauses, the application of any additional filters not supported by this feature removes the performance warnings. |