The Projects additional export populates 1 table in Databricks:
Table Details
D4J_PROJECTS
This table contains information related to projects in Jira. All project information available from Jira is stored in this table. One instance of this table is created per configured export location. All exports with the Projects additional export option selected will merge project 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.
|
Column |
Type |
Description |
|---|---|---|
|
ID |
INT |
Autogenerated ID |
|
PROJECTID |
INT |
Project ID in Jira |
|
PROJECTKEY |
STRING |
Project key in Jira |
|
NAME |
STRING |
Project name in Jira |
|
PROJECTTYPEKEY |
STRING |
Project type key in Jira |
|
SIMPLIFIED |
BOOLEAN |
Flag for simplified project types |
|
STYLE |
STRING |
Project style in Jira |
|
ISPRIVATE |
BOOLEAN |
Flag for private project types |
|
ENTITYID |
STRING |
Project entity ID in Jira |
|
UUID |
STRING |
Project UUID in Jira |
|
LEADACCOUNTID |
STRING |
Project lead’s Jira user account ID |
|
CATEGORYDESCRIPTION |
STRING |
Project category description |
|
CATEGORYID |
INT |
Project category ID in Jira |
|
CATEGORYNAME |
STRING |
Project category name in Jira |
|
ISDELETED |
BOOLEAN |
Flag for projects that have been deleted in Jira1 |
1Jira does not include deleted projects in its API responses. The value of this flag relies upon existing information in Databricks that is compared to information returned from Jira when export data is updated. As a result, this flag will not accurately reflect the status of projects that were deleted before being stored in Databricks.