• Products
  • Get started
  • Documentation
  • Resources

Create a parent and child hierarchy for your data

Assets in Jira Service Management is a Premium and Enterprise only feature. Learn more about Assets.

To import data into Assets, you must first create an import structure, and then you must map the data into Assets using object type mapping.

If you want to create a hierarchy of imported objects when mapping your data into Assets, you can use a Child object type mapping to automatically link the child object types to the parent object type. This will cause the child object types to inherit all of the attributes of the parent object types.

Before you begin

  1. You must prepare your data for importing into Assets.

  2. You must create an import configuration.

  3. For each parent object that you want to map in Assets, you must create an object type.

  4. In the parent object type, you must allow the attributes to be inherited by object type children. You must do this before creating any child object types.

  5. For each child object that you want to map in Assets, you must create an object type.

Create a parent and child hierarchy for your data using child object type mapping

  1. From your service project, go to Assets > Object schemas.

  2. Select an Object schema.

  3. Select Schema configuration, then choose the Import tab.

  4. In the Import tab, select on Edit mapping on your import structure to expand it.

  5. Select the object type mapping where you wish to create a child mapping and select Edit attributes mapping.

  6. A button to Create child mapping will appear under the attributes mapping. Select this and enter the following information:

    1. Object type - since the child object type will be the same as the parent object type, this option will be disabled.

    2. Filter data source by IQL - An optional IQL to query the objects fetched from source. If you wish to filter the objects from data, you can accomplish that here.

    3. Identifier case matching - this option will be disabled.

    4. Missing objects - select from:

      1. Remove - Only entries from the import will persist as Assets object/s. Any object manually created in Assets will be deleted.

      2. Update - All objects in Assets not present in the import will have an attribute edited.

      3. Ignore - Object in Assets that is not found in the import won't be removed or updated.

    5. Missing objects outbound references - select from:

      1. Remove - Only outbound references from the import will persist as Assets references. Any outbound references manually created in Assets will be deleted.

      2. Ignore - Outbound references in Assets that aren’t found in the import won't be removed or updated.

    6. Empty values - When an object is updated, choose if empty values from the external source should remove the existing value. Select from:

      1. Use default - use the value specified in the “Define import structure” screen for this object type.

      2. Remove - remove the current value. If the attribute is a status, select, or reference type attribute with more than one value, all of the values will be removed.

      3. Ignore - keep the current value for this object type. If the attribute is a status, select, or reference type attribute with more than one value, all of the values will be kept.

    7. Unknown values - this option will be disabled.

  7. Select Create.

 

How to import data into Assets

  1. There are five steps when importing your data into Assets:

    1. Prepare your data.

    2. Create an import structure. There are four different types of import available:

      1. Discovery. Learn more about how to bring data from Discovery into Assets.

      2. CSV. Learn more about how to configure your CSV for importing.

      3. JSON import. Learn more about importing data from a JSON file.

      4. External import. Learn more about how to develop an app to import data into Assets.

    3. Map your data. There are two options:

      1. Map your data automatically by automatically creating object types and attributes, or;

      2. Map your data manually by:

        1. Using object type mapping to create Assets object types

        2. Using object type attribute mapping to create Assets attributes and references

        3. Using child object type mapping to create hierarchical parent and child structures.

    4. After you have created your object type mappings you must enable them. The import structure will not be executable until all object type mappings are set to ENABLED. If your object type mappings are not enabled, right-click on your object type mapping and click Enable to enable them.

    5. Execute the import.

 

Additional Help