Jira is Atlassian's industry-leading project management and issue tracking platform, used by 300,000+ companies. It helps teams plan, track, and deliver work using agile methods like Scrum and Kanban, organizing work into projects, issues, sprints, and boards with powerful JQL search. The Jira Feeds connector provides multi-feed ELT access to issues, projects, users, boards, sprints, comments, and changelogs.
Power end-to-end data operations for your Jira Feeds API with Nexla. Our bi-directional Jira Feeds connector is purpose-built for Jira Feeds, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to Jira Feeds or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Jira Feeds workflows fast, secure, and fully governed.
Features
Type: API
SourceDestination
Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
Request optimization with intelligent batching, retry, and caching to minimize API calls and costs
The Jira Feeds connector uses Basic Authentication with an Atlassian API token. Before creating a credential in Nexla, you will need to gather the following information from your Jira Cloud account.
Your Jira Cloud site URL follows the format https://<your-company>.atlassian.net. This URL is visible in your browser whenever you are logged in to Jira Cloud. Note the full URL — you will enter it without a trailing slash when configuring the Nexla credential.
Rather than using your account password, Nexla authenticates using a personal API token. API tokens are scoped to your account and provide the same access permissions as your Jira account.
In the top navigation, click your profile avatar, then select Manage your account.
Select the Security tab in your account settings.
Under the API tokens section, click Create and manage API tokens.
Click the Create API token button.
Enter a descriptive label for the token in the Label field — for example, Nexla Integration — so you can identify its purpose later.
Click Create.
Copy the generated API token immediately and store it in a secure location such as a password manager.
Important
The API token is only shown once. Atlassian does not store the token value, and you cannot retrieve it again after dismissing the dialog. If you lose the token, you will need to revoke it and generate a new one.
The API token inherits the permissions of the Atlassian account that generated it. To ensure Nexla can access all required Jira data feeds, the account used to generate the token should have:
Browse Projects permission on all projects you want Nexla to access.
View Development Tools and View Read-Only Workflow permissions if you need to access certain agile data (boards and sprints).
Membership in the relevant Jira groups or project roles to view issues, components, versions, and users.
For broad ELT use cases, Atlassian recommends using a dedicated service account or integration account with appropriate project-level access rather than a personal user account.
After selecting the data source type, click the Add Credential tile to open the Add New Credential overlay.
Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.
This connector uses Basic Authentication, combining your Jira username (email address) with a personal API token. Nexla transmits these credentials over HTTPS using Base64 encoding as required by the Atlassian Cloud REST API.
Enter the full URL of your Jira Cloud instance in the JIRA Software URL field. This must be the complete base URL with no trailing slash.
Format: https://<your-company>.atlassian.net
Example: https://acme.atlassian.net
Enter the email address associated with your Atlassian account in the Username field. This is the email address you use to log in to Jira Cloud.
Enter the API token you generated in the Prerequisites section above in the API Token field. This token is used as the password component of Basic Authentication and authenticates Nexla's requests to the Jira Cloud REST API.
The API token is treated as a secret credential and is stored securely by Nexla. For security best practices, use a dedicated integration account rather than a personal account, and rotate your API token periodically.
Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source creation.
To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the Jira Feeds connector tile, then select the credential that will be used to connect to your Jira Cloud instance, and click Next; or, create a new Jira Feeds credential for use in this flow. Jira Feeds data sources are configured using pre-built feed templates that enable multi-object ELT extraction from Jira Cloud, with each feed type corresponding to a specific Jira object type; sources can also be configured manually to ingest data from any valid Jira REST API v3 endpoint.
Select the Jira object type from which this source will fetch data from the Endpoint pulldown menu. Available feed templates are listed in the expandable sections below. Click on a feed type to view details and configuration instructions.
Issues
Retrieves Jira issues from your instance using JQL (Jira Query Language). Issues are the core work items in Jira and include bugs, tasks, stories, epics, and any custom issue types defined in your projects. This feed uses the Jira Search API with paginated token-based pagination and supports both full and incremental sync strategies.
Select Issues from the Endpoint pulldown menu.
Optionally, enter a JQL filter in the Issue JQL Filter field to restrict which issues are returned. JQL (Jira Query Language) is Jira's built-in search syntax for filtering issues by any field. The default value fetches all issues ordered by ID:
Date-bounded: updated>="2024-01-01" order by updated ASC
Multiple projects: project in (PROJ1, PROJ2) order by id ASC
The issues feed returns fields including ID, key, summary, status, assignee, reporter, priority, issue type, project, created date, updated date, resolution date, due date, labels, components, fix versions, parent, subtasks, issue links, and resolution.
For incremental sync, configure the Incremental Sync Lookback Time field with the earliest date from which changes should be captured, in the format YYYY-MM-DD HH:MM (for example, 2024-01-01 00:00). Incremental runs will fetch issues updated on or after the cursor timestamp from the previous run.
JQL must be a bounded query to avoid timeout errors on large Jira instances. Always include an order by clause. For complete JQL syntax documentation, see the Atlassian JQL documentation.
Projects
Retrieves all Jira projects accessible to the authenticated account. Projects in Jira are containers that organize issues, boards, and team members. This feed uses the Jira Projects API with offset-based pagination (full sync only).
Select Projects from the Endpoint pulldown menu.
No additional configuration is required. The feed automatically retrieves all projects the authenticated user has Browse Projects permission to access.
Returned data includes project ID, key, name, description, project type, lead, and URL.
The number of projects returned depends on the permissions of the Jira account used in the Nexla credential. To access all projects in your Jira instance, use an account with Jira Administrator permissions or a service account with Browse Projects access to all projects.
Project Categories
Retrieves all project categories defined in your Jira instance. Project categories are labels used to group related projects together, and are managed by Jira administrators. This feed is a static (non-paginated) endpoint that returns all categories in a single request.
Select Project Categories from the Endpoint pulldown menu.
No additional configuration is required. All project categories visible to the authenticated account are returned automatically.
Returned data includes category ID, name, and description.
Issue Types
Retrieves all issue types defined in your Jira instance. Issue types classify the nature of a Jira issue—common examples include Bug, Task, Story, Epic, and Sub-task. Custom issue types created by your Jira administrator are also included. This is a static endpoint that returns all types in a single request.
Select Issue Types from the Endpoint pulldown menu.
No additional configuration is required. All issue types defined in the Jira instance are returned automatically.
Returned data includes issue type ID, name, description, icon URL, and whether the type is a subtask type.
Issue Priorities
Retrieves all issue priority levels defined in your Jira instance. Priorities indicate the urgency of a Jira issue—default levels include Highest, High, Medium, Low, and Lowest. This is a static endpoint that returns all priorities in a single request.
Select Issue Priorities from the Endpoint pulldown menu.
No additional configuration is required. All priorities are returned automatically.
Returned data includes priority ID, name, description, icon URL, and status color.
Statuses
Retrieves all workflow statuses defined in your Jira instance. Statuses represent the stages in a Jira workflow through which issues progress—common examples include To Do, In Progress, In Review, and Done. This is a static endpoint that returns all statuses in a single request.
Select Statuses from the Endpoint pulldown menu.
No additional configuration is required. All workflow statuses are returned automatically.
Returned data includes status ID, name, description, and the status category (To Do, In Progress, or Done).
Versions
Retrieves all versions (also called fix versions or releases) across all projects in your Jira instance. Versions are used to organize releases and track which issues are targeted for or resolved in a given release. This is a project-child feed that iterates over all projects to retrieve their associated versions.
Select Versions from the Endpoint pulldown menu.
No additional configuration is required. The feed automatically iterates over all accessible projects and retrieves their versions.
Returned data includes version ID, name, description, release date, released status, and archived status, along with the parent project key.
Components
Retrieves all components across all projects in your Jira instance. Components are sub-sections of a Jira project used to group issues into smaller parts, such as front-end, back-end, API, or documentation. This is a project-child feed that iterates over all projects to retrieve their components.
Select Components from the Endpoint pulldown menu.
No additional configuration is required. The feed automatically iterates over all accessible projects and retrieves their components.
Returned data includes component ID, name, description, lead, and the parent project key.
Fields
Retrieves all fields defined in your Jira instance, including both system fields and any custom fields created by your Jira administrator. This is useful for understanding your Jira schema and mapping field IDs to human-readable names. This is a static endpoint that returns all fields in a single request.
Select Fields from the Endpoint pulldown menu.
No additional configuration is required. All fields are returned automatically.
Returned data includes field ID, name, custom flag, orderable flag, navigable flag, searchable flag, and schema information.
Resolutions
Retrieves all resolution types defined in your Jira instance. Resolutions describe why an issue was closed—common examples include Fixed, Won't Fix, Duplicate, Cannot Reproduce, and Done. This is a static endpoint that returns all resolutions in a single request.
Select Resolutions from the Endpoint pulldown menu.
No additional configuration is required. All resolutions are returned automatically.
Returned data includes resolution ID, name, and description.
Issue Link Types
Retrieves all issue link types defined in your Jira instance. Issue link types define how issues can be related to one another—common examples include Blocks, Clones, Duplicates, and Relates to. This is a static endpoint that returns all link types in a single request.
Select Issue Link Types from the Endpoint pulldown menu.
No additional configuration is required. All issue link types are returned automatically.
Returned data includes link type ID, name, inward description, and outward description.
Users
Retrieves all users accessible to the authenticated account. This feed uses the Jira Users Search API with offset-based pagination and returns all users with access to the Jira instance. This is useful for building user dimension tables or mapping account IDs to user details.
Select Users from the Endpoint pulldown menu.
No additional configuration is required. The feed automatically paginates through all users in the Jira instance.
Returned data includes account ID, account type, display name, email address, and active status.
The Jira Users Search API requires the authenticated account to have Browse Users and Groups permission in Jira. Without this permission, the API may return an empty result or only the current user.
Boards
Retrieves all Jira boards (Scrum and Kanban) accessible to the authenticated account using the Jira Agile REST API. Boards are the primary interface for agile teams to visualize and manage their work. This feed uses the Agile API with offset-based pagination.
Select Boards from the Endpoint pulldown menu.
No additional configuration is required. All boards accessible to the authenticated account are returned automatically.
Returned data includes board ID, name, type (scrum or kanban), and location information.
Sprints
Retrieves all sprints from all Scrum boards accessible to the authenticated account. Sprints are time-boxed iterations used in Scrum methodology. This is a two-step feed: it first retrieves all Scrum boards, then iterates over each board to retrieve its sprints.
Select Sprints from the Endpoint pulldown menu.
No additional configuration is required. The feed automatically iterates over all Scrum boards and retrieves their sprints.
Returned data includes sprint ID, name, state (active, closed, or future), start date, end date, complete date, and the originating board ID.
Only Scrum board sprints are retrieved by this feed. Kanban boards do not use sprints and are not included in this feed's results.
Comments
Retrieves all comments from Jira issues matching a JQL filter. Comments are the discussion threads on Jira issues and contain the conversation history between team members. This is a two-step feed that first retrieves matching issues and then retrieves all comments for each issue. It supports both full and incremental sync strategies.
Select Comments from the Endpoint pulldown menu.
Optionally, enter a JQL filter in the Issue JQL Filter field to restrict which issues' comments are retrieved. This uses the same JQL syntax as the Issues feed. The default retrieves comments for all issues:
Specific project: project=MYPROJECT order by id ASC
For incremental sync, configure the Incremental Sync Lookback Time field to limit the issues iterated to those updated since a given timestamp. This significantly reduces the number of API calls required in incremental runs.
Returned data includes comment ID, author account ID, created date, updated date, and the comment body in Atlassian Document Format (ADF).
Changelogs
Retrieves the full audit history of changes to Jira issues matching a JQL filter. Each changelog record represents a single field change on an issue, including who made the change, when it was made, and what the field value was before and after the change. This is a two-step feed and supports both full and incremental sync strategies.
Select Changelogs from the Endpoint pulldown menu.
Optionally, enter a JQL filter in the Issue JQL Filter field to restrict which issues' changelogs are retrieved:
Specific project: project=MYPROJECT order by id ASC
For incremental sync, configure the Incremental Sync Lookback Time field to limit the issues iterated.
Returned data includes changelog ID, the issue it belongs to, author account ID, created timestamp, and an array of items describing each field that changed (field name, field type, from value, and to value).
Changelog data is valuable for auditing workflows, tracking SLA compliance, and analyzing how issues move through your Jira workflow stages over time.
Remote Issue Links
Retrieves all remote links associated with Jira issues. Remote links connect Jira issues to external resources such as Confluence pages, GitHub pull requests, or other web URLs. This is a static two-step feed that retrieves all issues (regardless of date) and then retrieves remote links for each.
Select Remote Issue Links from the Endpoint pulldown menu.
No additional configuration is required. The feed automatically iterates over all issues and retrieves their remote links.
Returned data includes the remote link ID, URL, title, and the parent issue ID.
Issue Boards
Retrieves all issues currently on each Jira board, for every board accessible to the authenticated account. This is a two-step feed that first retrieves all boards and then retrieves the issues associated with each board (returning only the issue ID and key). Use this feed to understand which issues are assigned to which boards.
Select Issue Boards from the Endpoint pulldown menu.
No additional configuration is required. The feed automatically iterates over all boards and retrieves their associated issues.
Returned data includes issue ID, issue key, and the parent board ID.
Project Boards
Retrieves all projects associated with each Jira board, for every board accessible to the authenticated account. This is a two-step feed that first retrieves all boards and then retrieves the project records associated with each board. Use this feed to create a mapping between boards and their associated projects.
Select Project Boards from the Endpoint pulldown menu.
No additional configuration is required. The feed automatically iterates over all boards and retrieves their associated projects.
Returned data includes project details and the parent board ID.
The Jira Feeds connector supports two sync strategies, selectable during data source configuration:
Full Ingest: Retrieves all data from Jira on each run. Supported for all feed types. Use this strategy for reference data feeds (Projects, Fields, Statuses, etc.) or when you need a complete snapshot of Jira data.
Incremental Sync: Retrieves only records updated since the last successful run. Supported for Issues, Comments, and Changelogs. Use this strategy for high-volume Jira instances where full scans are impractical or slow. Configure the Incremental Sync Lookback Time field with the starting timestamp, in the format YYYY-MM-DD HH:MM (for example, 2024-01-01 00:00); on the first incremental run, Nexla fetches records updated on or after this timestamp, and on subsequent runs automatically tracks the cursor from the last successful run.
Once the selected feed template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.
Jira Feeds data sources can also be manually configured to ingest data from any valid Jira Cloud REST API v3 endpoint, including endpoints not covered by the pre-built feed templates. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers.
The Jira REST API v3 base URL follows the format https://<your-company>.atlassian.net/rest/api/3/ (for example, https://mycompany.atlassian.net/rest/api/3/issue/search); the Jira Agile REST API v1 is available at https://<your-company>.atlassian.net/rest/agile/1.0/ (for example, https://mycompany.atlassian.net/rest/agile/1.0/board). Date/time macros such as {now-7} are useful for filtering JQL search endpoints by date range. For Path to Data, use $.issues[*] for the Issues search endpoint, $.values[*] for paginated list endpoints (projects, boards, sprints), and $[*] for static list endpoints (fields, statuses, resolutions); top-level fields like total, startAt, and maxResults can be captured as Metadata using $. For the complete endpoint reference, see the Atlassian Jira Cloud REST API documentation.
Once all of the relevant settings have been configured, click the Create button in the upper right corner of the screen to save and create the new Jira Feeds data source. Nexla will now begin ingesting data from the configured Jira feeds and will organize any data that it finds into one or more Nexsets.
