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

Insights Automation: Looking up Insight objects in automation when the IQL contains an & throws an error and returns no results

    XMLWordPrintable

Details

    • 8
    • Major
    • 68
    • Hide

      Hi Team 👋

      This is Mohamed from the JSM Assets product team. Quick update on this one, the fix has been implemented and rolled out to 100% of our users 🎉

      Once again Thank you for your patience and apologies for the inconvenience caused by this issue.

      Mohamed

      Show
      Hi Team 👋 This is Mohamed from the JSM Assets product team. Quick update on this one, the fix has been implemented and rolled out to 100% of our users 🎉 Once again Thank you for your patience and apologies for the inconvenience caused by this issue. Mohamed

    Description

      Issue Summary

      When looking up Insight objects (or branching on IQL) in Jira Automation, if the IQL contains an & (or a placeholder with an &) the IQL won't execute and will return an error.

      However, the same IQL executed within the Insight UI works fine.

      This is reproducible on Data Center: no

      Steps to Reproduce

      1. Create an object with a Name containing an & (e.g. "A & B")
      2. Create an automation rule (schedule trigger, lookup objects action)
      3. Add an IQL like "Name = "A & B"
      4. Execute the automation rule

      Expected Results

      The IQL is executed and the object with name "A & B" is returned in the results

      Actual Results

      An error is returned like "IQL has invalid syntax... token recognition error at..."

      Workaround

      Currently there is no known workaround for this behavior. A workaround will be added here when available

      Attachments

        Issue Links

          Activity

            People

              90325da67d46 Mohamed Hassan
              aolrich Andrea
              Votes:
              26 Vote for this issue
              Watchers:
              31 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: