Jira Insight (Assets) allow attribute to include child object types

[mnd]

In setting up an Object Schema in Jira Insight, I would like to be able to select child object types in an attribute field.

For example, I have an Object Type called "Location", which will be an abstract parent. There will be three child types called: Desk, Off Site, and Server Room. Each of these are separate types of locations, but all indicate where an asset can be located. In my "Computer" object type, I would like to have an attribute called "Location" which has a Type of "Object", and set it to the parent object type "Location".

After setting this up, I can only select Location objects in this field. What I want is to be able to select a Desk, Server Room, or Off Site location.

Is this possible?

Object Types

Computer Attribute

[Mikael Sandberg · Accepted solution]

No, the attribute reference can only be a 1-to-1 relation, so you cannot set the attribute to reference Desk, Server Room or Off Site, you have to pick one of the three. And you if you would create the location as an abstract object schema your reference cannot use that to pick objects, it would show up as an empty list.

[mnd]

@Mikael Sandberg thanks so much for the response. Do you know of any other way to handle this type of situation? The two less-than-ideal solutions I can think of are:

1. Do not group the different types of locations, just make them all as a "Location" object. Possibly include a naming convention prefix.
2. Keep the 3 sub-types of location and create 3 attributes on the asset to specify where it is located.

Thanks again.

[Mikael Sandberg]

I would probably go with your first option, and either use a label or a prefix like you suggested.

[mnd]

@Mikael Sandberg by "label" do you mean another attribute on the object type, or is there a label feature that I'm missing? Thanks.

[Mikael Sandberg]

Another attribute, that way you can use a filter to say only show desk.

[mnd]

Thanks for your help!

For anyone else who comes across this, I tested out the #1 option above. All types of locations were stored under the "Location" object type and used a prefix, such as "Server Room". Each location also had a "Type" attribute added, and required a value of: Desk, Off Site, or Server Room. When I associate an asset with one of these locations, I can then filter them down based on the Location.Type field, which is an advanced IQL query that looks like this:

"Location"."Type" = "Server Room"