Documentation
Jira
Connecting REAP to Jira (opens in a new tab): prerequisites, permissions, setup, what is read and written, troubleshooting.
Overview
REAP reads issues used for incidents and change requests and writes evidence as comments and agreed fields; verdict fields are in development.
Prerequisites
- Jira Cloud (opens in a new tab) or Data Center versions
- Integration user with API token or OAuth 2.0 (3LO) supported auth
- Projects that hold incidents/changes identified
Permissions requested
| Scope | Permission | Why |
|---|---|---|
| Read | Browse projects; read issues, comments, changelog | Evidence and change context |
| Write | Add comments; edit agreed custom fields (evidence link; verdict when released) | Investigation Window and verification evidence |
| Scope | Limited to the named projects | Least privilege |
Setup
- Create the integration user; grant project roles for the in-scope projects.
- Create the evidence-link custom field (or map to an existing one).
- In REAP: Integrations → Jira (opens in a new tab) → site URL, credentials, project keys; map issue types (incident, change).
- Test with a sandbox project.
What REAP reads
- Issues of the mapped types with fields, transitions and comments
- Change windows (custom date fields) for verification scheduling
What REAP writes
- Comments with the Investigation Window summary and evidence links
- Evidence link on change issues; verdict field in development
Troubleshooting
| Symptom | Likely cause | Check |
|---|---|---|
| Issues not visible | Project permission scheme | Integration user can browse the project |
| Comment write fails | Add Comments permission missing | Check project role |
Changelog
- September 2026 · page created (draft).
Engineering to confirm
- Supported Jira (opens in a new tab) editions and versions
Last reviewed: October 7, 2026 (draft) · Owner: solutions engineering · Corrections: security@reapnet.ai