How to update Assets custom field via an Automation rule in Jira Service Management

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

Summary

In the Jira Service Management Cloud, there may be a requirement to update an Assets custom field via an automation rule.

Solution

Choose based on whether you already know the object ID:

  • Known object ID → Edit action with a JSON payload setting the ID directly.

  • Unknown/dynamic → Lookup Objects first, then pass {{lookupObjects.id}} into the JSON.

Known object ID

The following image shows how to update the Assets custom field via an automation rule. For simplicity, we have selected the manual trigger. But based on your requirements, you can select the trigger as you wish.

(Auto-migrated image: description temporarily unavailable)
{ "fields": { "customfield_11758": [ { "id": "af747313-53f2-461b-9db1-6b24f094fba2:2520" } ] } }

Unknown/dynamic

Run Lookup Objects earlier in the rule, then use {{lookupObjects.id}} in place of the hard-coded ID.

(Auto-migrated image: description temporarily unavailable)

REST-based calls in the rule need your workspaceId (Assets Premium). Retrieve it from https://<site>.atlassian.net/rest/servicedeskapi/assets/workspace.

Object ID

You can get the object ID via the Assets UI or via the REST API Get object {id}.

To confirm the rule works, trigger it on a test issue and confirm the Assets custom field shows the expected object.

Updated on July 17, 2026

Still need help?

The Atlassian Community is here for you.