JIRA connector icon

JIRA Connector

Embed in-app Jira workflows at scale — create and update issues, surface project data and automate ticketing directly inside your SaaS product using Cyclr’s low-code builder and publish integrations to your customers.

01

Faster time to market

Ship integrations without building backend connectors.

02

Reduce maintenance

Centralize auth, retries and rate-limit handling.

03

Governed MCP tools

Expose approved Jira actions as managed, versioned MCP tools.

04

Embedded experience

Deliver customer-facing workflows natively inside your SaaS product.

CONNECTOR OVERVIEW

Overview

Cyclr’s JIRA connector lets product and engineering teams embed customer-facing Jira integrations — issue creation, search, project and board reads, and webhook-driven automation — into multi-tenant SaaS apps. Build orchestrations, map and transform data between systems, and expose selected actions as governed MCP tools without shipping bespoke integration code.

PRODUCT USE CASES

Top Use Cases for JIRA Integrations

Build customer-facing automations that create issues from app events, sync ticket status, embed issue creators and surface project data for reporting — all publishable through Cyclr’s embedded integration marketplace.

Create Jira issues from product events

Automatically open Jira issues when app alerts, error logs or user reports occur, with mapped context and attachments.

Sync ticket status and comments

Keep status, priority and comments in sync between your app and Jira for consistent cross-system workflows.

In-app issue creation and search

Embed an issue creator, issue picker and JQL-based search directly inside your product UI for end users.

ORCHESTRATION

How JIRA works with Cyclr

Cyclr sits between your SaaS product and JIRA to handle authentication, govern access and orchestrate every API call per customer, at scale.

  1. 1

    Your SaaS product

    Your app requests an action for a specific customer.

  2. 2

    Cyclr orchestration

    Cyclr authenticates, applies policies and routes the request.

  3. 3

    JIRA

    JIRA processes the request and returns a response to your app.

Customer-specific authentication · Governed data movement · Centralized visibility and audit

CONNECTOR COVERAGE

Available connector capabilities

Explore JIRA methods you can orchestrate through Cyclr.

Issues (Custom Fields - Object Name format: Project ID, Issue Type ID. (i.e. 10001,10009))8

Create Issue

Action

Creates a new Issue.

Get Issue

Action

Returns details of an issue for a given ID.

List Updated Issues

Action

List all issues updated since the last successful run.

List Issues By Project/Issue Type

Action

List all issues attached to this project and issue type.

List New Issues

Action

List all issues created since the last successful run.

List Issues

Action

List all issues in the project.

List New And Updated Issues

Action

Lists all issues created or updated since the last successful run.

Get Satisfaction Comment

Action

Returns (where available) the comment left with a satisfaction rating for an issue.

Worklogs5

Get Worklog

Action

Retrieve a worklog by issue ID and worklog ID.

List Updated Worklogs IDs

Action

List ID's for worklogs that have been updated since last run.

Add Worklog

Action

Adds a worklog to an issue.

List Worklogs

Action

Returns a list of the specified worklogs.

Update Worklog

Action

Updates a worklog to for an issue.

Webhooks5

Update Webhook

Action

Update a webhook.

Get Webhook

Action

Get a webhook specified by ID.

Create Webhook

Action

Create a webhook.

List Webhooks

Action

List all webhooks.

Delete Webhook

Action

Delete a webhook.

Projects4

Create Project

Action

Create a project in this JIRA account.

List Projects

Action

List all projects.

Get Project

Action

Get details of a project, by passing its ID or Key.

(DEPRECATED) List Projects

Action

List all projects which are visible for the currently logged in user. If no user is logged in, it returns the list of projects that are visible when using anonymous access.

Metadata2

List Issue Create Metadata

Action

Lists all meta data for creating an issue.

Get Issue Edit Metadata

Action

Returns meta data for the issue.

Assets7

Get Object

Action

Returns the details of a single Object.

Create Object

Action

Creates a new Object in Assets.

List Objects

Action

List all Objects in Assets with a Status of 'Active'.

Update Object

Action

Update an existing Object in Assets.

List New Objects

Action

List all Objects in Assets with a Status of 'Active' created since the last successful run.

List Updated Objects

Action

List all Objects in Assets with a Status of 'Active' updated since the last successful run.

Delete Object

Action

Delete the referenced Object.

Dashboards2

Get Dashboard

Action

Returns details of the requested Dashboard.

List Dashboards

Action

Returns a list of all Dashboards.

Sprints5

Sprint Updated Webhook

Webhook

Triggered whenever a sprint is updated.

Get Sprint

Action

Get a sprint by ID.

Sprint Created Webhook

Webhook

Triggered whenever a sprint is created.

Create Sprint

Action

Create a future sprint.

Update Sprint

Action

Updates a sprint.

Issue Worklogs4

List Updated Issue Worklogs

Action

List all worklogs for an issue updated since the last successful run.

List Issue Worklogs

Action

List all worklogs for an issue.

List New Issue Worklogs

Action

List all worklogs for an issue created since the last successful run.

List Started Issue Worklogs

Action

List all worklogs for an issue started since the last successful run.

Issues26

Issue Updated Webhook

Webhook

Triggered whenever an issue is updated.

List Updated Issues

Action

List all issues updated since the last successful run.

List New Issues

Action

List all issues created since the last successful run.

List New And Updated Issues

Action

Lists all issues created or updated since the last successful run.

Get Project Issue Types

Action

Returns a list of all issue types for a project that are visible to the user.

