Assets Data Model

Assets in Jira Service Management is a feature within Jira Service Management that allows team to track their assets, configuration items, and resources to understand and visualize the critical relationships between applications, services, their underlying infrastructure, and other key dependencies.

...

Expand
title Here’s what it looks like in Assets Admin View
Object schema: It works like a map that holds all of it together. In the Jira world, that would be a project. Object types: Containers for your objects (assets), each with its own characteristics, like specific issue types (Computers, Mobile phones).  Objects: Your actual assets, whatever they are. Similar to Jira issues or requests. Put them into object types, and get going (MacBook MBP M1, Latitude 7480). Attributes: What defines your object types (objects inherit them). Like fields or custom fields (Name, RAM, Storage). References: Relations and dependencies between objects. If you own a laptop, you have a reference to it (you own it). Like issue links, though they serve a different purpose.

...

Asset Object Schema

An object schema is a collection of information in Assets used to track assets, configuration items, and resources, and to understand and visualize the critical relationships between them.

...

🔷 Object schemas can be set up fully isolated from each other. Alternatively, you can allow some schemas to cross-reference objects from other schemas → combine individual object schemas into a larger data structures.

Sample Asset_object_schema table

describes the names, descriptions, unique identifiers, and creation metadata for all object schemas defined within asset and configuration management.

...

...

* Services Object Schema

...

Asset Object Type

All object types will have four mandatory attributes:

...

The last three are set automatically and can not be edited.

Sample asset_type table

describes the names, descriptions, unique identifiers, and creation metadata for all object types defined within asset and configuration management.

...

...

Asset Object

describes individual objects defined under the object types and object schemas.

Sample asset_object table

uses the following columns:

...

...

Asset Object Attribute

Attributes can comprise of many different data types including text, dates, numerics, URLs, etc. Details in dropdown .

...

🔷 Most notable attribute type which enables the whole network to build up is referencing another object with a custom link.

Sample asset_object_attribute table

describes the attributes of each object and stores the value of those attributes.

...

Sample asset_object_issue_mapping table

maps objects to Jira issues. The table uses the following columns:

...

...

Attribute Configurations

...

Expand
title More configurations
Option Description Suffix For default type "Integer" and "Float" you can set a suffix for the attribute. Example is "$" for an attribute "Salary". Hidden Hide the attribute from users in the "assets-users" role. Include children Include objects from a child object type(s). Unique Validate attribute values to be unique within the object type. Show Sum For default type "Integer" and "Float" you can choose to add the values and display the sum of the attribute values Indexed This is a checkbox and you can use this to determine if you want to index this attribute or not. The Indexed feature on every attribute essentially helps you to retrieve your search results faster when you do a basic search or an advanced search using AQL anywhere (e.g, post functions, imports, custom fields etc). So the recommended practice is that for all AQL queries used at these multiple places, you should index your attributes. If your attribute is indexed, Assets will not retrieve results from the database every time but instead retrieve them from an index/cache which yields results quicker. However, this comes at the cost of a higher memory consumption. For non-indexed attributes, memory consumption will be lower. If you index an attribute, a small icon () precedes the Name of the attribute as shown below. This icon will not be visible when you uncheck the Indexed checkbox. Additionally, for the label attribute, the indexed icon will appear adjacent to the icon for the label () as shown below. By default, Assets will index all attributes on an object type, but the "Textarea" attribute is an exception to this rule. The Key, Label, Created, and Updated attributes will always be indexed, as will any attributes of the type Reference.

Sample asset_type_attribute_metadata table

provides the metadata for object attributes. The table uses the following columns:

...

Sample asset_type_attribute_type_mapping table

maps object types to object type attributes. The table uses the following columns:

...

Sample asset_type_schema_mapping table

provides links between object types and the object schemas to which they belong. The table uses the following columns:

...