Connector library

Implemented source Collaboration & Productivity APIs

Jira connector.

Create, retrieve and update Jira Cloud issues, add comments, discover transitions and move issues through their workflow. Jira Service Management customer requests use the separate connector.

Connector download

Download Jira

Versioned ZIP for your CXFabric tenant.

Use this connector in a flow

  1. Register the ZIP in your tenant, or add a new version if the connector is already installed.
  2. Create or select a credential if the action requires one.
  3. In a Draft flow, add an available action, choose its version, connect it, and map inputs.
  4. Test the step and flow; review output and failures before activation.

See readme.md in the ZIP for settings and limitations.

Version
v0.3.0.0 Choose version
Release
2026-10-03
Package
Implemented source
Schema credentials
Basic auth
Connection settings
API Base URL
Package size
10 KB
SHA-256
e1d703b6b793c3023cf6afe29161696843461c1af73e29b057d1b955e73f0d7a

Version history

What's new

  1. v0.3.0.0Latest · 2026-10-03 · Implemented source

    Adds Project Key, Issue Type ID, Summary and optional plain-text Description to Create issue, and Summary/Description to Update issue.

  2. v0.2.0.1Earlier · 2026-10-03 · Implemented source

    Corrects the package identity to match the confirmed original connector registration.

Included in this version

Included actions

Implemented in v0.3.0.0. Use a separate flow trigger; no webhook trigger is included.

Get issue

Read a Jira issue and its visible fields.

Create issue

Create an issue using Project Key, Issue Type ID, Summary and optional plain-text Description. Advanced Fields JSON supplies custom or legacy fields.

Update issue

Update Summary or plain-text Description on an existing issue. Advanced Fields JSON supports custom fields and existing fields-only calls.

Add comment

Add a plain text comment converted to Atlassian Document Format.

Get transitions

Discover available transitions for the issue.

Transition issue

Apply an available transition and any transition-screen fields.

Search issues

Run enhanced JQL search and return one bounded page.

Vendor API

API and access

Implementation considerations
  • Confirm project IDs, board/list IDs, status transition rules, custom fields, and user mapping before enabling writes.
  • Use external IDs or links back to source records so duplicate workflow retries do not create duplicate tasks.
  • For broad work-management APIs, start with create/update/comment/transition before advanced reporting.

Support

Need help with Jira?

Tell us what you need to connect or change.