Skip to main content
Regentra can store a Jira Cloud API token for your organization and verify it’s valid. This is a credential-connection integration today — Regentra does not yet automatically pull change tickets, approval status, or linked pull requests from Jira.
Automated evidence collection from Jira (change tickets, approvals, linked PRs) is not implemented yet, and there is no JQL filter field on the card. Connecting today saves and validates your credentials for when that ships.

​
Setup

1

Generate an Atlassian API token

Sign in to id.atlassian.com/manage-profile/security/api-tokens. Click Create API token, give it a label like Regentra Compliance, and copy the token.
2

Enter credentials in Regentra

In Regentra, go to Settings → Integrations and find the Jira card. Enter:
  • Jira Domain — e.g. mycompany.atlassian.net
  • Email Address — the email of the Atlassian user that owns the token
  • API Token — the token you generated
3

Save and test

Click Save Credentials, then Test Connection. A successful test confirms the credentials are valid and shows the connected user’s display name.

​
Frequently asked questions

Any valid Atlassian account with an API token can connect — the token inherits that user’s role. Treat it like a password: rotate it when the user leaves.
Cloud only today. Server / Data Center uses different auth (Basic + cookies / PAT) and isn’t supported.