Asset schema
Jira Assets (Insight) organizes data in a schema, made up of object types (for example Customer or Project), each with its own attributes (for example Name or Country). Before Business Central records can be synchronized as assets, this structure needs to exist in Business Central - either created automatically as a recommended default, or modeled manually to match an existing Jira Assets schema.
Default schema
On the Jira Asset Schemas page, select Create Default DYCE Schema to create the recommended starting point in one step: a schema named DYCE Business Central (code DYCE_CORE, schema key DYCEBC) with four object types - Customer, Customer Employee, Project and Service Asset - together with their attributes and the matching table and field mappings. This can be run repeatedly; configuration that already matches is reused rather than duplicated.
The Service Asset object type's Job Planning Line ID attribute carries the Business Central system ID of the underlying Project Planning Line; DYCE Time Tracking uses it to preset time recordings - see Creating Service Assets.
Schema, object type and attribute
| Page | Shows |
|---|---|
| Jira Asset Schemas | All schemas, with Code, Name, Schema Key, Sync Status and Jira ID |
| Jira Asset Schema Card | Code, Name, Schema Key (2-10 uppercase letters or digits), Description, OAuth Setup Code, Sync Status, Jira ID, and the object types belonging to the schema |
| Jira Asset Object Type Card | Schema Code, Code, Name, Icon ID, Sync Status, Jira ID, and the attributes belonging to the object type |
| Jira Asset Attributes (part on the object type card) | Code, Name, Data Type, Options (Select data type only), Is Mandatory, Is Unique, Reference Object Type (Object Reference data type only), Sync Status |
Every new object type automatically receives a mandatory, non-deletable system attribute named Name.
Attribute data types
Each attribute has one of the following data types: Text, Integer, Boolean, Date, Date Time, URL, Email, Select, or Object Reference. An Object Reference attribute points to another object type within the same schema (its Reference Object Type), and can only be targeted by a field mapping whose Business Central source field has a table relation - see Field mapping.
Sync status and pushing to Jira
Schemas, object types and attributes each carry a Sync Status: Draft while only defined in Business Central, and Synced once pushed to Jira. A Synced record can no longer be edited directly in Business Central; to change it, adjust the corresponding record in Jira, or add a new Draft attribute and push it separately.
Actions:
- Push to Jira - available while the schema is Draft; creates the schema, its object types and their attributes in Jira Assets, and marks them Synced.
- Push New Attributes (Jira Asset Schemas list) / Push Additions (Jira Asset Schema card) - available once the schema is Synced; pushes only attributes added since, without affecting what already exists in Jira.
Deleting a schema, object type or attribute that is already Synced asks for confirmation, since it is not removed from Jira by doing so. Deleting one still used by a table mapping, a field mapping, or as the target of an Object Reference attribute is not possible.