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

# Jira tickets and status sync

> After Jira is connected and configured, you can create Jira tickets from NoScope findings. The integration is one-way: NoScope sends tickets and status chang...

After Jira is connected and configured, you can create Jira tickets from NoScope findings. The integration is one-way: NoScope sends tickets and status changes to Jira, but changes made in Jira do not update NoScope.

## Create Jira tickets

<Steps>
  <Step title="Create one ticket">
    Open a finding and click Create Jira ticket. Confirm the project and create the ticket. NoScope uses the configured issue type.
  </Step>

  <Step title="Create several tickets">
    Select findings in the findings table and click Create Jira tickets. Only findings that do not already have a Jira ticket are included.
  </Step>

  <Step title="Open a linked ticket">
    After a ticket is created, its Jira key appears on the finding. Click the key to open the ticket in Jira.
  </Step>
</Steps>

## What NoScope sends to Jira

* The finding title and security details needed to understand the issue.
* A private link between the Jira ticket and the NoScope finding.
* Later status updates and short comments that explain what changed in NoScope.

## How status sync works

<Steps>
  <Step title="A status changes in NoScope">
    When a finding becomes Open, Fixed, or Risk Accepted, NoScope schedules an update for the linked Jira ticket.
  </Step>

  <Step title="Jira is updated">
    The update normally reaches Jira within about one minute. NoScope uses the transitions allowed by your Jira workflow.
  </Step>

  <Step title="A blocked update is shown">
    If the Jira workflow does not allow the required move, the finding shows a Jira sync warning. The status change in NoScope is still saved.
  </Step>
</Steps>

## If ticket creation fails

Some Jira projects require custom fields that NoScope cannot fill. If Jira rejects a ticket, NoScope shows Jira's error message. Choose another project or update the required fields in the Jira project settings.

## Disconnect and reconnect

Disconnecting stops NoScope from writing to Jira and removes pending status updates. Existing Jira tickets stay in Jira, and findings keep their ticket links. Reconnecting the same site restores the connection without creating the tickets again.


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