Jira Feeds

Jira is Atlassian's project management and issue tracking platform, used by teams to plan, track, and release work with agile Scrum and Kanban workflows. The Jira Feeds connector is a source-only ELT connector that ingests core Jira objects — issues, projects, project categories, issue types, priorities, and statuses — from the Jira Cloud REST API v3. Nexla discovers the objects available in your Jira site, then full-refreshes each selected feed on a schedule.

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

Prerequisites

The Jira Feeds connector uses Basic Authentication with an Atlassian API token. Before creating a credential in Nexla, gather your Jira Cloud site URL, your Atlassian account email, and an API token.

Your Jira Cloud URL

Your Jira Cloud site URL follows the format https://<your-company>.atlassian.net. This URL is visible in your browser whenever you are signed in to Jira Cloud. Note the full URL — enter it without a trailing slash when configuring the Nexla credential.

Your Jira Username

Your username is the email address associated with your Atlassian account. This is the same address you use to sign in to Jira Cloud.

Generate an Atlassian API Token

Rather than using your account password, Nexla authenticates using a personal API token. The token is used as the password component of Basic Authentication, with your email address as the username.

To generate an API token:

1. Sign in to your Atlassian account and go to the API token management page at https://id.atlassian.com/manage-profile/security/api-tokens.

2. Click Create API token (or Create API token with scopes for a scoped, more restricted token).

3. Enter a descriptive label for the token — for example, Nexla Integration — so you can identify its purpose later.

4. Select an expiration for the token. Atlassian API tokens can be set to expire between 1 and 365 days.

5. Click Create.

6. Copy the generated 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, revoke it and generate a new one.

The API token inherits the permissions of the Atlassian account that generated it. To ensure Nexla can read all of your projects and issues, use an account with Browse Projects permission on the relevant projects — or a dedicated integration account with appropriate project access. For more information, see the Atlassian support documentation on managing API tokens.

For more information on the Jira Cloud REST API, see the Atlassian Jira Cloud REST API documentation.

Authenticate

Credentials required

Use your JIRA API Token for authentication.

Field	Required	Secret	Description
JIRA Software URL	Yes	No	The JIRA API url used to access your account. Ex: https://mycompany.atlassian.net
Username	Yes	No	Your username for accessing your JIRA instance.
API Token	Yes	Yes	Your REST API Token for accessing your JIRA instance.

Create a credential in Nexla

1. After selecting the data source type, click the Add Credential tile to open the Add New Credential overlay.

2. 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 as required by the Atlassian Cloud REST API.

3. 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

4. Enter the email address associated with your Atlassian account in the Username field. This is the email address you use to sign in to Jira Cloud.

5. 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.

6. 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.

Use as a data source

How This Connector Works

The Jira Feeds connector is a source-only, whole-catalog ELT connector. Rather than configuring one endpoint at a time, you select the Jira objects you want from a single catalog of feeds, and Nexla ingests each selected object as its own feed from the Jira Cloud REST API v3.

• Discovery: When you create the source, Nexla discovers the Jira objects available from your site and presents them for selection.

• Full refresh: Each selected feed is ingested using a full-refresh strategy, so every run reads the complete current set of records for that object. The id field is used as the primary key to uniquely identify records within each feed.

• Parallel ingestion: Selected feeds are ingested in parallel, so a single source can pull multiple Jira objects on the same schedule.

Create a New Data Flow

1. To create a new data flow, navigate to the Integrate section, click the New Data Flow button, select the ELT flow type, and click Create.

2. Select the Jira Feeds connector tile from the list of available connectors. 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.

Select the Objects to Ingest

After authenticating, Nexla lists the Jira objects available from the connector. Select one or more of the following objects to ingest. Each selected object becomes its own feed and is full-refreshed on the configured schedule.

Issues

Retrieves Jira issues from your instance. 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 reads from the Jira search API and paginates automatically to ingest all matching issues.

• Select Issues from the list of objects to ingest.
• Nexla paginates through the results automatically, reading the complete set of issues on each full-refresh run.

Projects

Retrieves the Jira projects accessible to the authenticated account. Projects are containers that organize issues and team members.

• Select Projects from the list of objects to ingest.
• The number of projects returned depends on the permissions of the account used in the Nexla credential. To access all projects, use an account with Browse Projects permission on those projects.

Project Categories

Retrieves the project categories defined in your Jira instance. Project categories are labels used to group related projects together, and are managed by Jira administrators.

• Select Project Categories from the list of objects to ingest.
• All project categories visible to the authenticated account are returned in a single request.

Issue Types

Retrieves the issue types defined in your Jira instance. Issue types classify the nature of an issue — common examples include Bug, Task, Story, Epic, and Sub-task. Custom issue types created by your Jira administrator are also included.

• Select Issue Types from the list of objects to ingest.
• All issue types defined in the Jira instance are returned in a single request.

Issue Priorities

Retrieves the issue priority levels defined in your Jira instance. Priorities indicate the urgency of an issue — default levels include Highest, High, Medium, Low, and Lowest.

• Select Issue Priorities from the list of objects to ingest.
• All priorities are returned in a single request.

Statuses

Retrieves the 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.

• Select Statuses from the list of objects to ingest.
• All workflow statuses are returned in a single request.

Feeds are ingested with a full-refresh strategy. Paginated objects (such as Issues) are read page by page until all records are retrieved, while reference objects (such as Projects, Issue Types, Priorities, and Statuses) are returned in a single request. In every case, each run reads the complete current set of records for the selected object.

Schedule and Activate

Use the default sync schedule or adjust the schedule in the source settings before activating the flow. On each run, every selected feed is full-refreshed, and Nexla organizes the ingested data into one or more Nexsets.

Reference

For object schemas, field definitions, and additional detail on each Jira endpoint, see the Atlassian Jira Cloud REST API documentation.