Integration · Jira
Jira integration: compliance tasks from SimpleAct as Jira issues
Compliance work happens where teams already work. SimpleAct’s Jira integration creates issues in your Jira project for overdue audit actions, evidence requests, governance blockers, escalated runtime signals, changes and CAPA actions, and keeps them current.
Runtime signal escalated
Service chatbot "Lia"
Evidence approval requested
DPIA report
Governance approval blocked
Marketing copy generator
Change register updated
Model update, application screening
SimpleAct
Event routing
Jira
Issues
What the integration does
Compliance cases as tickets
Each case gets exactly one issue. When its content changes in SimpleAct, the issue is updated through the Jira API; if it stays the same, nothing happens.
- Governance and audit
- Overdue audit playbook actions, requested evidence approvals and blocked governance completions become issues. These three kinds can be switched on and off individually.
- Operations and corrections
- Escalated runtime signals, change register entries and CAPA actions also become issues, with the AI system and a link back to SimpleAct.
- No duplicates
- SimpleAct remembers the issue per case and updates it instead of creating new ones. You keep maintaining the status of the case in SimpleAct.
How it works
Setting up Jira
Set-up happens under Enterprise options → Integrations.
Enter access details
Enter the base URL of your Jira instance, project key, issue type (default: Task), e-mail and API token; optionally a default assignee.
Test the connection
A connection test calls Jira with the stored details and reports whether access works.
Cases come in
From now on, issues are created when a matching case is created or changes in SimpleAct. If delivery fails, SimpleAct shows a warning; the case stays saved.
What the Jira integration does and does not do
Tailored to compliance cases, honestly scoped.
- Issues for overdue audit actions, evidence requests and governance blockers
- Issues for escalated runtime signals, change register entries and CAPA actions
- Title and description updated on changes
- Configurable per project, issue type and default assignee
- No status or comments transferred back from Jira
- AI incidents themselves go to ServiceNow, not to Jira
Frequently asked questions about Jira
What do we need for the set-up?
The base URL, a project key, an e-mail address with an API token and an issue type. No code changes are needed.
Is a resolved Jira issue taken over into SimpleAct?
No. The integration only writes from SimpleAct to Jira. You maintain the status in SimpleAct.
Does it work with Jira Cloud and Jira Data Center?
The integration uses the Jira REST API version 3 with e-mail and API token, as offered by Jira Cloud. For Data Center, please get in touch.
Make compliance tasks visible in your ticket system
With the Jira integration, compliance cases arrive as issues in your project, with context and a link back to SimpleAct.