---
schema_version: "1"
id: e2d6dc40dbd2eddccfa3591057c178fe96e36af166879ddf3a406311d7648202
title: Jira Connector 1.2
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/jira-connector/latest/index.md
canonical_url: https://docs.mulesoft.com/jira-connector/latest/
source_site: docs.mulesoft.com
content_type: documentation
content_hash: 54826168a8cd2d99e10c36d288f40a79792804a3bb2861dbb83303ad2b09872d
description: MuleSoft Documentation Site
release: "1.2"
latest: true
---
---
product: Jira Connector
version: 1.2
is-latest-version: true
---

# Jira Connector 1.2

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

Anypoint Connector for Jira (Jira Connector) synchronizes data and automates business processes
between Jira and third-party applications, either on-premises or in the cloud.

> [!NOTE] Jira Connector uses the Jira REST API v3 and is only for the Cloud version of Jira.

Jira is a software development platform to help agile product development teams triage and track
their work from inception to launch. Jira Connector enables organizations of all sizes to establish
scalable and sustainable product development workflows by connecting Jira to other tools in the
organization such as the customer service platforms, project management tools, and others.

For compatibility information and fixed issues, see the Jira Connector Release Notes.

## Before You Begin

To use this connector, you must be familiar with:

- The Jira APIs

- Anypoint Connectors

- Mule runtime engine (Mule)

- Elements and global elements in a Mule flow

- Creating a Mule app using Anypoint Studio or Anypoint Code Builder

Before creating an app, you must have:

- Credentials to access the target Jira resource

- Anypoint Studio or Anypoint Code Builder

## Common Use Cases for the Connector

Automate business processes by integrating Jira with other IT tools and systems in your enterprise
such as messaging, CRM, customer service, and others.

Possible use cases include:

- Enhance customer experience by connecting Jira with your customer service platform, thereby
  reducing the cycle times between when a customer raises an issue through a customer service
  platform, like Salesforce’s Sales Cloud, and when that issue gets added to the product team’s work
  backlog in Jira.

- Streamline crossteam handoffs by ensuring that the updated information on every issue is available
  across all systems and stakeholders. For example, when the engineering team marks a customer issue
  as resolved, update the status across your CRM and customer support platforms, so the
  customer-facing teams (sales and support) are notified immediately.

- Foster team collaboration and improve productivity by automating the flow of information between
  Jira and your team’s communication platform, so that when a new issue gets added to the backlog or
  an issue gets updated, relevant team members are notified so the appropriate next steps can be
  taken.

## Authentication Types

Jira Connector connections use the following authentication methods:

- Basic authentication  
  Uses a username and password for authentication

- OAuth2  
  Delegates user authentication to the service hosting the user account

> [!NOTE] Jira Connector does not support authentication via personal access tokens (PATs).

## See Also

- [Introduction to Anypoint Connectors](https://docs.mulesoft.com/connectors/introduction/introduction-to-anypoint-connectors)

- [Use Exchange to Discover Connectors, Templates, and Examples](https://docs.mulesoft.com/connectors/introduction/intro-use-exchange)

- [Jira Reference](https://docs.mulesoft.com/jira-connector/latest/jira-connector-reference)

- [Salesforce Help](https://help.salesforce.com)