Data pipeline export schema
Issues data schema
issues_job<job_id>_<timestamp>.csv. | Field | Description |
|---|---|
id (Primary Key) | Type: Number Description: Unique ID of this issue. Use as Primary Key. Example: |
| instance_url | Type: String Description: Base url of the current instance Example: |
| url | Type: String Description: URL of the issue Example: |
| key | Type: String Description: Unique Key for this issue Example: |
| project_key | Type: String Description: Key of the project this issue is in Example: |
| project_name | Type: String Description: Title of the project this issue is in Example: |
| project_type | Type: String Description: Type of the project this issue is in (can be Business, Software, Service Desk) Example: |
| project_category | Type: String Description: Assigned category for the project this issue is in Example: |
| issue_type | Type: String Description: Type of issue (for example, task, bug, or epic) Example: |
| summary | Type: String Description: Summary of the issue Example: |
| description | Type: String Description: Description of the issue (limited to 2000 characters) Example: |
| creator_id | Type: Number Description: Unique identifier of the user who created the issue, regardless of directory Example: |
| creator_name | Type: String Description: Name of the user issue creator Example: |
| reporter_id | Type: Number Description: Unique identifier of the issue reporter, regardless of directory Example: |
| reporter_name | Type: String Description: Name of the issue reporter Example: |
| assignee_id | Type: Number Description: Unique identifier of the issue assignee, regardless of directory Example: |
| assignee_name | Type: String Description: Name of the issue assignee Example: |
| status | Type: String Description: Current status of this issue Example: |
| status_category | Type: String Description: Status category for the current status for this issue Example: |
| priority_sequence | Type: String Description: The priority order (admins can change this which will result in non-deterministic priority orders) Example: |
| priority_name | Type: String Description: Name of the priority for this issue Example: |
| resolution | Type: String Description: The final status of an issue. Jira considers the workflow of an Issue complete once a value is present in the resolution field. Example: |
| watcher_count | Type: Number Description: Number of users watching this issue Example: |
| vote_count | Type: Number Description: Number of votes for this issue Example: |
| created_date | Type: Date Description: UTC timezone creation date of this issue (ISO string) Example: |
| resolution_date | Type: Date Description: UTC timezone resolution date of this issue (ISO string) Example: |
| updated_date | Type: Date Description: UTC timezone date that this issue was last updated (ISO string) Example: 2020-11-05T14:44:57Z |
| due_date | Type: Date Description: UTC timezone date that this issue is due to be completed (ISO string) Example: |
| estimate | Type: Number Description: Estimate time remaining from original estimate, in seconds (requires time-tracking enabled) Example: |
| original_estimate | Type: Number Description: Original estimate that was set, in seconds (requires time-tracking enabled) Example: |
| time_spent | Type: Number Description: Amount of logged work, in seconds (requires time-tracking enabled). Field is null if there is no time spent. Example: |
| labels | Type: String Description: JSON array of label names. Field is null if there are no labels. Example: |
| components | Type: String Description: JSON array of component names. Field is null if there are no labels. Example: |
| parent_id | Type: Number Description: ID of the parent issue. Field is null if the issue is not a subtask. Example: |
| environment | Type: String Description: A short description of the environment in which the issue occurred (for example, Example: |
| affected_versions | Type: String Description: JSON Array of Affected Version Names. Field is null if there are no labels. Example: |
| fix_versions | Type: String Description: JSON array of fix version names. Field is null if there are no labels. Example: |
| security_level | Type: String Description: Security level name. NOTE: This can change between data exports. Example: |
Data schema for Jira Software and Jira Service Management fields
issue_fields_job<job_id>_<timestamp>.csv, and every custom field is displayed on a separate row. To map a custom field to its corresponding issue, use the issue_id from this file and find its matching ID from the Issues file.
User-generated custom fields are not exported.
| Field | Description |
|---|---|
| issue_id | Type: Number Description: ID to link to the corresponding issue in Issues data schema. Example: |
| field_id | Type: String Description: Pre-defined IDs of the Jira Software and Jira Service Management fields. Example: |
| field_name | Type: String Description: Name of the field Example: |
| field_value | Type: Number, String, JSON array Description: Value of the field Examples: |
| The following Jira Software fields relate to non-epic issues. | |
| sprint | Type: JSON 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. Example: |
| epic_link_id | Type: Number Description: ID of the epic linked to this issue Example: |
| story_points | Type: Number Description: Number of story points associated with this issue Example: |
| The following Jira Software fields relate to epics | |
| epic_color | Type: String Description: Color of the epic Example: |
| epic_name | Type: String Description: Name of the epic Example: |
| epic_status | Type: String Description: Status of the epic Example: |
| The following fields relate to Jira Service Management | |
| customer_request_type | Type: String Description: Customer Request Type for a JSM Customer Request Example: |
| organizations | Type: String Description: List of organizations assigned to a given JSM Issue. Organizations are entities that admins can organize customers into. Example: ["org1", "org2"] |
| request_participants | Type: Number Description: List of users assigned as request participants for a given JSM Issue Example: |
| satisfaction_comment | Type: String Description: Comment given as part of a JSM Issue Satisfaction survey Example: |
| satisfaction_rating | Type: String Description: Rating given as part of a JSM Issue Satisfaction survey Example: |
| satisfaction_scale | Type: String Description: Scale (max rating) the given satisfaction rating is based upon Example: |
| satisfaction_date | Type: Date Description: Date the Satisfaction survey was completed Example: |
SLA Cycle data schema (for Jira Service Management only)
sla_cycles_job<job_id>_<timestamp>.csv. Each issue can have multiple SLAs, where each SLA cycle (Ongoing and/or Completed) is displayed on a separate row. To map an SLA to its corresponding issue, use the issue_id from this file and find its matching ID from the Issues file.| Field | Description |
|---|---|
| issue_id | Type: Number Description: ID to link to the corresponding issue in Issues data schema Example: |
| sla_id | Type: Number Description: ID of the SLA of which the SLA cycle belongs to Example: |
| sla_name | Type: String Description: Name of the SLA of which the cycle belongs to. Example: |
| cycle_type | Type: String Description: Whether current SLA cycle is Example: |
| start_time | Type: Date Description: Timestamp of when the SLA cycle started Example: |
| stop_time | Type: Date Description: Timestamp of when the SLA cycle transitioned from Example: |
| paused | Type: Boolean Description: Notes whether the SLA cycle is paused or not. Can be true, false, or empty. Only available for Example: |
| remaining_time | Type: Number Description: Represents the time (in milliseconds) remaining before the expected SLA limit is breached. Remaining times are calculated and updated every 30 minutes. Therefore, the outputted value may not represent the actual current remaining time. Example: |
| elapsed_time | Type: Number Description: Represents the time (in milliseconds) that has passed since the SLA cycle started. Example: |
| goal_duration | Type: Number Description: Represents time (in milliseconds) taken to complete the current cycle. Only available for Example: |