Uploaded image for project: 'Jira Service Management Data Center'
  1. Jira Service Management Data Center
  2. JSDSERVER-11050

IQL+JQL search in Insight is slower when connectedTickets() contains additional arguments

      Issue Summary

      IQL+JQL search in Insight is slower when connectedTickets() contains additional arguments

      Steps to Reproduce

      1. Launch an Insight search over an object type that has connected tickets in Jira by using the connectedTickets() function and add some parameter to the JQL function to identify only certain Jira issues Ex.
      2. Create 2 projects (TEST and TEST2) and 2 Insight custom fields (test associated with project TEST1 and and test2 associated with project TEST2) and a total of 13 issues for the 2 projects and containing values for both custom fields.
      3. Custom field test is filtering on object type Service Catalogue and custom field test1 is associated with object type Service type.
        #2 issues are in status Work in progress in project test and only 2 issues exists in project test2 (with custom field associated with object type Service type).
        #When launching:
      *objectType = "Service Catalogue" AND object HAVING connectedTickets()*
      

      there is no JQL search initiated at all for returning the results.

      When launching:

      *objectType = "Service Catalogue" AND object HAVING connectedTickets(status!="Work in progress")*
      

      and adding status!="Work in progress" the JQL search is made through:

      issue_id:(10100 10101 10102 10103 10104 10105 10106 10107 10108 10201 10202)
      
       /rest/insight-am/1/search [c.a.j.i.search.providers.LuceneSearchProvider] JQL query: {ISSUE in (10100, 10101, 10102, 10103, 10104, 10105, 10201, 10106, 10202, 10107, 10108)} AND {status != "Work in progress"}
      

      where issues with IDs 10201 10202 are belonging to test2 where the custom field is filtering on object type Service Type.

      Therefore the SQL will be much slower as it will query all the issues with Insight custom fields disregarding of the object type filtered in IQL.

      Expected Results

      The JQL should search through issues which are connected to the Insight custom field filtering only over the IQL filtered object type

      Actual Results

      The JQL search is performed within all the issues with Insight custom fields disregarding of the object type filtered in IQL.

      Workaround

      Currently there is no known workaround for this behavior apart from specifying the issues ID in the JQL such as jql: issue in (issueIDs)

            [JSDSERVER-11050] IQL+JQL search in Insight is slower when connectedTickets() contains additional arguments

            Tom Tran added a comment -

            We are affected on JSM 5.4.7. Please backport this bug fix over to JSM 5.4 LTS

            Tom Tran added a comment - We are affected on JSM 5.4.7. Please backport this bug fix over to JSM 5.4 LTS

            Yash added a comment -

            Priority should be high for this issue

            Yash added a comment - Priority should be high for this issue

            I am surprised to see the BUG priority as LOW !!!

            We are on Jira 9.4.2, JSM 5.4.2 and Assets 10.4.2. Able to reproduce this issue even not having a single object created. 

            We tried accessing Assets → Search Assets → Search for Objects → With unresolved tickets in assets search(please mind our production Jira is not having any asset data or objects or no user have asset access), thats when we observed high CPU, memory and threads utilization on the connected node. 

            For sure this BUG will break our complete instance once Assets is rolled out to our user based.

             

             

            Madhu Kiran Yalamanchili added a comment - I am surprised to see the BUG priority as LOW !!! We are on Jira 9.4.2, JSM 5.4.2 and Assets 10.4.2. Able to reproduce this issue even not having a single object created.   We tried accessing Assets → Search Assets → Search for Objects → With unresolved tickets in assets search(please mind our production Jira is not having any asset data or objects or no user have asset access), thats when we observed high CPU, memory and threads utilization on the connected node.  For sure this BUG will break our complete instance once Assets is rolled out to our user based.    

            Babu R added a comment -

            Can we increase the Priority to High ??

            Babu R added a comment - Can we increase the Priority to High ??

              a06a9964b472 Dominic Brodowski
              tmarchionni@atlassian.com Tiziana Marchionni
              Affected customers:
              13 This affects my team
              Watchers:
              17 Start watching this issue

                Created:
                Updated:
                Resolved: