Engineering teams fix what's in the sprint, and the sprint lives in Jira. This integration turns findings into Jira tickets with the context needed to fix them, syncs status both ways, and closes the loop when the re-check passes, so compliance work gets estimated, prioritized, and done like any other work.
Prerequisites
- An OptiTech workspace with the Admin role.
- Jira administrator access (Jira Cloud) to install the app and authorize the connection.
Connect the integration
- In the OptiTech Console, go to Integrations and select Jira.
- Click Connect and complete the Atlassian OAuth flow, selecting your Jira site.
- Map OptiTech teams to Jira projects and choose the issue type (Task or Bug are typical) under Routing.
- Optionally map severity to priority so incident-grade findings arrive as Highest.
How findings become tickets
When a check fails on a control whose owner routes to Jira:
- A ticket is created in the mapped project with the finding's summary, the failed values, affected resources, the control reference, and a deep link back to OptiTech.
- Deduplication holds: one finding is one ticket. Repeat failures update the existing ticket instead of spamming new ones.
- The remediation deadline (for clocked findings like patch windows) maps to the ticket's due date.
Status syncs both ways: resolving the ticket triggers a re-check, and only a passing re-check closes the finding. A ticket closed without the underlying fix reopens with a comment, which keeps the loop honest.
What auditors get from this
The Jira trail becomes remediation evidence: finding opened, ticket created, work done, re-check passed, all timestamped across both systems and stored in the evidence log. "How do you handle identified deviations?" gets answered with a process that demonstrably runs, not a described intention.
Recommended mappings
| OptiTech event | Jira target |
|---|---|
| Platform/infra findings | The platform team's project |
| Endpoint findings | IT service desk project |
| Exception expiring | Ticket to the exception's approver |
| Incident tasks | The incident project, linked to the incident record |
Chat-first teams can route some controls to Slack or Teams instead; routing is per control owner.
Troubleshooting
- Tickets in the wrong project: the control's owner team isn't mapped; unmapped teams fall back to the default project.
- Loops of reopen/close: someone resolves tickets without fixing the drift; the re-check comment names the still-failing values.
- Custom workflows: if your Jira workflow lacks a standard Done state, map OptiTech's "resolved" trigger to the right transition under Routing > Advanced.
Need help?
Join our Discord Server to ask questions or see what others are doing with OptiTech. For paid plan support options, see Support.