# Jira

OneLens integrates with Jira to help you automate ticket management workflows. Once connected, OneLens can automatically create or update Jira issues when an **anomaly is detected**, a **ticket is created**, or a **ticket status is updated**—ensuring your engineering and FinOps teams are instantly in sync.

Alerts generated from OneLens are created as **Jira issues within a specified project and epic**, and can also be **assigned to specific users**, helping streamline accountability and tracking.

{% hint style="success" %}

### Prerequisites

* You must be a **OneLens Admin** user to configure the Slack integration. *Make sure you are log in with the specific account that holds admin access.*
* You must have access to your Jira workspace (via Atlassian) with permission to:
  * View and manage projects and epics
  * Assign tickets
  * Approve third-party app access
    {% endhint %}

## Setting Up Jira

OneLens uses a trusted third-party provider, **Truto**, to securely connect with Atlassian (Jira).

{% hint style="success" %}
**Your data belongs to you—Truto does not sell or share your data.** All authentication and permissions are handled through a secure, privacy-respecting flow.*To know more about Truto,* [*click here*](https://truto.one/)*.*
{% endhint %}

### Required Jira Permissions

<details>

<summary>OneLens (via Truto) uses the following Jira scopes to automate issue creation and synchronization:</summary>

<table><thead><tr><th width="279.8515625">Jira Scope</th><th>Purpose Used in OneLens</th></tr></thead><tbody><tr><td><code>read:jira-work</code></td><td>Read issue types and metadata</td></tr><tr><td><code>write:jira-work</code></td><td>Create and update issues</td></tr><tr><td><code>read:jira-user</code></td><td>List assignable users</td></tr><tr><td><code>manage:jira-project</code></td><td>Read project structures for issue placement</td></tr><tr><td><code>manage:jira-configuration</code></td><td>Read issue field and status configurations</td></tr><tr><td><code>manage:jira-webhook</code></td><td>Enable webhook-based updates</td></tr><tr><td><code>manage:jira-data-provider</code></td><td>Allow secure token flow via Truto</td></tr><tr><td><code>read:application-role:jira</code></td><td>Confirm user roles</td></tr><tr><td><code>offline_access</code></td><td>Maintain integration without re-authentication</td></tr></tbody></table>

</details>

{% hint style="info" %}

## **Privacy Note**&#x20;

OneLens only accesses what’s necessary to create and sync Jira issues.\
It **does not read your Jira project content, internal comments, or attachments.** Integration is limited to anomaly and ticket creation, updates, and basic user/project metadata.
{% endhint %}

### Integration Steps

{% stepper %}
{% step %}
**Go to Integrations**

* Open the **Integrations** section from the OneLens sidebar.
  {% endstep %}

{% step %}
**Click Connect on Jira**

* Find the **Jira** option and click **Connect**.
  {% endstep %}

{% step %}
**Truto Authorization Prompt**

* You’ll see a message indicating that OneLens uses Truto for this integration. Click **Continue**.

  <figure><img src="/files/d4hqJWw5f88pz5rQr1FF" alt="" width="188"><figcaption></figcaption></figure>

{% endstep %}

{% step %}
**Review Permissions**

* You will be redirected to a screen listing required Jira permissions. Click **Connect**.

  <figure><img src="/files/3cbc4NJlh5BV5cPFXNxU" alt="" width="188"><figcaption></figcaption></figure>

{% endstep %}

{% step %}
**Login to Atlassian**

* Enter your Atlassian credentials. Ensure this account has access to the relevant **project**, **epics**, and **assignee details**.

  <figure><img src="/files/f5ftz81zacUdWSQUflgg" alt="" width="375"><figcaption></figcaption></figure>

{% endstep %}

{% step %}
**Authorize Truto-Jira**

* You will see a screen showing that **Truto-Jira** is requesting access on behalf of OneLens. Click **Allow**.

  <div align="left"><figure><img src="/files/WZTGeppzx6SRSESj39dl" alt="" width="563"><figcaption></figcaption></figure></div>

{% endstep %}

{% step %}
**Integration Confirmation**

* Jira is now connected. You can view the integration status in the Integrations section of OneLens.
  {% endstep %}
  {% endstepper %}

## Managing Integration

To disconnect Jira, go to the **Integrations** section and click **Disconnect** under the Jira option.

<div align="center" data-full-width="false"><figure><img src="/files/lENz5C6jYZ84Ao7My6aO" alt="" width="168"><figcaption></figcaption></figure></div>

{% hint style="warning" %}

## NOTE

Disconnecting Jira will **not remove previously created Jira issues**. However, you will no longer be able to create new issues from OneLens until the integration is reconnected. Existing workflows that depend on Jira will stop functioning until connection is restored.
{% endhint %}

## What Next

You can set up workflows for creating a Jira issue automatically whenever a **ticket is generated** or an **anomaly is detected** in OneLens.&#x20;

One of its usecase is:[Automatically Create Jira Issues for New Tickets](/automate/workflows-and-automation/usecases/automatically-create-jira-issues-for-new-tickets.md)


---

# Agent Instructions: 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:

```
GET https://docs.onelens.cloud/integrations/third-party-integrations/jira.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.