Integrations
Jira
Issue tracking integration.
Overview
Create and link issues from failed runs and remediation plans.
Implementation status: partial. Verify availability in your organization before production dependency.
Who should read this
- QA engineers, SREs, platform teams, and developers operating Zof Console and APIs.
Prerequisites
- Admin Center access for OAuth connections
- Scopes or credentials: read:jira-work, write:jira-work
When to use this workflow
- Onboarding new team members to Zof terminology and workflows
- Authoring internal runbooks aligned with Console labels
- Designing CI/CD or webhook integrations against documented behavior
Step-by-step procedure
Open Integrations
Platform → Integrations → select provider.
Confirm you have admin or integrations:manage permission.
Authorize connection
Complete OAuth consent or paste token per provider documentation.
Use least-privilege scopes required for your workflow.
Verify and configure
Run connection test from Integrations detail.
Configure webhooks or pipeline triggers as needed.
Key concepts
- Organization scope
- All Zof Console and API operations are isolated to your authenticated tenant.
- Governed execution
- Agent output and remediation follow policy packs with human approval when configured.
Best practices
- Validate changes in staging before applying release gates to production.
- Include run IDs and timestamps when escalating issues to support or auditors.
- Align internal runbook terminology with Zof Console UI labels for clarity.
Was this page helpful?