Get Issue

Action

Returns details of an issue for a given ID.

Issue Created Webhook

Webhook

Triggered whenever an issue is created.

List Issue Types

Action

Lists all issue types visible to the user.

Update Issue

Action

Update an issue.

Delete Issue

Action

Deletes the specified issue.

Create Issue

Action

Creates a new Issue.

List Possible Transitions for Issue

Action

Lists all transitions available for this issue, for the current user.

Search Issues By JQL

Action

Search for issues with a user defined JQL string.

List Issues

Action

List all issues.

Transition Issue

Action

Performs the issue transition.

Create Issue Link

Action

Creates a link between two issues.

Search Issues By JQL (On Premises)

Action

Search for issues with a user defined JQL string.

List Issues By Project

Action

List all issues attached to a project.

Get Attachment

Action

Returns the contents of an attachment.

Add Attachment

Action

Adds one or more attachments to an issue.

Delete Issue Property

Action

Delete a specified property for the issue identified.

List Issue Properties

Action

Returns the keys of all properties for the issue identified.

Get Issue Property

Action

Returns the keys of a specified property for the issue identified.

Get Attachment Details

Action

Returns details and file content for the specified attachment.

Update Issue Property With Array

Action

Store data in an array against a property key.

Update Issue Property

Action

Store data against a property key.

Boards7

Board Created Webhook

Webhook

Triggered whenever a board is created.

List Boards

Action

Returns all boards the user has permission to view.

Board Updated Webhook

Webhook

Triggered whenever a board is updated.

Move Issues To Board

Action

Move issues from the backlog to the board.

Get Board

Action

Returns the board for a specific ID.

List Board Issues For Backlog

Action

Returns a list of all issues.

List Board Issues

Action

Returns a list of all issues.

Issues (Custom Fields - Name format Project ID,Issue Type ID, ie 10001,10009)1

Update Issue

Action

Update an issue.

Issue Comments7

Delete Comment

Action

Deletes specified comment attached to an issue.

List Comments

Action

Returns all comments for an issue.

Comment Updated Webhook

Webhook

Triggered whenever a comment is updated.

Get Comment

Action

Returns a single comment attached to an issue.

Update Comment

Action

Update a specified comment attached to an issue.

Comment Created Webhook

Webhook

Triggered whenever a comment is created.

Add Comment

Action

Add a new comment to a specified issue.

Organization2

Create Organization

Action

Create an organization.

List Organizations

Action

List all organizations.

Assets (Enhanced Object - Object Name format: Object Type ID, Workspace ID. (i.e. 2,eacegr56-4678-56c5-a200-ft543dfd556))7

Find Objects (On-Premises)

Action

Retrieve a list of objects based on an AQL query.

Delete Object

Action

Delete an existing Object in Assets.

Create Object

Action

Creates a new Object in Assets.

Find Objects (Cloud)

Action

Retrieve a list of objects based on the provided query.

Get Object (On-Premises)

Action

Get the specified object.

Get Object (Cloud)

Action

Returns the details of a single Object.

Update Object

Action

Update an existing Object in Assets.

Users5

Search Users

Action

Allows you to search users.

Search Users (v2)

Action

Allows you to search users with the v2 API.

Get User

Action

Returns the details of a specified user

Delete User

Action

Deletes a user. If the operation completes successfully then the user is removed from Jira's user base.

Create User

Action

Creates a user. This resource is retained for legacy compatibility.

Workspaces1

List Workspaces

Action

Returns a list of Assets workspace IDs.

TECHNICAL DETAILS

JIRA integration and API details

Review the sourced authentication and API behaviour used when configuring customer-facing JIRA integrations in Cyclr.

API and authentication

API host
https://api.atlassian.com
Authentication
OAuth 2.0 (3LO) and API token (Basic auth)
Credentials

Cloud site domain, Atlassian account email plus API token or OAuth client ID/secret and redirect URI.

Method categories

Issues, Projects, Users, Search, Boards, Sprints, Worklogs, Webhooks

View vendor API documentation →

Pagination and rate limits

Pagination

Jira Cloud REST uses offset pagination with startAt and maxResults; responses include total for next-page calculation.

Rate limits

Jira Cloud enforces burst-based per-tenant rate limits and returns HTTP 429 for excess requests. Implement exponential backoff and avoid load testing production tenants.

IMPLEMENTATION

Authentication at a glance

OAuth 2.0 authorization code grants (3LO) are recommended for apps. Ad-hoc scripts or service accounts can use Atlassian API tokens with basic auth. Forge and Connect apps use their platform-specific auth flows.

Authentication method
OAuth 2.0 (3LO) and API token (Basic auth)
Credential required

Cloud site domain, Atlassian account email plus API token or OAuth client ID/secret and redirect URI.

Before you begin:

API tokens default to one-year expiration; admin permissions often required to register apps and webhooks.

View setup guide

COMMON QUESTIONS

Frequently asked questions

Use OAuth 2.0 (3LO) for customer-facing apps; ad-hoc scripts or service accounts can use Atlassian API tokens with basic auth. Forge and Connect apps use their own auth frameworks.

Admin rights may be required to register apps, configure OAuth credentials or create instance-level webhooks. Basic API token access can work for per-user integrations.

Yes. Jira Cloud supports admin and app webhooks and they can drive Cyclr orchestrations for near real-time automation.

Implement retries with exponential backoff, batch work when possible and respect Jira’s burst-based per-tenant limits to avoid HTTP 429 responses.