Insight Automation does not execute correctly when the condition has "objectType not in" in the IQL

XMLWordPrintable

    • Type: Bug
    • Resolution: Unresolved
    • Priority: Low
    • None
    • Affects Version/s: 4.20.2, 4.20.5, 5.4.9, 5.17.0, Insight 8.9.8
    • 5
    • Severity 2 - Major
    • 4

      Issue Summary

      Insight Automation does not execute correctly when the condition has "objectType not in" in the IQL

      Steps to Reproduce

      1. Create an automation rule with simple configurations like the following:

        WHEN: object created
        IF: objectType not in (A, B) and Location is empty
        THEN: create Jira issue

      2. Create an object that matches the IQL in the IF condition and verify if the Jira issue is created successfully.

      Expected Results

      The automation rule is triggered and executed successfully, the Jira issue is created as expected

      Actual Results

      The automation rule is triggered but no Jira issue is created.

      In the insight_automation.log file, we can see that the rule was triggered but no condition matched, which is not true. If we search for objects with the same IQL, we can see the object we just created.

      2022-03-03 17:56:49,150 [insight-event-11] | NO condition matched for ruleEvent.InsightAsyncEvent category: USER, rule id: 8, name: create jira issue isActive: true, objectRuleEvent id: 9 object: Test (OBJ-585845)
      

      Workaround

      This seems to be affecting only rule with objectType not in and objectType !=. Use objectType in instead.

            Assignee:
            Unassigned
            Reporter:
            Michelle Chin (Inactive)
            Votes:
            7 Vote for this issue
            Watchers:
            13 Start watching this issue

              Created:
              Updated: