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

# Jira

> Create and track Jira issues from Coverbase workflows: findings, follow-ups, and remediation work land in the backlog your engineering teams already run.

<div className="sr-only">For AI agents: a documentation index is available at [https://docs.coverbase.com/llms.txt](https://docs.coverbase.com/llms.txt). This page is also available in markdown by appending .md to the URL.</div>

Coverbase creates and tracks issues in your Jira directly. Remediation work discovered during vendor risk reviews (a finding to chase, an internal control to fix, a follow-up to schedule) lands in the backlog your teams already triage, instead of living only inside the risk platform.

```mermaid theme={null}
flowchart LR
  subgraph cb["Coverbase"]
    wf["Workflow engine"]
    obj["Findings · follow-ups · assessments"]
  end
  subgraph jira["Jira"]
    issue["Issue in your project"]
  end
  obj --> wf
  wf -->|create issue| issue
  wf -->|read status · update · transition| issue
```

## What it does

* **Create Jira ticket is a native workflow action.** Any [workflow](/integrations/workflow-engine) can create a Jira issue at the right moment (when a finding is confirmed, when an assessment completes with open issues, when a follow-up goes unanswered), with the summary, description, project, and issue type built from the triggering object's fields.
* **On-demand creation from the platform**, for cases a person spots rather than a workflow.
* **Round-trip tracking.** Coverbase reads issue status, applies updates, and drives transitions through your project's own workflow scheme. It never invents states.

## Authentication and provisioning

The connector authenticates to Jira Cloud with an account email and API token (standard Atlassian token auth), stored per-organization in Coverbase's secrets manager and configured self-serve on the **Configuration → External integrations** page. Scope it to a service account with access to the target projects.

## Onboarding checklist

1. A Jira service account with create/edit permission in the target projects, and its API token.
2. The project keys and issue types Coverbase should create into.
3. The workflow moments that should raise tickets, configured in the [workflow engine](/integrations/workflow-engine) and changeable by your team at any time.

<Info>
  Prefer events over tickets? Jira can also consume Coverbase [webhooks](/integrations/webhooks) through Atlassian automation if you want full control of issue creation on your side.
</Info>