> For the complete documentation index, see [llms.txt](https://docs.rely.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rely.io/plugins-and-automation/plugin-installation-guides/jira.md).

# Jira

{% hint style="info" %}
This plugin is part of Pro and Enterprise plan only
{% endhint %}

## Overview

Jira, by Atlassian, is a widely-used project and issue management platform. When integrated with Rely.io, it can provide additional dimensions of insights, such as customer-facing incidents, security tickets, and ongoing projects. Leveraging Jira data within Rely.io can help in achieving better incident management and project tracking.

Rely.io fetches data directly from Jira, including Projects, Issues, Users, and Groups, ensuring regular synchronization on an hourly basis. Additionally, to achieve real-time data updates, this plugin supports webhooks as outlined in Step 3 of this guide.

## Installation Guide

**Step 1: Generate a Jira API Token (official docs** [**here**](https://id.atlassian.com/manage-profile/security/api-tokens)**).**

1. Log into your Jira Cloud account.
2. Navigate to `Account settings` → `Security` → `API tokens`.
3. Click `Create and manage API tokens`.
4. Name your token, for example, "Rely.io Integration", and click `Create`.
5. Copy and securely store the API token generated.

**Step 2: Add Jira to Rely.io Settings**

1. Open Rely.io and navigate to `Settings` → `Data Sources`.
2. Click `Add Data Source` and choose `Jira`.
3. A form will appear for the Jira Cloud integration:
   * **Plugin Name**: Assign a name for the Jira data source collector.
   * **Jira API Token**: Paste the token you generated in Step 1.
   * **Jira Username Email**: Enter the email address associated with the Jira API Token (should match the email used in Jira settings on Step 1.
   * **Webhook Token**: This token authenticates webhook requests from Jira to Rely.io. If you want to enable webhook implementation, securely store this token for use in Step 3, as you won't be able to view it again in the future. You can also generate a new token and paste it in this field.

Click `Create` to finalize the integration.

**Step 3: Configure Webhooks in Jira**

1. Go to **Jira administration** → **System** → **Webhooks**.
2. Click **Create a Webhook**.
3. Fill in the details:
   * **Name**: Set a name like "Rely.io Integration Webhook".
   * **URL**: Get the webhook URL from Rely.io. Go to [Rely.io Data Sources](https://webapp.rely.io/data-model/datasources), select the Jira plugin and click "View details". The URL format should be `https://magneto.rely.io/api/v1/webhooks/jira?plugin_id=<plugin_identifier>`.
   * **Secret**: Use the webhook token generated in Step 3.
4. Under **Events**, select the following checkboxes:
   * **Issue related events**: Issue created, updated, deleted.
   * **User related events**: User created, deleted, updated.
   * **Project related events**: Project created, updated, deleted
5. Click **Create** at the bottom of the page.

After you submit your form, an entity discovery run will be kickstarted that can take a few minutes. By the end of this discovery run:

* New blueprints will be added to your data model
* Entities representing Jira Projects, Users, Issues and Groups, will be added your software catalog
* These entities will be hourly updated  to ensure they remain in sync with their external counter-parts
* With webhooks enabled the changes in Jira will be immediately available in your software catalog.
* Only issues 30 days old will be added to your data model from the moment you setup this integration.


---

# 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.rely.io/plugins-and-automation/plugin-installation-guides/jira.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.