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

# Jira Integration

> Connect Jira to use it as evidence for change management and incident tracking controls.

## Overview

The Jira integration links your Jira projects to Matproof so that Jira issues and change tickets can serve as evidence for change management, incident management, and corrective action controls.

**What it enables:**

* Map Jira projects to Matproof controls as evidence sources
* Sync Jira issues as incident records or corrective actions
* Use Jira tickets as change management evidence (change requests, approvals, CAB decisions)
* Link specific Jira issues to controls directly from Matproof

***

## Prerequisites

* Jira Cloud account (Atlassian Cloud — Jira Server/Data Center is not currently supported)
* Matproof Admin or Owner role
* Jira project admin or organization admin permissions

***

## Connecting Jira

1. Go to **Settings → Integrations**
2. Click **Connect** next to Jira
3. Enter your Atlassian site URL (e.g., `yourcompany.atlassian.net`)
4. Click **Authorize** — you will be redirected to Atlassian to grant access
5. Select which Jira projects Matproof should have access to
6. Return to Matproof and confirm the connection

<Note>
  Matproof requests read-only access to your Jira issues and project configurations. It cannot create, edit, or delete Jira issues.
</Note>

***

## Configuring Project Mappings

After connecting, configure which Jira projects map to which Matproof functions:

1. Go to **Settings → Integrations → Jira → Configure**
2. For each Jira project, select its purpose in Matproof:
   * **Change Management** — issues used as change request evidence
   * **Incident Tracking** — issues synced to the Incidents module
   * **Corrective Actions** — issues linked to Matproof corrective actions

### Change Management Mapping

Map a Jira project used for change requests to the Change Management function. Matproof will check:

* Change requests have an approval record before implementation
* Emergency changes are documented post-facto
* Change request count and approval rate over the audit period

This provides automated evidence for SOC 2 CC8 (Change Management) and ISO 27001 A.8.32.

### Incident Tracking Mapping

If you track incidents in Jira, Matproof can pull these as incident records:

* Jira issues of a specific type (e.g., "Incident", "Security Incident") sync to the Incidents module
* Severity, status, and resolution data are mapped automatically
* Jira issues appear alongside natively created Matproof incidents

### Corrective Actions Mapping

Link a Jira project to corrective actions so that Jira tickets serve as the remediation tracking mechanism. When an issue in the linked project is closed, the corresponding Matproof corrective action can be updated automatically.

***

## Linking Individual Issues to Controls

Beyond project-level mapping, you can link specific Jira issues to individual controls as point-in-time evidence:

1. Open a control in **Controls**
2. Click **Add Evidence → Link from Jira**
3. Search for the Jira issue by key or title
4. Confirm — the issue title, status, and URL are stored as evidence

This is useful for controls that reference specific decisions or one-time events (e.g., a change approval for a specific system migration).

***

## What Gets Mapped to Which Controls

| Evidence Collected                     | Control Examples                                         |
| -------------------------------------- | -------------------------------------------------------- |
| Change requests with approval records  | Change management controls (SOC 2 CC8, ISO 27001 A.8.32) |
| Incident records with resolution times | Incident response controls                               |
| Security incidents logged and resolved | DORA Art. 17-23, NIS2 incident handling                  |
| Corrective actions tracked to closure  | ISO 27001 Clause 10.1                                    |

***

## Common Issues

### "My Jira Server instance isn't connecting"

Jira Server (self-hosted) and Jira Data Center are not currently supported — only Jira Cloud (atlassian.net). If you need Jira Server support, contact [support@matproof.com](mailto:support@matproof.com).

### "Incidents from Jira are appearing as duplicates"

If you are both logging incidents natively in Matproof and importing from Jira, check the deduplication setting under **Settings → Integrations → Jira → Configure → Incident deduplication**. Set the matching field (e.g., Jira issue key) to prevent duplicates.

### "Change request issues aren't showing approval status"

Matproof looks for Jira workflow transitions named "Approved" or "CAB Approved". If your workflow uses different transition names, map them in **Settings → Integrations → Jira → Configure → Workflow mapping**.

***

## Disconnecting

Go to **Settings → Integrations → Jira → Disconnect**. Also revoke the Matproof OAuth app from your Atlassian account under **Atlassian Account → Security → Connected apps**.