Jira Assets Cloud : external import: import schema cannot reference objects created via the GUI?

[thomas]

Hi,

The concept of schema from a Jira Assets (Cloud) point of view and from a Jira external import point of view is confusing.

Scenario

1. Create a new Asset schema via the GUI. e.g "Henry's Sandbox", code: HSAND
2. With the GUI I create an object in that HSAND schema called : "Asset Owner"
3. I add 3 objects items: 'company', 'BYOD', '3rdparty'
4. I create an External import, generate a token
5. The import script use the token and MUST have a 'schema' and 'mapping' JSON file
6. In that schema/mapping JSON file, It defines a new object called "Laptop" that contains will contain a name, a S/N attribute AND a reference to the "Asset Owner" object created via the GUI to state if it's a company, personal or 3rd party laptop.

Issues/questions:

• I am confused by the concept of schema (HSAND) and the "schema": required for external import (aka API imports). Because on import it will create the "Laptop" object using the object definition from the "JSON "schema" into HSAND schema. A schema in a schema?
• Finally, my real issue is that if I understand correctly, I cannot set a reference to the "Asset Owner" objects because they aren't part of the same "schema"?
• Does the concept of external import mean we can only import everything and ideally nothing should be created via the GUI because there won't be anyways to reference it?

Note: I am NOT talking about cross-gui-schema access. e.g: a HSAND schema object trying to reach a FOOBAR schema object. Both created via the GUI. I am only trying to understand the concept of schema relationship and limitations between a GUI created schema (workspace) and the JSON "schema": attribute. 

[Christos Markoulatos]

Hi

In Jira Assets (Cloud), a schema is indeed the actual workspace (e.g. "Henry's Sandbox") where all of the object types live. When doing an external import, the "schema" in the JSON does not establish a new workspace but defines object types and attributes to be added to a selected pre-existing schema. Thus, your imported object (e.g. "Laptop") will be created within the HSAND schema. You can use GUI-created objects (like "Asset Owner") in your import, if they are in the same schema and the attribute is correctly defined as a reference. Mixing GUI setup and external imports is valid and often best practice.