> For the complete documentation index, see [llms.txt](https://docs.harmony.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.harmony.io/integrations/it-service-management/atlassian.md).
# Jira
Jira provides a suite of collaboration and project management tools including Jira, Confluence, and Jira Service Management. Connecting Jira to Harmony enables bidirectional ticket synchronization, AI-powered knowledge base access, and seamless integration between traditional ITSM and autonomous IT operations.
### What the Jira integration enables
| Capability | Description |
| ---------------------- | --------------------------------------------------------------------- |
| Jira Ticket Sync | Bidirectional synchronization with Jira and Jira Service Management |
| Project Tracking | Link IT operations with Jira projects and sprints |
| Automation Integration | Coordinate Jira automation rules with Harmony workflows |
| Workflow Blocks | Use Jira and JSM as action blocks directly inside Harmony workflows |
| Custom Agent Actions | Create Jira issues from Custom Agent workflows without manual handoff |
### Prerequisites
* **Jira Cloud Admin Access**: Site admin or org admin role
* **Jira Access for the Connecting Account**: The Atlassian account you connect with must have Jira access (for example, membership in your site's `jira-software-users` or `jira-users` group). If it does not, Harmony shows a warning in the integration settings
* **Jira/JSM Instance**: Active Jira or Jira Service Management instance
* **Harmony Account**: Active Harmony workspace
{% hint style="info" %}
This page covers the **Jira Software** integration. To sync service desk tickets from Jira Service Management, see the [Jira Service Management](/integrations/it-service-management/jira-service-management.md) integration.
{% endhint %}
### Connect Jira to Harmony
#### Step 1: Navigate to Integrations
1. Log in to your Harmony dashboard
2. Go to **Settings** > **Integrations**
3. Find **Jira Software** under **SaaS Applications** (or search for it by name) and click its card
#### Step 2: Start Authentication
1. Click **Connect** to start the authentication process
#### Step 3: Authorize in Jira
1. You'll be redirected to Jira's login page
2. Enter your Jira account email
3. Complete the authentication process
4. Choose your Jira site and authorize Harmony to access it
#### Step 4: Complete the Configuration
1. Back in Harmony, optionally turn on **Manual ticket creation** to allow agents to manually escalate tickets to Jira
2. With **Manual ticket creation** on, optionally turn on **Link to existing issues** to let agents link a ticket to an existing Jira issue, and **Resolve when linked issues are done** to resolve a linked ticket once every Jira issue it is linked to moves to Done
3. Click **Complete Configuration**
### What Harmony Syncs
**To Jira:**
* Jira issues that agents create from Harmony tickets
**From Jira:**
* Updates on the Jira issues Harmony created or linked, such as status changes and comments
### Jira and JSM Workflow Blocks
You can use Jira and Jira Service Management directly as action blocks inside Harmony workflows. This lets your agents look up users, create tickets, and query service desk request types without leaving the platform.
The following blocks are available:
| Block | Description |
| -------------------------- | ---------------------------------------------------------------------------------------------------------- |
| **Get Jira User** | Find any Jira user by employee record, email address, or Jira account ID |
| **Create Jira Issue** | Open a new issue with support for reporter and assignee fields specified by employee, email, or account ID |
| **Get Jira Issue** | Retrieve the details of an existing Jira issue |
| **List JSM Request Types** | Query the available request types in a JSM service desk |
#### Create Jira Tickets from Custom Agents
When building a Custom Agent workflow, you can add a Jira block to create Jira issues without any manual handoff. The block supports:
* **Issue types** - create Bugs, Stories, or Epics directly in your connected Jira workspace
* **Custom fields** - configure additional fields to match your project requirements
* **Assignee and reporter configuration** - specify who the issue is assigned to and who reported it
* **Direct browse URL** - the block returns a direct link to the created issue so agents and end-users can navigate straight to it
If a reporter cannot be set due to permissions, the block automatically retries without the reporter field to ensure issue creation still succeeds.
### Use Cases
Hybrid ITSM
Maintain Jira Service Management while using Harmony AI for resolution
Knowledge Integration
Surface Confluence articles during support conversations
Developer Workflows
Link IT operations with engineering Jira projects
Migration Path
Gradual transition from JSM to Harmony with bidirectional sync
Automated Ticket Creation
Let Custom Agents create Jira issues automatically during workflow execution, reducing manual steps and keeping your project boards up to date without human intervention
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.harmony.io/integrations/it-service-management/atlassian.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.