How to update Asset object attribute using automation with values from associated Jira issue

Still need help?

The Atlassian Community is here for you.

Ask the community


Platform Notice: Cloud Only - This article only applies to Atlassian products on the cloud platform.

Summary

This article details steps to automatically update the Attributes for an Asset object with values from the associated Jira issue via Automation for Jira. This action also can be of benefit to non-JSM licensed users to edit objects in Assets via creating an issue in Jira or the Customer Portal.

Environment

Jira Service Management Assets

Scenario

The admin would like to update an Attribute of assets selected on an Asset object field in JSM issues. For example, the admin would like to update the 'Owner' Attribute of a 'Computer' asset with the Reporter of the JSM issue.


Solution

  1. Create Object Schema and Object type for Assets.
  2. In the Assets object type, add 'Owner' attribute.
  3. Create Asset object custom field  and add to JSM screen. E.g: Computer
  4. Then, create automation as below:-
    • Pick Issue Created trigger (Or any trigger depending on when/where in the issue you would like the attribute to be updated)
    • Then, add the 'Edit Assets field attributes' action. 

      The 'Edit Assets field attributes' action is located under Issue Actions



    • For Asset Field, select the Asset object field created on Step 3.
    • Choose the attributes that you would like to update. For example, to update the Owner attribute with the Reporter of the Jira issue:

    • Save and publish the automation rule.
    • Lastly, the moment of truth. Test it (smile)



(info) This automation also can be used to update object attributes with other smart values or fixed text as well. E.g: value from a different custom field in the issue. Feel free to explore the smart values that can be used on the  Advance your rules with smart values  documentation page.

(warning) The same actions are not available on Jira Server/Data Center. More details and a potential workaround can be found here:

Last modified on Mar 21, 2024

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.