Jira is Atlassian’s project management and issue tracking platform designed for software development teams. It provides tools for agile project management, bug tracking, and workflow automation to help teams plan, track, and release software efficiently.

Configuring Jira as a Source

In the Sources tab, click on “Add source” and select Jira from the list of connectors. Click Next and follow the setup steps below.

1. Add account access

Use your Jira Cloud credentials and workspace information. If needed, check Jira’s REST API documentation. The following configurations are available:

API token: The token used to authenticate against Jira. For instructions on generating it, check Atlassian’s guide.
User email: The email address associated with the API token.
Workspace domain: Your Jira domain, without https:// (for example, company.atlassian.net).
Start date: The earliest timestamp used for incremental extraction.
Project keys: Optional list of project keys to scope extraction. When defined, project-dependent streams are filtered to those projects.
Issues stream JQL query: Optional custom JQL filter for the issues stream. It is combined with the start date filter and project filter.

Once you’re done, click Next.

2. Select streams

Choose which Jira streams you want to sync. For faster extractions, select only the streams required for your use case.

Tip: You can search for a stream by typing its name.

Select the streams and click Next.

3. Configure data streams

Customize how each stream table will be created in your Catalog:

Layer: Select where the tables will be created.
Folder: Optionally group generated tables under a folder.
Table name: Use suggested names or customize them (you can apply a prefix to all tables).
Sync Type: Choose INCREMENTAL or FULL_TABLE according to your data strategy.

Once you finish this step, click Next.

4. Configure data source

Add a source name and description for your team, then define a Trigger frequency. Optionally, configure:

Delta Log Retention: How long old table states should be retained. Learn more here.
Additional Full Sync: Optional periodic full refresh to complement incremental runs.

When ready, click Next to complete the setup.

5. Check your new source

After setup, you can monitor runs in Sources. Once at least one run succeeds, the resulting tables become available in Catalog.

For you to be able to see the extracted tables on your Catalog, you need at least one successful source run.

Streams and Fields

Below you’ll find all available data streams from Jira and their corresponding key fields.

Projects

Base project entities used by other project-scoped streams.Primary key:

id

Key Fields:

Field	Type	Description
`key`	String	Project key used as Jira identifier
`name`	String	Project name
`project_type_key`	String	Project type
`is_private`	Boolean	Project visibility flag
`project_category`	Object	Project category metadata
`insight.total_issue_count`	Integer	Total number of issues

Boards

Agile boards associated with projects.Primary key:

id

Parent stream:

projects (filtered by project context)

Key Fields:

Field	Type	Description
`name`	String	Board name
`type`	String	Board type (`scrum`, `kanban`, etc.)
`location.project_id`	String	Related project ID
`location.project_key`	String	Related project key
`location.project_name`	String	Related project name

Sprints

Sprint entities collected from agile boards.Replication key:

id

Parent stream:

boards (only boards with type scrum)

Key Fields:

Field	Type	Description
`state`	String	Sprint state
`name`	String	Sprint name
`start_date`	String	Sprint start date
`end_date`	String	Sprint end date
`complete_date`	String	Completion date
`board_id`	String	Parent board ID
`goal`	String	Sprint goal

Issue Types

Issue type definitions available per project.Primary key:

id

Parent stream:

projects (filtered by project context)

Key Fields:

Field	Type	Description
`name`	String	Issue type name
`description`	String	Issue type description
`subtask`	Boolean	Whether the type is a subtask
`hierarchy_level`	Integer	Hierarchy level in Jira
`scope.project.id`	String	Project-scoped type project ID
`scope.project.key`	String	Project-scoped type project key

Fields

Field definitions and metadata available for projects.Primary key:

id

Parent stream:

projects (filtered by project context)

Key Fields:

Field	Type	Description
`key`	String	Field key
`name`	String	Field name
`custom`	Boolean	Whether the field is custom
`orderable`	Boolean	Whether the field can be used in ordering
`searchable`	Boolean	Whether the field can be searched
`schema.type`	String	Data type for field values
`schema.custom`	String	Custom schema identifier

Users

Jira users available to the authenticated account.Primary key:

account_id

Key Fields:

Field	Type	Description
`display_name`	String	User display name
`email_address`	String	User email
`account_type`	String	Account type
`active`	Boolean	Whether the user is active
`time_zone`	String	User time zone
`locale`	String	User locale

Issues

Main issue entities with detailed nested fields from Jira.Primary key:

id

Replication key:

updated

Key Fields:

Field	Type	Description
`key`	String	Issue key
`created`	String	Issue creation timestamp
`updated`	String	Last update timestamp
`fields.summary`	String	Issue summary
`fields.status`	Object	Current issue status
`fields.issuetype`	Object	Issue type details
`fields.project`	Object	Parent project details
`fields.assignee`	Object	Assignee details
`fields.reporter`	Object	Reporter details
`fields.labels`	Array	Labels array

Issue Changelog

Change history for each issue.Primary key:

id

Replication key:

created

Parent stream:

issues

Key Fields:

Field	Type	Description
`issue_id`	String	Parent issue ID
`author.account_id`	String	Author account ID
`created`	String	Changelog creation timestamp
`items.field`	String	Changed field
`items.from`	String	Previous value ID
`items.to`	String	New value ID
`items.from_string`	String	Previous value (display)
`items.to_string`	String	New value (display)

Data Model

The following diagram shows the relationship between the main Jira streams.

Implementation Notes

Filtering behavior

project_keys limits project-scoped extraction to specific Jira projects.
issues applies an updated >= start_date filter if a starting timestamp is available, and can additionally apply a custom JQL query.
The final JQL for issues combines the start date (if present), optional project keys, and optional custom JQL with logical and.

Stream hierarchy behavior

boards, fields, and issue_types are project-scoped child streams.
sprints is collected only from scrum boards.
issue_changelog is collected per issue and includes issue_id as parent context.

Skills for agents

Download Jira skills file

Jira connector documentation as plain markdown, for use in AI agent contexts.

Documentation

Get started

Using Nekt

Workspace

Resources

Jira as a data source

Configuring Jira as a Source

1. Add account access

2. Select streams

3. Configure data streams

4. Configure data source

5. Check your new source

Streams and Fields

Data Model

Implementation Notes

Filtering behavior

Stream hierarchy behavior

Skills for agents

Download Jira skills file

Documentation

Get started

Using Nekt

Workspace

Resources

Documentation Index

​Configuring Jira as a Source

​1. Add account access

​2. Select streams

​3. Configure data streams

​4. Configure data source

​5. Check your new source

​Streams and Fields

​Data Model

​Implementation Notes

​Filtering behavior

​Stream hierarchy behavior

​Skills for agents

Download Jira skills file

Configuring Jira as a Source

1. Add account access

2. Select streams

3. Configure data streams

4. Configure data source

5. Check your new source

Streams and Fields

Data Model

Implementation Notes

Filtering behavior

Stream hierarchy behavior

Skills for agents