> For the complete documentation index, see [llms.txt](https://docs.heeler.com/mrecEO40m5D6bt7Pq5pE/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.heeler.com/mrecEO40m5D6bt7Pq5pE/get-started/ticketing/jira-cloud.md).

# Jira Cloud

Connect Jira Cloud to Heeler over OAuth for two-way ticket creation, updates, and closure.

Heeler runs a **two-way** integration with Jira Cloud — creating, updating, and closing tickets, and harvesting Projects, Users, and Teams to automate ticket context. It connects over **OAuth**, so there's no token to manage.

## What Heeler needs

You'll authorize Heeler to:

* View user information (names, emails, avatars).
* Read project and issue data — search issues and their attachments/worklogs.
* Create and edit issues, post comments, create worklogs, and delete issues.

## Connect Jira Cloud

{% stepper %}
{% step %}

### Add the integration

In Heeler, go to **Administration → Integrations → Add Integration → Jira**.

<figure><img src="https://414480750-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXP3dp2kecwKA2KvYkntz%2Fuploads%2Fgit-blob-3d0e41c09d0467a4c1bd2e1f8b278319240be500%2Fcc-int-jira-cloud-01.png?alt=media" alt="The Add Integration menu in Heeler with Jira selected."><figcaption><p>Add Integration → Jira.</p></figcaption></figure>
{% endstep %}

{% step %}

### Authorize

Review the requested permissions and click **Accept**. Heeler completes the OAuth handshake and returns you to the Integrations list.

<figure><img src="https://414480750-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXP3dp2kecwKA2KvYkntz%2Fuploads%2Fgit-blob-3e6a0bad0c6387312f725c81941076e5be8da48e%2Fcc-int-jira-cloud-02.png?alt=media" alt="The Atlassian consent screen: Heeler Security is requesting access to your Atlassian account, listing view and update permissions, with Accept highlighted."><figcaption><p>Atlassian's OAuth consent — click <strong>Accept</strong>.</p></figcaption></figure>
{% endstep %}

{% step %}

### Verify

The integration shows **Healthy**. Jira is now available as a destination in [Workflows](/mrecEO40m5D6bt7Pq5pE/operate/workflows.md) and [team routing](/mrecEO40m5D6bt7Pq5pE/get-started/map-your-organization/team-ticket-settings.md).

<figure><img src="https://414480750-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXP3dp2kecwKA2KvYkntz%2Fuploads%2Fgit-blob-c76107834b1cc0a3deb6f69dd6320c711ad3bb92%2Fcc-int-jira-cloud-03.png?alt=media" alt="The Heeler Integrations list showing the Jira integration with a Healthy status."><figcaption><p>The connected Jira integration, Healthy.</p></figcaption></figure>
{% endstep %}
{% endstepper %}

## Refreshing credentials

Heeler uses short-lived credentials that refresh automatically. If the connection breaks — often because the person who set it up has left or scopes changed — open the **⋯** menu on the Jira row and choose **Refresh Token**, then re-authorize.

<figure><img src="https://414480750-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FXP3dp2kecwKA2KvYkntz%2Fuploads%2Fgit-blob-629b55c900ab156c45bc57dd212d6d9ee7207277%2Fcc-int-jira-cloud-04.png?alt=media" alt="The row action menu on the Jira integration with the Refresh Token option."><figcaption><p>Refresh Token re-runs the OAuth flow to restore the connection.</p></figcaption></figure>

## Related

* [Team Ticket Settings](/mrecEO40m5D6bt7Pq5pE/get-started/map-your-organization/team-ticket-settings.md) — route each team's findings to its Jira project.
* [Jira (Legacy/On-prem)](/mrecEO40m5D6bt7Pq5pE/get-started/ticketing/jira-legacy-on-prem.md) — the self-hosted, token-based variant.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.heeler.com/mrecEO40m5D6bt7Pq5pE/get-started/ticketing/jira-cloud.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.