Summary

The Automation service can be used to retrieve and handle Jira Service Management Assets data in a number of ways, however due to certain bugs impacting data processing for the returned Assets data, Jira smart value functions such as text, list and math functions do not work as expected. The primary workaround at this time is to use the Create variable action in Automations to set the value of the returned Assets data. Variables currently return data in text format, which allows various smart value functions to be used on the data stored in the variable.

This document will list the associated bugs and provides examples and workarounds for the associated functions.

Associated bugs

The following bugs have been identified to be impacting how Automation functions handle Assets data returned through branches using AQL, the Lookup Objects action or accessing Objects within Assets custom fields on an issue:

List functions:

JSDCLOUD-12734 - Getting issue details... STATUS

Text functions:

JSDCLOUD-12733 - Getting issue details... STATUS

Math functions:

JSDCLOUD-12831 - Getting issue details... STATUS

Conditional logic:

JSDCLOUD-12834 - Getting issue details... STATUS

Solution

In all four scenarios, the workaround to allow the attributes to be used by the functions listed above is to create a variable and to set the value of the variable to the data returned from Assets. An example of this would be using the Lookup Objects action to query Assets and using the split text function on the data returned as part of a JSON payload. This is because the .split(",") text function converts text data into list data, allowing the various functions to operate on the data.

1. In this example, we are accessing an Object with a Select attribute type called Components holding the values ABC and XYZ:
   
2. For testing purposes the following trigger and AQL configuration will be used with the Lookup Objects action:
   1. Trigger: Manual trigger from issue
   2. Schema: DEMO AQL: Key = DEMO-123
3. Using the Create variable action the result of the Lookup Objects action can be set as the. The following data is used with the variable:
   1. Variable name: componentObject
   2. Smart value: {{lookupObjects.Components}}

4. As this example is for demonstration purposes, the result is captured in a log action, however the payload below can be used to edit an issue field via the advanced field editor in the Edit issue action. In this case the split function can be used to create a list of values that can be converted into a valid JSON payload using JSON functions:

   {{componentObject.split(",").asJsonObject("name").asJsonArray}}

The result of the above log action is shown in the screenshot below:

{{componentObject.split(",").size}}