Skip to main content
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. Jira

​
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.
Base project entities used by other project-scoped streams.Primary key:
  • id
Key Fields:
  • key - Project key used as Jira identifier
  • name - Project name
  • project_type_key - Project type
  • is_private - Project visibility flag
  • project_category - Project category metadata
  • insight.total_issue_count - Total number of issues
Agile boards associated with projects.Primary key:
  • id
Parent stream:
  • projects (filtered by project context)
Key Fields:
  • name - Board name
  • type - Board type (scrum, kanban, etc.)
  • location.project_id - Related project ID
  • location.project_key - Related project key
  • location.project_name - Related project name
Sprint entities collected from agile boards.Replication key:
  • id
Parent stream:
  • boards (only boards with type scrum)
Key Fields:
  • state - Sprint state
  • name - Sprint name
  • start_date - Sprint start date
  • end_date - Sprint end date
  • complete_date - Completion date
  • board_id - Parent board ID
  • goal - Sprint goal
Issue type definitions available per project.Primary key:
  • id
Parent stream:
  • projects (filtered by project context)
Key Fields:
  • name - Issue type name
  • description - Issue type description
  • subtask - Whether the type is a subtask
  • hierarchy_level - Hierarchy level in Jira
  • scope.project.id - Project-scoped type project ID
  • scope.project.key - Project-scoped type project key
Field definitions and metadata available for projects.Primary key:
  • id
Parent stream:
  • projects (filtered by project context)
Key Fields:
  • key - Field key
  • name - Field name
  • custom - Whether the field is custom
  • orderable - Whether the field can be used in ordering
  • searchable - Whether the field can be searched
  • schema.type - Data type for field values
  • schema.custom - Custom schema identifier
Jira users available to the authenticated account.Primary key:
  • account_id
Key Fields:
  • display_name - User display name
  • email_address - User email
  • account_type - Account type
  • active - Whether the user is active
  • time_zone - User time zone
  • locale - User locale
Main issue entities with detailed nested fields from Jira.Primary key:
  • id
Replication key:
  • updated
Key Fields:
  • key - Issue key
  • created - Issue creation timestamp
  • updated - Last update timestamp
  • fields.summary - Issue summary
  • fields.status - Current issue status
  • fields.issuetype - Issue type details
  • fields.project - Parent project details
  • fields.assignee - Assignee details
  • fields.reporter - Reporter details
  • fields.labels - Labels array
Change history for each issue.Primary key:
  • id
Replication key:
  • created
Parent stream:
  • issues
Key Fields:
  • issue_id - Parent issue ID
  • author.account_id - Author account ID
  • created - Changelog creation timestamp
  • items.field - Changed field
  • items.from - Previous value ID
  • items.to - New value ID
  • items.from_string - Previous value (display)
  • items.to_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 always applies an updated >= start_date filter, and can additionally apply a custom JQL query.
  • The final JQL for issues combines start date, 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.