Create Jira issues for new ComplianceScout findings.
Destination connector — pushes ComplianceScout findings and violations out to Jira. Configure this connector to automatically create issues or tickets whenever a new finding is raised.
After a successful sync, the following data is available in your ComplianceScout dashboard for violation detection and reporting.
These fields are collected when you add the connector in the ComplianceScout dashboard. Secrets are encrypted at rest using AES-256-GCM and are never logged.
| Field | Type | Required | Notes |
|---|---|---|---|
| Base URL | URL | Required | e.g. https://acme.atlassian.net (no trailing slash) |
| Text | Required | The Atlassian account email associated with the API token. | |
| API token | Secret | Required | Create at id.atlassian.com → Security → API tokens. |
| Project key (for connection test) | Text | Optional | Optional. If provided, we verify access during connection test. Not stored. |
Follow these steps to gather the credentials above and connect Jira to ComplianceScout.
Log in to id.atlassian.com → Security → API tokens → Create API token. Name it "ComplianceScout" and copy the value.
Ensure the Atlassian account has Create Issues permission in the target Jira project.
Note your Atlassian base URL (e.g. https://acme.atlassian.net).
In ComplianceScout, go to Data & Secrets → Integrations → Add Connector → Jira (Destination), enter the base URL, email, and API token.
Configure routing rules under Settings → Routing Rules to specify which violations trigger Jira issue creation.
Start a free trial — your tenant is provisioned instantly and you can wire up this integration from the connectors page.