Uploaded image for project: 'Automation for Jira Server'
  1. Automation for Jira Server
  2. JIRAAUTOSERVER-1111

Assets custom field doesn't retrieve any values in Automation

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Low Low
    • 10.3.4
    • 10.3.1, 10.3.2, 10.3.3
    • Fields
    • Severity 3 - Minor
    • 9

      Issue Summary

      Assets custom field doesn't retrieve any values in Automation, even when using the object name (which should work).

      Steps to Reproduce

      1. Create project (you can use an example project with sample data, such as Assets IT Service Management)
      2. Go to the Automation area under Project Settings
      3. Create a new rule
      4. Select any event trigger, such as Issue commented
      5. Add a new action of type Edit issue
      6. Select an Assets field, such as Affected Server
      7. Try to search for an object associated with it, like exchange* (for the example project of point 1)
      8. The field will load forever and you'll see a 400 error in the browser console:
        GET
        https://linux-92270.prod.atl-cd.net/jsm/rest/insight/1.0/iql/objects?iql=objectTypeId=21 and Name like exchange
        Status
        400
        

      Expected Results

      The object is retrieved successfully.

      Actual Results

      The field keeps loading and never returns an object.

      Workaround

      The issue does not occur on (at least) versions 5.17.5 / 10.4.0.

      As a workaround, you may try specifying the Assets custom fields and objects to be assigned in JSON format as per Advanced field editing using JSON. Here's an example JSON text of setting an object (ITSMITSM-465) to an Assets custom field (customfield_10204).

      {
          "fields": {
              "customfield_10204": [{"key" : "ITSMITSM-465"}]
          }
      }
      

       

              34f3b0aee441 Swaraj Pal
              braymundo Bruno Raymundo (Inactive)
              Votes:
              3 Vote for this issue
              Watchers:
              10 Start watching this issue

                Created:
                Updated:
                Resolved: