Uploaded image for project: 'Jira Platform Cloud'
  1. Jira Platform Cloud
  2. JRACLOUD-83317

Queries using `worklogAuthor` JQL field are timing out

XMLWordPrintable

      Issue Summary

      Queries that use worklogAuthor with user IDs as filter condition are timing out. It is not Tempo Timesheet specific, the problem also occurs when using standard JQL Search.

      For example, worklogDate > 2024-03-02 and worklogDate < 2024-03-10 and (worklogAuthor in ('putUserIDHere')) is timing out using the standard JQL search.

      When using a group as a filter condition the query is not timing out, e.g., worklogDate > 2024-03-02 and worklogDate < 2024-03-10 and worklogAuthor in (membersOf('developers')) returns a result.

      Steps to Reproduce

      • Go to Issue Navigator (Filters -> View all issues from top menu)
      • add JQL query: worklogDate > 2024-03-02 and worklogDate < 2024-03-10 and worklogAuthor = currentUser()
      • Run the query

      Expected results

      The report is generated as expected

      Actual results

      The following error is seen in the UI:

      Jira unavailable
      The requested resource fails to load. If the problem persists, please contact Atlassian Cloud Support

      Workaround

      The JQL queries need to be further scoped to specify as many parameters as possible (project, particular user, etc). 

      When using a group as a filter condition the query is not timing out, e.g., worklogDate > 2024-03-02 and worklogDate < 2024-03-10 and worklogAuthor in (membersOf('developers')) returns a result.

      Combining the two filter conditions is also not timing out worklogDate > 2024-03-02 and worklogDate < 2024-03-10 and (worklogAuthor in ('userIDHere') or worklogAuthor in (membersOf('developers')))

       

      If you are still experiencing issues, please raise a request with us

              2cae379b8388 Łukasz Rajzer
              746d4674445b dkozel
              Votes:
              7 Vote for this issue
              Watchers:
              21 Start watching this issue

                Created:
                Updated:
                Resolved: