Uploaded image for project: 'Jira Service Management Cloud'
  1. Jira Service Management Cloud
  2. JSDCLOUD-13635

In Automation AQL condition switches to Issue field tab even though the rule has object trigger.

XMLWordPrintable

      Issue Summary

      In Automation AQL condition switches to the Issue field tab even though the rule has an object trigger.

      Steps to Reproduce

      1. Create an automation with Object Trigger.
      2. Add a branch with AQL.
      3. Now below the object trigger, add the AQL condition.

      Expected Results

      • It should allow the query to be entered in the Object Tab.

      Actual Results

      • The object Tab is grayed out and the Issue tab is by default selected with a random custom field.

      Workaround

      Steps:
      1. Substitute "AQL Condition" with "Lookup objects" action
      2. Copy the Query from "AQL Condition" to "Lookup objects" action
      3. Append "AND Key = object" to the AQL used in AQL condition i.e:
         "Model Name" IS Empty AND Key = {{object}}
      4. Add "Smart values Condition" to compare "lookupObjects.size" and:
        • Equals 1 (for True) OR
        • Does not equal 1 (for False)
      Reference documentation:
      Loom/Recording/Screenshot:

        1. Doesn't work.png
          269 kB
          Yuti Kavathia
        2. workaround.png
          136 kB
          Ivan Chapistrak
        3. Works.png
          235 kB
          Yuti Kavathia

              7dfef69540b6 Naveen Karthick Baskaran
              7d0889323684 Yuti Kavathia
              Votes:
              14 Vote for this issue
              Watchers:
              21 Start watching this issue

                Created:
                Updated:
                Resolved: