Skip to main content
All CollectionsEmployee Lifecycle Workflows
Use Action Outputs as Smart Values in Jira Automation
Use Action Outputs as Smart Values in Jira Automation
Updated yesterday

When configuring a Trigger Action post function in Jira, you can store the output of the action as an issue property.

This allows you to use the output using a Smart Value in Jira Automation rules. This can be useful when you want to trigger different automation actions based on the output of an integration.

For example, you may want to perform a custom action after creating a user in your Okta integration.

In the Trigger Action post function, you'll find an option to transition the issue to another status after the actions have completed. This is important because the actions are executed asynchronously, so you need to evaluate the output after they have all finished.

While you don't have to use the transition option, it's recommended to evaluate the output properties in the "after execution" status.

For this example, we'll use the "Resolved" status. It's worth noting that you can have multiple Trigger Action post functions for the same transition. In that case, you should only select the transition option for one of them.

After selecting the transition status, you can configure the Create User action. The key part is the option at the bottom of the action configuration.

Enabling this checkbox will store the output of the action in the specified issue property

The default property path is: issue.properties.multiplierActionsOutput., but you can edit the the property name (multiplierActionsOutput) and the key (actioName) as needed.

If you have multiple Trigger Action post functions for the same transition, it's recommended to use a different property name to prevent potential race conditions when updating the issue properties.

For this example, we'll use the default values, but you can edit them by clicking on them. You can also copy the smart value path by clicking the copy to clipboard icon. The copied value will include a trailing .success, as this is likely the most useful value for automations. Clicking the copy to clipboard button will copy:

##{{issue.properties.multiplierActionsOutput.createUserWithoutCredentials.success}}

In this example, the User Creation action returns a success value (true/false) and the ID of the newly created user when the action succeeds. All actions will return a success value. Hover over each listed output value to see its description. Click the checkbox to enable the output.

With the configuration in place, we can now automate writing different comments based on the success value.

The automation is triggered when the issue is transitioned to the "Resolved" status. It then evaluates the success value written by the action. The IF condition must use the ##{{smart values}} condition to compare the previously copied smart value path. Use the copied path as the first value:

##{{issue.properties.multiplierActionsOutput.createUserWithoutCredentials.success}}

In the editor, it looks like this:

The automation is triggered when the issue reaches the "after execution" status, ensuring that the action has finished executing and the properties have been correctly written.

All actions will export a success value (true or false). Some actions may also export additional values, such as the user ID in user creation actions. If you are using an action that returns a value that is not being exported, please reach out to us, and we will include it.

Did this answer your question?