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

Validate and report if JQL is "slow" during any save function in the product

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • None
    • JQL
    • None
    • 2
    • 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.

      Slow JQL can create multiple performance-related  issues:

      • slow automation in JSD 
      • slow down issue creation, assignment, commenting etc   JRASERVER-68174 if dealing with webhooks listening for these events 
      • slow down kanban board loading

      Just to name a few. 

      It would be really cool if Jira ran a quick self-check on how long the JQL being saved to a board, webhook, filter, automation rule, to see if it violates the slow JQL rule of let's say 40 ms or something like that. 

          Form Name

            [JRASERVER-69442] Validate and report if JQL is "slow" during any save function in the product

            M Hoogenboom added a comment -

            This also seems to be an issue when migrating issues to another issue type (because an issue type screen scheme change). I see a lot of these messages in the log and the strange thing is, that the JQL doesn't really make sense in the log:

             2020-09-15 09:39:53,448+0200 http-nio-8080-exec-8 INFO UserName 564x95445x1 1vfuzwy 10.103.152.67,10.103.9.161 /secure/admin/MigrateIssueTypes!perform.jspa [c.a.j.p.webhooks.matcher.JqlEventMatcher_SLOW] JQL query '{project = "PROJX"} AND {status = "In Progress"} AND {key in ("PROJY-8153")}' produced lucene query and took '139' ms to run.

            Note that PROJX and PROJY are different projects, and for me it is totally unclear why the MigrateIssueTypes would run such a query.

            M Hoogenboom added a comment - This also seems to be an issue when migrating issues to another issue type (because an issue type screen scheme change). I see a lot of these messages in the log and the strange thing is, that the JQL doesn't really make sense in the log:  2020-09-15 09:39:53,448+0200 http-nio-8080-exec-8 INFO UserName 564x95445x1 1vfuzwy 10.103.152.67,10.103.9.161 /secure/admin/MigrateIssueTypes!perform.jspa [c.a.j.p.webhooks.matcher.JqlEventMatcher_SLOW] JQL query '{project = "PROJX"} AND {status = "In Progress"} AND {key in ("PROJY-8153")}' produced lucene query and took '139' ms to run. Note that PROJX and PROJY are different projects, and for me it is totally unclear why the MigrateIssueTypes would run such a query.

              Unassigned Unassigned
              rvolkmar Ronnie Volkmar
              Votes:
              10 Vote for this issue
              Watchers:
              11 Start watching this issue

                Created:
                Updated: