Data Pipeline export schema
Issues data schema
All data relating to issues will be exported to issues_job<job_id>_<timestamp>.csv
. This file's schema appears as follows:
Field | Schema/Type | Sample Data | Description |
---|---|---|---|
| NUMBER |
| Unique ID of this issue. Use as Primary Key. |
| STRING | Base url of the current instance. | |
| STRING | Link/URL to the issue. | |
| STRING |
| Unique Key for this issue. |
| STRING |
| Key of the project this issue is in. |
| STRING |
| Name of the project this issue is in. |
| STRING |
| Type of the project this issue is in. |
| STRING |
| Assigned category for the project this issue is in. |
| STRING |
| Type of this issue (for example: task, bug, or epic) |
| STRING |
| Summary for the issue. |
| STRING |
| Description of the issue. Field is truncated to 2000 characters. |
| NUMBER |
| Unique identifier of the creator, regardless of directory. |
| STRING |
| Name of current creator. |
| NUMBER |
| Unique identifier of the reporter, regardless of directory. |
| STRING |
| Name of the reporter. |
| NUMBER |
| Unique identifier of the assignee, regardless of directory. |
| STRING |
| Name of assignee. |
| STRING |
| Current status of this issue. |
| STRING |
| Status category of the current status for this issue. |
| NUMBER |
| Shows the priority order. However, admins can change this which will result in non-deterministic priority orders. |
| STRING |
| Name of the priority for this issue. |
| STRING |
| The final status of an issue. Jira considers the workflow of an Issue complete once a value is present in the resolution field. |
| NUMBER |
| Number of watchers for this issue. |
| NUMBER |
| Number of votes for this issue. |
| DATE |
| UTC timezone creation date of this issue (ISO string). |
| DATE |
| UTC timezone resolution date of this issue (ISO string). |
| DATE |
| UTC timezone date that the issue was last updated (ISO string). |
| DATE |
| The issue's UTC timezone due date (ISO string). |
| NUMBER |
| Estimate time remaining from original estimate (requires time-tracking enabled). |
| NUMBER |
| Original estimate that was set (requires time-tracking enabled). |
| NUMBER |
| Amount of logged work (requires time-tracking enabled). Field is null if there is no time spent. |
| STRING[] |
| JSON array of label names. Field is null if there are no labels. |
| STRING[] |
| JSON array of component names. Field is null if there are no labels. |
| NUMBER |
| ID of the parent issue. Field is null if the issue is not a subtask. |
| STRING |
| A short description of the environment in which the issue occurred (for example, |
| STRING[] |
| JSON Array of Affected Version Names. Field is null if there are no labels. |
| STRING[] |
| JSON array of fix version names. Field is null if there are no labels. |
| STRING |
| Security level name. NOTE: This can change between data exports. |
Jira Software fields data schema
Jira Software fields data will be exported to
, and every custom field is displayed on a separate row. To map a custom field to its corresponding issue, use the issue_fields_job<job_id>_<timestamp>.csv
issue_id
from this file and find its matching ID
from the Issues file.
Any user-generated custom fields will not be exported.
Field | Type | Sample data | Description |
---|---|---|---|
| NUMBER |
| ID to link to the corresponding issue in Issues data schema . |
| STRING |
| Pre-defined IDs of the Jira Software fields. |
| STRING |
| Name of field. |
| NUMBER/STRING/JSON ARRAY |
| Value of field. |
The following Jira Software fields are non-epic issue fields:
Field ID | Sample data | Description |
---|---|---|
|
| Sprints that the issue is currently in or has been in. All date and times are formatted as an ISO string with UTC timezone. |
|
| ID of the epic linked to this issue. |
|
| Number of story points associated with this issue. |
The following Jira Software fields relate to epics:
Field ID | Sample data | Description |
---|---|---|
|
| Color of the epic. |
|
| Name of the epic. |
|
| Status of the epic. |