Quality
Bug analysis
Root-cause analysis and triage.
Overview
Bug analysis correlates validation failures with issue tracking systems (Jira, Linear, Azure DevOps). Cluster related failures by stack signature, route, and agent category to prioritize root-cause work.
Test Health signals feed bug analysis with flakiness scores and regression confidence.
Who should read this
- QA engineers, SREs, platform teams, and developers operating Zof Console and APIs.
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
Connect issue tracker
Admin Center → Integrations → Jira/Linear/Azure DevOps.
Map project keys to Zof projects.
Create linked issues
From failed case → Create ticket with run artifact attachments.
Include run ID and environment in ticket description.
Track resolution
Re-run affected suite after fix deploy.
Close linked ticket when run passes on staging.
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?
