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

# Jira

> Create Jira issues from verification events for compliance tracking.

The Jira integration creates issues in your Jira Cloud project when Verilock events require team action. Issues are created with configurable types, priorities, and labels for easy triage.

## Prerequisites

* Jira Cloud instance (Data Center is not supported)
* Project admin permissions
* Verilock Business or Enterprise plan

## Setup

<Steps>
  <Step title="Generate an API Token">
    Go to [id.atlassian.com/manage-profile/security/api-tokens](https://id.atlassian.com/manage-profile/security/api-tokens) and click **Create API token**. Name it `Verilock Integration` and copy the token.
  </Step>

  <Step title="Identify Your Project Key">
    In Jira, open your target project. The project key appears in the URL and issue prefixes (e.g., `COMP` for `COMP-123`). You will need this in the next step.
  </Step>

  <Step title="Configure in Verilock">
    Go to **Dashboard > Settings > Integrations > Jira** and enter:

    * **Jira URL**: `https://your-domain.atlassian.net`
    * **Email**: The email associated with your Atlassian account
    * **API Token**: The token from step 1
    * **Project Key**: Your project key (e.g., `COMP`)
  </Step>

  <Step title="Configure Issue Types">
    Map Verilock events to Jira issue types:

    | Event Category     | Issue Type |
    | ------------------ | ---------- |
    | AML events         | Task       |
    | Session events     | Story      |
    | Transaction events | Bug        |

    <Tip>
      You can use any issue type available in your project, including custom types. Verilock validates the type against your project schema on save.
    </Tip>
  </Step>

  <Step title="Test Connection">
    Click **Create Test Issue** to verify the integration. A test issue will appear in your Jira project.
  </Step>
</Steps>

## Event-to-Issue Mapping

| Verilock Event         | Priority | Labels                     | Summary                                      |
| ---------------------- | -------- | -------------------------- | -------------------------------------------- |
| `aml.match_found`      | Highest  | `compliance`, `aml`        | AML Match Found - {screening_id}             |
| `aml.monitoring.match` | Highest  | `compliance`, `monitoring` | Continuous Monitoring Match - {screening_id} |
| `transaction.blocked`  | High     | `fraud`, `blocked`         | Transaction Blocked - {transaction_id}       |
| `transaction.flagged`  | High     | `fraud`, `review`          | Transaction Flagged - {transaction_id}       |
| `session.declined`     | Medium   | `kyc`, `declined`          | Session Declined - {session_id}              |
| `face.duplicate_found` | High     | `kyc`, `duplicate`         | Duplicate Face Detected - {session_id}       |
| `session.expired`      | Low      | `kyc`, `expired`           | Session Expired - {session_id}               |

## Issue Description

Each Jira issue includes a structured description with event details:

```json theme={null}
{
  "fields": {
    "project": { "key": "COMP" },
    "summary": "AML Match Found - aml_x7k9m2p4",
    "issuetype": { "name": "Task" },
    "priority": { "name": "Highest" },
    "labels": ["compliance", "aml", "verilock"],
    "description": {
      "type": "doc",
      "version": 1,
      "content": [
        {
          "type": "paragraph",
          "content": [
            { "type": "text", "text": "Screening ID: aml_x7k9m2p4\nApplicant: Jean Dupont\nMatch Type: PEP\nMatch Score: 92%\nRisk Level: High" }
          ]
        }
      ]
    }
  }
}
```

## Custom Fields

You can map Verilock data to Jira custom fields from the dashboard. Common mappings include:

| Verilock Field    | Jira Custom Field              |
| ----------------- | ------------------------------ |
| `risk_score`      | Risk Score (number)            |
| `session_id`      | Verilock Session ID (text)     |
| `applicant.email` | Applicant Email (text)         |
| `decision`        | Verification Decision (select) |

<Warning>
  Custom field mappings require the fields to exist in your Jira project before configuration. Create them in **Project Settings > Fields** first.
</Warning>

## Troubleshooting

<AccordionGroup>
  <Accordion title="401 Unauthorized">
    Verify your email and API token are correct. Ensure the Atlassian account has access to the target project.
  </Accordion>

  <Accordion title="Issue type not found">
    The configured issue type must exist in your project's issue type scheme. Check **Project Settings > Issue Types** for available types.
  </Accordion>

  <Accordion title="Labels not appearing">
    Jira auto-creates labels on first use. If labels are not visible, check that the `labels` field is available on your issue type's screen scheme.
  </Accordion>
</AccordionGroup>