Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-73047

As a Jira Admin I would like to be able to identify filters causing slow JQL

    XMLWordPrintable

Details

    • Suggestion
    • Resolution: Unresolved
    • None
    • JQL
    • None
    • 1
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

    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.

      Attachments

        Activity

          People

            Unassigned Unassigned
            imurakami@atlassian.com Murakami
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated: