Export Assets objects fails when AQL search query contains the ampersand (&) character

XMLWordPrintable

    • 11
    • Severity 3 - Minor
    • 5

      Issue Summary

      Exporting the data from Jira Service management's assets objects will fail if the filter's AQL contains the ampersand (&) character somewhere in the string

      Steps to Reproduce

      1. Go to an Assets object schema that has some objects
      2. View an object type and filter the objects in it using AQL that includes an ampersand like in the example: 
         "Team" = "Test & Test" 
      1. Click in the "Bulk actions" drop-down menu (gear icon), then select"Export objects"
      2. Select Delimiter, Encoding and Format values then click in "Export"

      Expected Results

       The save file widget should open allowing the user to select the destination for the file containing the exported data.

      Actual Results

      The following unhandled error message is thrown in the page:

      {"errorMessages":[
      "Unexpected end-of-input: was expecting closing quote for a string value\n at [Source: (String)\"
      {\"iqlSearch\":true,\"iqlParams\":{\"objectTypeId\":\"3\",\"attributesToDisplay\":{\"attributesToDisplayIds\":[\"18\",\"19\",\"14\",\"20\",\"16\",\"17\",\"21\"]},\"page\":1,\"asc\":\"0\",\"orderByTypeAttrId\":\"14\",\"resultsPerPage\":100,\"includeAttributes\":true,\"objectSchemaId\":\"3\",\"iql\":\"\\\"Team\\\" = \\\"Test \";
       line: 1, column: 273] (through reference chain: com.riadalabs.jira.plugins.insight.channel.web.api.rest.model.ObjectFiltersEntry[\"iqlParams\"]->com.riadalabs.jira.plugins.insight.channel.web.api.rest.model.ObjectIQLFilterParamEntry[\"iql\"])"],"errors":{}} 

      Workaround

      Currently the only workaround to this issue is by avoid using the ampersand character at the IQL string.

            Assignee:
            Unassigned
            Reporter:
            Matheus Geraldini dos Santos (Inactive)
            Votes:
            22 Vote for this issue
            Watchers:
            22 Start watching this issue

              Created:
              Updated:
              Resolved: