Page History

...

1.   Using unoptimized JQL queries can degrade performance substantially
   1. most times this happens because users don't understand how JQL works first of all; JQL is not like SQL (see Understanding JQL Performance). Thus, filtering issues by project by adding the "project = <xxx>" clause is not the same as specifying the project as argument to the subsequent JQL function.
      
      1. Example: 

         1. Use

            issue in requirements('OK','CALC')

            ...instead of ...

            project = 'CALC' and issue in requirements('OK')
            
            

2.  Some JQL functions, such as the ones dealing with requirement coverage, may be more intensive than other ones, since Xray may have to, for example, load all the related Test Runs in order to obtain relevant data. Some care should be taken with the following JQL functions:

   1. testPlanTests() - whenever by tests in a given status; the current workaround is to search using the "TestRunStatus" custom field. 

      Note
      title Please note
      When searching for Tests with a certain status inside a Test Plan, we recommend you to use the custom field search instead. Xray has created a new way of searching with big improvements when filtering by test status, using the Custom Fields: (3) issuetype = Test and TestRunStatus = "DEMO-10 - TODO" (4) issuetype = Test and TestRunStatus = "DEMO-10 - TODO environment:IOS"

   2. requirements() - whenever filtering by dates, as shown in the following example:

         requirements('OK',

                   'Calculator',  

                   'v1.0',

                   'chrome' 

                   'false'

                   '2014-08-30')

   3. testExecutionTests() - it will depend on the amount of Tests you have on the Test Execution

Xray calculated custom fields

...