How to Sync Assets with Getint
Jira Assets lets you track configuration items, services, and other resources. With Getint, you can keep those Assets up to date across connected systems. This article shows you how to configure Getint to pull and push Jira Assets, map fields, and schedule regular updates.
What Are Assets?
In Jira, an Asset is an object composed of fields and values in a key-value format, similar to a JSON structure. If your organization assigns devices to employees (such as phones or laptops), these devices are usually tracked in tickets that include one or more Asset fields.
These objects live inside custom fields created by users, just like other field types. However, querying them requires a different syntax than standard JQL. Instead, you'll use AQL (Assets Query Language).
To search for data within an asset object, you'll need two things:
The name of the custom field that contains the asset.
The specific field and value within the object you want to locate.
Mapping Assets in Getint
Mapping assets works like any other field in Getint. To locate specific objects, you'll need to include a query written in AQL (Assets Query Language). Here's how to map two related fields:
Identify the custom fields that contain the asset data, and map them. In this example, we will use the Multi Related Asset field.
Assets can store multiple objects/values. Therefore, you will need to select the Assets schema and write an AQL query that targets the relevant object type and attributes.
Asset queries should now be visible. You can edit the selected schemas at any time from the same menu.
Test the query to confirm it returns the expected results, and match the options based on shared values or reference.
Mapping Assets to Other Fields
Assets can be mapped to various fields, including text, picklist, and multi-select fields.
To map another field to your assets, add a field mapping and select the field to sync. For example, using a custom cascading field requires matching options in the mapping configuration, as shown below.
To map assets to text fields, repeat the process and select the corresponding text field to sync. Unlike the picklist, no dropdown options are needed. Instead, set the text field to use label from other side, so it receives values from assets during sync.
Mapping assets to text fields works unidirectionally—from assets to the custom field only. Changes to the custom field will not sync back to assets.
How to Query Assets?
For example, let’s say we have a project where we only want to sync work items that include a custom field called Multi Related Asset. This field contains an Asset object, and we’re looking for items where the Name inside that object field is set to MacBook Pro 15''.
In the project's JQL selection box, we would enter:
project = "Jira Jesus" AND "Multi Related Asset" in aqlFunction("Name = \"MacBook Pro 15\\\"\"")
Once you've confirmed that the JQL returns the correct work items in your project, you can paste the query into the appropriate field in Getint, as shown below.
Important Notes:
Asset objects often include multiple fields, and each one can be queried on its own. If you need to check more than one field, create separate AQL clauses and combine them using
ANDorOR, depending on the logic you want to apply.
project = "Jira Jesus" AND "Multi Related Asset" in aqlFunction("Name = "MacBook Pro 15\""") OR "Related Asset" in aqlFunction("Name = "Lenovo Thinkpad\"")
Before syncing or migrating, make sure your JQL query returns only the work items you want to move. Double-check that nothing extra is included and nothing important is left out. Once you're confident the results are accurate, paste the query into the JQL selector in your Getint connector. This ensures that only the intended items are included in the sync or migration.
Conclusion
Syncing Jira Assets with Getint comes down to understanding how Assets are structured, writing precise AQL queries, and mapping fields correctly. Once your queries are tested and your connector is configured, Getint will handle the syncing based on your setup. This gives you a reliable way to keep asset data aligned across systems without surprises or unnecessary transfers.
Last updated
Was this helpful?