Triage
Triage is an AI-powered analysis engine that evaluates incoming issues from your tracker (Jira or Azure DevOps) before they enter the Clears AI 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, Clears AI 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:
| Band | Score Range | Meaning |
|---|---|---|
| High | 90–100% | The AI is highly confident it can implement this story end-to-end |
| Medium | 70–89% | The AI can likely handle this with some guidance or Q&A |
| Low | Below 70% | The AI may struggle, consider manual implementation or story decomposition |
| Not triaged | — | The issue has not yet been analyzed |
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:
| Filter | Description |
|---|---|
| Project | Projects to include, the ones listed under Project in the Board's Filters popover (see the Board toolbar) (e.g., the Jira project keys PROJ, BACKEND) |
| Reporter | Only triage issues from specific reporters |
| Assignee | Only triage issues assigned to specific users |
| Issue Type | Restrict to specific types: Story, Task, or Bug |
Viewing Triage Results
Triage results appear in two places, whatever your tracker. The Ticket Panel has only the Ticket details (Epic details for an epic) and AI session tabs, so there is no separate triage tab.
- Board card - The card shows a Triage block with the readiness percentage, Complexity and Risk.
- Ticket Panel - The panel shows the triage summary: the readiness percentage ("ready"), a bar against your account's readiness threshold, Complexity and Risk. When triage has open questions, the summary sits above them under Clears paused · needs your answers, and you answer with Submit Answers. See Answer triage questions.
- Run step - On a ready ticket, the Run step shows the same summary and a folded Confidence reasoning.
- Ticket details - The tab lists the Repos for the ticket.
Starting and Running from Triage
- Click Start Triage on a card or in the Ticket Panel to triage a ticket on demand. See Start Triage.
- Once a ticket is triaged, click Run on its card, or in the Ticket Panel's Run step, to start the run. See Run.
- To order the Board by triage result, choose Sort → Triage score in the Board toolbar.
Importing from Jira
On a Jira account, Add Task → Import from Jira opens a dialog that lists tickets with the columns Key, Summary, Jira status, Priority, Assignee and Updated. Clears triages each ticket you import. See Import from Jira.
Azure DevOps and standalone accounts have no import view: there, use the Board card and the Ticket Panel to see triage results.
The full triage result for an issue is also available through the Triage API below.
Triage API
Triage settings and results are also accessible via the REST API:
| Endpoint | Method | Description |
|---|---|---|
/triage/settings | GET | Retrieve current triage configuration |
/triage/settings | PUT | Update triage configuration |
/triage/results/{story_key} | GET | Retrieve triage results for a specific issue |
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
}
}