The Assets additional export populates 3 tables in Databricks:
Table Details
D4J_ASSETS
This table contains information related to Assets in Jira. All Asset information available from Jira is stored in this table. One instance of this table is created per configured export location. All exports with the Assets additional export option selected will merge asset information into this table. For this reason, it is generally recommended that this option only be selected for one export per location. Otherwise export processes may perform duplicate work. Custom/scheduled updates to exports will only merge in assets that have changed since the last update.
|
Column |
Type |
Description |
|---|---|---|
|
ID |
INT |
Autogenerated ID |
|
ASSETID |
STRING |
Asset ID |
|
WORKSPACEID |
STRING |
Asset’s workspace ID |
|
GLOBALID |
STRING |
Asset’s global ID |
|
OBJECTKEY |
STRING |
Asset object key |
|
LABEL |
STRING |
Asset label |
|
CREATED |
TIMESTAMP |
Asset creation timestamp |
|
UPDATED |
TIMESTAMP |
Asset update timestamp |
|
TYPEID |
STRING |
Asset type ID |
|
TYPENAME |
STRING |
Asset type name |
|
TYPEDESCRIPTION |
STRING |
Asset type description |
|
TYPESCHEMAID |
STRING |
Asset type schema ID |
D4J_ASSETS_BRIDGE
This table contains information that associates assets to work items and custom fields in Jira. All Asset custom field link information associated with the current export’s work items is stored in this table. One instance of this table is created per configured export location. All exports, regardless of Assets additional export option selection, will merge information into this table if they contain custom fields that use assets. For this reason, multiple exports per location may include this information without causing export processes to perform duplicate work. If all asset custom fields from Jira are required, then one or more exports containing all Jira work items must include these fields. Custom/scheduled updates to exports will only merge in information that has changed since the last update.
|
Column |
Type |
Description |
|---|---|---|
|
ID |
INT |
Autogenerated ID |
|
ISSUEID |
INT |
Jira work item ID containing assets field |
|
FIELDID |
STRING |
Jira field ID containing assets |
|
ASSETGLOBALID |
STRING |
Asset’s global ID |
D4J_ASSETS_OBJECT_SCHEMAS
This table contains information related to Asset object schemas in Jira. All Asset object schema information available from Jira is stored in this table. One instance of this table is created per configured export location. All exports with the Assets additional export option selected will merge asset object schema information into this table. For this reason, it is generally recommended that this option only be selected for one export per location. Otherwise export processes may perform duplicate work. Custom/scheduled updates to exports will only merge in object schemas that have changed since the last update.
|
Column |
Type |
Description |
|---|---|---|
|
ID |
INT |
Autogenerated ID |
|
WORKSPACEID |
STRING |
Object schema’s workspace ID |
|
GLOBALID |
STRING |
Object schema’s global ID |
|
SCHEMAID |
STRING |
Object schema ID |
|
NAME |
STRING |
Object schema name |
|
SCHEMAKEY |
STRING |
Object schema key |
|
STATUS |
STRING |
Object schema status |
|
DESCRIPTION |
STRING |
Object schema description |
|
CREATED |
TIMESTAMP |
Object schema creation timestamp |
|
UPDATED |
TIMESTAMP |
Object schema update timestamp |
|
OBJECTCOUNT |
INT |
Number of objects in the schema |
|
OBJECTTYPECOUNT |
INT |
Number of object types in the schema |
|
CANMANAGE |
BOOLEAN |
Flag indicating whether the schema can be managed |
1This table is created and populated based on the presence of certain custom field selections in the main export table. The table may not exist in your Databricks instance.