Using Cascading Options with Jira forms and Assets

XMLWordPrintable

    • Type: Bug
    • Resolution: Unresolved
    • Priority: Low
    • Component/s: Assets - AQL
    • None
    • 2
    • Minor

      Issue Summary

      This is a problem on how the Assets AQl resolve the ${customfield_xxx.label} placeholders. Rather than returning a list of comma separated value if the custom field have multiple values. It return a "-" separated list.
      You can see the same errors if you use the Asset fields on the Jira issue view, and not using proforma forms. Which comes from CMDB's endpoint
      /rest/servicedesk/cmdb/1/field/customfield_10359/config/10605/autocomplete?start=0&limit=50

      Steps to Reproduce

      1. Create a form that references 2 Assets Custom field and keep the Filter work item scope (AQL) of custom_field_1 as object HAVING inboundReferences(Name IN (${custom_feild_2.label}))
      2. Now try selecting multiple felids in the column that references custom_field_1
      3. Post that try adding the column  that references custom_field_2 and it would fail

      Expected Results

      "AQL "objectSchemaId = 15 AND (object HAVING inboundReferences(Name IN ("001-AIR CONDITIONING ASSEMBLY - COMPLETE","004-HEATER AND A/C - SLEEPER")))"

      Actual Results

      The below exception is thrown in the splunk file:

      "AQL "objectSchemaId = 15 AND (object HAVING inboundReferences(Name IN ("001-AIR CONDITIONING ASSEMBLY - COMPLETE"-"004-HEATER AND A/C - SLEEPER")))" has invalid syntax at position 108 with error message "no viable alternative at input ' AND (object HAVING inboundReferences(Name IN ("001-AIR CONDITIONING ASSEMBLY - COMPLETE"-'""  

      Workaround

      No workaround

            Assignee:
            Unassigned
            Reporter:
            Simran Singh
            Votes:
            2 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated: