Triage

Triage is an AI-powered analysis engine that evaluates incoming issues from your tracker (Jira or Azure DevOps) before they enter the Zero0 pipeline. It scores each issue on risk, complexity, and agent confidence so your team can prioritize what to import and decide which stories are good candidates for AI implementation.

How Triage Works​

When triage is enabled, Zero0 automatically analyzes issues from your connected projects in your tracker (Jira or Azure DevOps). For each issue, the AI evaluates:

• Risk Level - How risky is this change? Considers blast radius, data sensitivity, and architectural impact.
• Complexity - How complex is the implementation? Considers cross-service dependencies, unknowns, and scope.
• Agent Confidence - How confident is the AI that it can implement this story autonomously? Expressed as a percentage (0–100%).

Confidence Bands​

Agent confidence scores map to four bands:

Configuring Triage Settings​

Navigate to Settings > Triage to configure the triage engine.

Triage Status​

Toggle triage on or off for your workspace. When enabled, issues matching your filters are automatically analyzed.

Run Behavior​

Select a workflow to trigger when triage completes. Use the Run Behavior dropdown to choose which workflow (if any) should execute after an issue is triaged. Leave empty to analyze without triggering further automation.

Filters​

Narrow which issues are triaged using these filters:

Viewing Triage Results​

Triage results appear on the Triage tab of each story, whatever your tracker.

On a Jira account, they also appear in the Import from Jira view on the Board. Azure DevOps and standalone accounts have no import view: there, use the story's Triage tab. Each issue row of the import view displays:

Expanding Issue Details​

Click on any triaged issue to expand its detail panel. The expanded view shows:

• Problem / Need - A concise AI-generated summary of the issue's core requirement.
• Risk Reasoning - Why the AI assigned the given risk level.
• Complexity Reasoning - Why the AI assigned the given complexity level.
• Confidence Reasoning - What factors influenced the agent confidence score.
• Relevant Repos - Each repository listed with its individual confidence score (0.0–1.0).

Triage API​

Triage settings and results are also accessible via the REST API:

Settings Object​

{
  "enabled": true,
  "project_keys": ["PROJ", "BACKEND"],
  "reporter_ids": [],
  "assignee_ids": [],
  "issue_types": ["story", "task", "bug"],
  "run_workflow_id": "wf_abc123"
}

Result Object​

{
  "risk_level": "medium",
  "complexity": "high",
  "agent_confidence": 82,
  "problem_need": "Add rate limiting to the public API gateway",
  "risk_reasoning": "Touches shared infrastructure used by multiple services",
  "complexity_reasoning": "Requires changes across API gateway, auth service, and config",
  "confidence_reasoning": "Well-documented patterns exist but cross-service coordination adds uncertainty",
  "relevant_repos": [
    "https://github.com/org/api-gateway",
    "https://github.com/org/auth-service"
  ],
  "relevant_repos_confidence": {
    "https://github.com/org/api-gateway": 0.95,
    "https://github.com/org/auth-service": 0.72
  }
}