_SvIncludePlusContent-_DP_Schema_Issues_Jira

_SvIncludeLibrary

On this page

Still need help?

The Atlassian Community is here for you.

Ask the community

All data relating to issues will be exported to issues CSV file. 

FieldDescription
id (Primary Key)

Type: Number

Description: Unique ID of this issue. Use as Primary Key.

Example: 10002

instance_url

Type: String

Description: Base url of the current instance

Example: http://www.example.com/jira

url

Type: String

Description: URL of the issue

Example: http://www.example.com/jira/browse/TEST-1002

key

Type: String

Description: Unique Key for this issue

Example: TEST-1002

project_key

Type: String

Description: Key of the project this issue is in

Example: TEST

project_name

Type: String

Description: Title of the project this issue is in

Example: Sample Test Project

project_type

Type: String

Description: Type of the project this issue is in (can be Business, Software, Service Desk)

Example: Software

project_category

Type: String

Description: Assigned category for the project this issue is in

Example: Sample Project Category

issue_type

Type: String

Description: Type of issue (for example, task, bug, or epic)

Example: Task

summary

Type: String

Description: Summary of the issue

Example: Sample issue

description

Type: String

Description: Description of the issue (limited to 2000 characters)

Example: This is a sample issue for demo purposes.

creator_id

Type: Number

Description: Unique identifier of the user who created the issue, regardless of directory

Example: 10000

creator_name

Type: String

Description: Name of the user issue creator

Example: Alana Grant

Schema: Version 1 only. This data is now contained in the Users file.

reporter_id

Type: Number

Description: Unique identifier of the issue reporter, regardless of directory

Example: 10001

reporter_name

Type: String

Description: Name of the issue reporter

Example: Omar Darboe

Schema: Version 1 only. This data is now contained in the Users file.

assignee_id

Type: Number

Description: Unique identifier of the issue assignee, regardless of directory

Example: 10002

assignee_name

Type: String

Description: Name of the issue assignee

Example: Jie Yang Song

Schema: Version 1 only. This data is now contained in the Users file.

status

Type: String

Description: Current status of this issue

Example: Not Started

status_category

Type: String

Description: Status category for the current status for this issue

Example: In Progress

priority_sequence

Type: String

Description: The priority order (admins can change this which will result in non-deterministic priority orders)

Example: 3

priority_name

Type: String

Description: Name of the priority for this issue

Example: Medium

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: Done

watcher_count

Type: Number

Description: Number of users watching this issue

Example: 5

vote_count

Type: Number

Description: Number of votes for this issue

Example: 4

created_date

Type: Date

Description: UTC timezone creation date of this issue (ISO string)

Example: 2020-11-05T14:44:57Z

resolution_date

Type: Date

Description: UTC timezone resolution date of this issue (ISO string)

Example: 2020-11-05T14:44:57Z

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: 2020-11-05T14:44:57Z

estimate

Type: Number

Description: Estimate time remaining from original estimate, in seconds (requires time-tracking enabled)

Example: 5000

original_estimate

Type: Number

Description: Original estimate that was set, in seconds (requires time-tracking enabled)

Example: 2000

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: 4000

labels

Type: String

Description: JSON array of label names. Field is null if there are no labels.

Example: ["test-label", "test2-label”]

components

Type: String

Description: JSON array of component names. Field is null if there are no labels.

Example: ["component_a", "component_b"]

parent_id

Type: Number

Description: ID of the parent issue. Field is null if the issue is not a subtask.

Example: 10001

environment

Type: String

Description: A short description of the environment in which the issue occurred (for example, IE9 on Windows 7). This field has a limit of 2000 characters

Example: "linux”

affected_versions

Type: String

Description: JSON Array of Affected Version Names. Field is null if there are no labels.

Example: ["a_version_1", "a_version_2"]

fix_versions

Type: String

Description: JSON array of fix version names. Field is null if there are no labels.

Example: ["f_version_1", "f_version_2"]

security_level

Type: String

Description: Security level name. NOTE: This can change between data exports.

Example: staff-only

archived_by_user_id

Type: Number

Description: Unique identifier of the user who archived the issue, regardless of directory.

Example: 10002

Schema: Version 1 and later (requires Jira 8.19 or later)

archived_date

Type: Date

Description: UTC timezone date this issue was archived (ISO string).

Example: 2020-11-05T14:44:57Z

Schema: Version 1 and later (requires Jira 8.19 or later)

Last modified on Jan 7, 2026

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.