Skip to main content

Jira

The Jira connector enables easy and secure data synchronization between your application and your customers’ Jira accounts through unified data models.

​
Authorization

The Jira connector uses OAuth for secure authentication. When creating a connection, the required OAuth scopes are automatically configured based on your specific operations needs (e.g. genericContact::create, genericUser::list).

✓ Automatic token refresh handling
✓ Proactive insufficient permissions detection

View our step-by-step integration guideWhitelabel
Supported
You can choose to provide your own set of clientId and clientSecret for this connector from the Morph Cloud dashboard; allowing a fully whitelabled experience for your end-customers.
import { Morph } from "@runmorph/cloud";

const morph = Morph({ publicKey: "pk_demo_xxxxxxxxxxxxxxx", secretKey: "sk_demo_xxxxxxxxxxxxxxx"}); 

// create a new connection
const connection = morph.connections({ connectorId: "jira", ownerId: "demo" });
await connection.create({ operations:[ "genericContact::list" ]});

// auhtorize the connection
const { auhtorizationUrl } = await connection.authorize();

// redirect the user to the auhtorizationUrl

Live Demo
Select a connector below to experience our seamless authentication flow and see how easy it is to connect third-party services.

​
Models

​
Generic

The Jira connector seamlessly integrates with our unified genericContact model, enabling you to manage Contacts with rich data including firstName, lastName, phoneNumber, email and other key details

API Reference
GET/resources/genericContactList and Search Jira Contacts
GET/resources/genericContact/:idRetrieve a Jira Contact
POST/resources/genericContactCreate a Jira Contact
PATCH/resources/genericContact/:idUpdate a Jira Contact
DEL/resources/genericContact/:idDelete a Jira Contact
Custom Fields
Supported
The Jira connector supports our Field Mapping feature, enabling you or your customers to seamlessly map Jira Contact custom fields to the unified contact model. This allows for flexible data synchronization while maintaining data consistency across all connectors.

view Contact model details

The Jira connector seamlessly integrates with our unified genericCompany model, enabling you to manage Companies with rich data including name and other key details

API Reference
GET/resources/genericCompanyList and Search Jira Companies
GET/resources/genericCompany/:idRetrieve a Jira Company
POST/resources/genericCompanyCreate a Jira Company
PATCH/resources/genericCompany/:idUpdate a Jira Company
DEL/resources/genericCompany/:idDelete a Jira Company
Custom Fields
Supported
The Jira connector supports our Field Mapping feature, enabling you or your customers to seamlessly map Jira Company custom fields to the unified company model. This allows for flexible data synchronization while maintaining data consistency across all connectors.

view Company model details

The Jira connector seamlessly integrates with our unified genericUser model, enabling you to manage Users with rich data including firstName, lastName, email and other key details

API Reference
GET/resources/genericUserList and Search Jira Users
GET/resources/genericUser/:idRetrieve a Jira User
POST/resources/genericUserCreate a Jira User
PATCH/resources/genericUser/:idUpdate a Jira User
DEL/resources/genericUser/:idDelete a Jira User
Custom Fields
Supported
The Jira connector supports our Field Mapping feature, enabling you or your customers to seamlessly map Jira User custom fields to the unified user model. This allows for flexible data synchronization while maintaining data consistency across all connectors.

view User model details

The Jira connector seamlessly integrates with our unified genericWorkspace model, enabling you to manage Workspaces with rich data including name and other key details

API Reference
GET/resources/genericWorkspaceList and Search Jira Workspaces
GET/resources/genericWorkspace/:idRetrieve a Jira Workspace
POST/resources/genericWorkspaceCreate a Jira Workspace
PATCH/resources/genericWorkspace/:idUpdate a Jira Workspace
DEL/resources/genericWorkspace/:idDelete a Jira Workspace
Custom Fields
Supported
The Jira connector supports our Field Mapping feature, enabling you or your customers to seamlessly map Jira Workspace custom fields to the unified workspace model. This allows for flexible data synchronization while maintaining data consistency across all connectors.

view Workspace model details

​
Ticketing

The Jira connector seamlessly integrates with our unified ticketProject model, enabling you to manage Projects with rich data including name, description, members and other key details

API Reference
GET/resources/ticketProjectList and Search Jira Projects
GET/resources/ticketProject/:idRetrieve a Jira Project
POST/resources/ticketProjectCreate a Jira Project
PATCH/resources/ticketProject/:idUpdate a Jira Project
DEL/resources/ticketProject/:idDelete a Jira Project

view Project model details

The Jira connector seamlessly integrates with our unified ticketIssue model, enabling you to manage Issues with rich data including project, title, description, status, priority and other key details

API Reference
GET/resources/ticketIssueList and Search Jira Issues
GET/resources/ticketIssue/:idRetrieve a Jira Issue
POST/resources/ticketIssueCreate a Jira Issue
PATCH/resources/ticketIssue/:idUpdate a Jira Issue
DEL/resources/ticketIssue/:idDelete a Jira Issue

view Issue model details

The Jira connector seamlessly integrates with our unified ticketComment model, enabling you to manage Comments with rich data including issue, author, content, isInternal and other key details

API Reference
GET/resources/ticketCommentList and Search Jira Comments
GET/resources/ticketComment/:idRetrieve a Jira Comment
POST/resources/ticketCommentCreate a Jira Comment
PATCH/resources/ticketComment/:idUpdate a Jira Comment
DEL/resources/ticketComment/:idDelete a Jira Comment

view Comment model details

​
Custom

Supported
Can’t find the unified model you need? The Jira connector supports your own custom model.

​
Webhooks

The Jira connector supports real-time event subscriptions, allowing you to receive instant notifications when records are created, updated, or deleted. Below are the supported models and their corresponding triggers.
ModelsCreatedUpdatedDeletedAPI Reference
genericContactview event
genericCompanyview event
genericUserview event
genericWorkspaceview event
ticketProjectview event
ticketIssueview event
ticketCommentview event

​
Proxy

Supported
The Jira connector supports our Proxy Request feature, allowing you to directly call any endpoints from Jira’s public API without needing to handle authentication. Your customer’s token will be automatically set and refreshed as needed, enabling quick implementation of custom connector behaviors. View API Reference.