Issue linking custom asset object to request type

[J Conners]

Using OOB ITSM project template and OOB Employee and ITAssets for Assets templates.

Added attribute "Assigned to" type: Object: Employee on "Hardware Assets" objects, which is outbound reference to Employee:Employee objectType which contains attribute AtlassianUser type User.

Attempting to add "Hardware Assets" sub objectType: Laptops, objectType: Monitors objectType: "Docking Stations" to request issue type Service Request and request issue type Incident.

asset custom objects created and added to Create and view/edit screens for Service Request issue type and Incident request issue type

Affected Hardware

object schema: IT Assets

• objectType = "Hardware Assets"
• Filter scope: "Assigned to".AtlassianUser = ${reporter}

Affected Laptops

• objectType = Laptops
• Filter scope: "Assigned to".AtlassianUser = ${reporter}

Affected Monitors

• objectType = Monitors
• Filter scope: "Assigned to".AtlassianUser = ${reporter}

Should the filter scope be: outR("Assigned to".Atlassian.User = ${reporter}   ????

Is there an issue with AQL because object hierarchy does not contain unique names?

(Object Schema: Employees --> objectType: Employees  ????