Automate Reporter Assets Field in JSM Cloud
Platform Notice: Cloud Only - This article only applies to Atlassian apps on the cloud platform.
Summary
Learn how to auto-populate the Assets object field based on the "Reporter" field of the ticket.
Solution
This recipe needs two things in place before the Automation rule works: (1) a User-type attribute on the object type, populated with each user's account, and (2) the Assets object custom field on the screen. The rule then matches objects to the ticket reporter via an AQL query such as:
"<user-type-attribute-name>" = {{reporter}}First, create the User attribute under Assets > object type > Attributes (it accepts both Atlassian and portal-only accounts).
For this automation to work, the "User" type attribute created above must be populated with the reporter's account.
Then create a rule:
Trigger: Work item created.
Action: Edit work item → set the Assets object field with this AQL, replacing
Ownerwith your User attribute name:
"Owner" = "{{reporter.accountId}}"Save and publish the automation rule.
After publishing the rule, the Assets object field will be automatically populated with the assets assigned to the reporter of the ticket right on its creation.
To verify it works, create a test ticket and confirm that the Assets object field is populated with the reporter's assigned objects (check the audit log if it's empty — the User attribute isn't usually populated for that reporter).
For more examples about fetching Asset objects based on single or multi-user type custom fields or vice versa, refer to this article: Auto-populate approvers from Asset objects attributes.
Was this helpful?