Atlassian Data Model and Tables

Owned by Maria Kutkina
Last updated: Feb 04, 2024
11 min read

 

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.

assets dm.png

 

Core Elements:

  • Object Schema “A”

    • Object Type (e.g. “Software”)

      • object 1 (“MS Offie”)

        • child object 1-1 (“Word”)

          • attribute

image-20240202-102308.png

 

  1. Object schema: It works like a map that holds all of it together. In the Jira world, that would be a project.

  2. Object types: Containers for your objects (assets), each with its own characteristics, like specific issue types (Computers, Mobile phones). 

  3. 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).

  4. Attributes: What defines your object types (objects inherit them). Like fields or custom fields (Name, RAM, Storage).

  5. 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.

Each object schema is distinct and holds unique information in the form of

  • object types,

  • objects,

  • attributes,

  • icons,

  • references,

  • and statuses.

 

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.

The table uses the following columns:

The date and time (UTC time zone) when the schema was created.

SQL name

created_at

Data type

Datetime

The description of the object schema.

SQL name

description

Data type

String

* Services Object Schema

 

Asset Object Type

All object types will have four mandatory attributes:

  • Name

  • Key

  • Created Date

  • Last Updated Date

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.

The table uses the following columns:

 

  • Each object type can have a single parent object type and multiple child object types.

  • You can configure inheritance so that child object types automatically receive the attributes of their parents and pass their own attributes to their children.

  • Similarly you can set some object types as abstract, meaning that they can’t contain any objects of their own but can pass their attributes to their children, who can themselves contain objects. Inheritance and abstract object types can be used to create object schemas that are both simple and powerful.

 

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.

When the attribute is a string (for example, an address), it is stored in attribute_value_string. When the attribute is another object, the object_id of that object is stored in attribute_value_object_id.

The table uses the following columns:

 

Sample asset_object_issue_mapping table

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

Attribute Configurations

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: