Details
-
Suggestion
-
Resolution: Unresolved
-
None
-
None
-
1
-
Description
Users can create filters and use them for
- Gadgets,
- Boards,
- Webhooks,
- Automations,
- and so on
A complex JQL with slow execution will be triggered on Jira DC monitoring, Slow query log and diagnostic log, but on none of them is possible to identify the filter used that caused the slow JQL execution.
The ideal would be to log when a filter used caused a slow query, logging the event.
This event could be captured by a monitoring tool and the Jira Admin would be able to take an action, identifying the filter and the user who had created it.