> ## Documentation Index
> Fetch the complete documentation index at: https://docs.enokilabs.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Jira

> File a Jira Cloud issue for every finding above your severity threshold, and keep the two in step.

Enoki files an issue for each new finding above your severity threshold, in the
Jira project you choose. Move the issue to Done and the finding is marked fixed;
verify the fix in Enoki and the issue moves to Done; dismiss the finding and the
issue is closed as Won't Do.

## Connect

Only **workspace admins** manage integrations. In **Settings → Integrations**,
open the **Jira** card. Enoki connects to Jira Cloud; Jira Data Center is not
supported. Connecting does not start filing: the connection is stored without a
project and switched off.

<Steps>
  <Step title="Connect">
    Click **Connect Jira** and approve the access on Atlassian's consent
    screen, choosing your site there. Enoki does not ask to delete issues.
  </Step>

  <Step title="Choose a project and a threshold">
    A new connection starts at **High and above**. Choosing the project also
    registers the webhook that reports issue changes to Enoki; Enoki renews it
    daily, and the card says so if it ever lapses.
  </Step>

  <Step title="Turn it on">
    Click **Create issues automatically**.
  </Step>
</Steps>

## What gets filed

One issue per finding, as a **Bug**, or a **Task** where the project has no Bug
type. The title is the finding's name, as its page in Enoki shows it; the body
carries the category, severity, description, expected behaviour, and a link to
the finding in Enoki.

A run files every open finding it sees at or above your threshold, including
ones that existed before you connected, and a finding re-graded upward across
the threshold is filed at that point. To file one no run has seen, use **Push
to Jira** on the finding.

## How the two stay in step

| In Enoki | In Jira |
| - | - |
| A new finding above your threshold | A new issue in your project |
| A fix verified by a replay | The issue moves to Done, resolved **Done** or **Fixed** |
| A finding dismissed | The issue moves to Done, resolved **Won't Do** (or **Won't Fix**) |
| A finding observed again, or a fix that did not hold | The issue is reopened |

| In Jira | In Enoki |
| - | - |
| The issue reaches Done | The finding is marked **Fixed**, and its attacks are re-run |
| Resolved **Won't Do**, or any other change | Nothing |

Moving an issue to Done asserts the fix; Enoki checks it by replaying the
finding's attacks. If one still works, the finding goes to **Regressed**; if the
replay cannot confirm the fix, for example because your agent could not be
reached, it goes to **Still broken**. Either way the issue is reopened. Each change Enoki makes goes through your workflow's own
transitions and carries a comment saying why.

## Good to know

* **Turning issue creation off stops both directions.**
* **The re-run is a replay, not an assessment.** It spends none of your
  allowance and is capped per finding per day.
* **A project that requires extra fields on create refuses the issue:** the
  finding shows **Jira push failed**, and **Retry push to Jira** retries it.
* **A workflow with no way into Done still gets issues**, but Enoki cannot
  close them: the Jira card shows the failure.
* **Enoki only touches issues it created.**
* **Disconnecting** deletes the stored token and the issue links; issues stay
  in Jira, and Enoki deletes the webhook it registered. To remove Enoki's
  access entirely, remove it under **Connected apps** in your Atlassian
  account.
* **Redacted findings are not filed in full.**


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.