Proposal: improve uat-tester — assign milestone to filed bug issues based on the feature area being tested #5580

New issue

Open

opened 2026-04-09 07:40:05 +00:00 by HAL9000 · 0 comments

HAL9000 commented

2026-04-09 07:40:05 +00:00

Owner

Agent Improvement Proposal

Pattern Detected

Type: workflow_fix
Affected Agent: uat-tester
Evidence: Analysis of UAT bug issues filed in cycles 1-2 shows that many bugs are filed without milestone assignments. Issues #5569, #5568, #5565, #5551, #5549, #5548, #5547, #5546, #5545, #5543, #5542, #5541, #5540, #5539, #5534, #5530, #5528, #5527, #5525, #5524, #5523 all have no milestone assigned. This means the implementation orchestrator (which filters by milestones v3.2.0-v3.7.0) cannot find and dispatch workers to fix these bugs.

Detailed Evidence

From the implementation orchestrator tracking issue #5564:

"Issues Found: 7 issues in target milestones"

Yet there are 100+ UAT bugs filed. The discrepancy is because most UAT bugs don't have milestones assigned, so the orchestrator cannot find them.

Example bugs without milestones:

#5569: agents actor context clear command missing
#5568: agents actor context list and agents actor context show missing
#5565: LangGraph.parallel_groups computed but never used
#5551: plan_diff_artifacts.robot test file missing
#5549: DefaultValidationRunner uses text-matching heuristic
#5548: TUI session database path mismatch

These bugs are filed but never picked up for implementation because they lack milestone assignments.

Proposed Change

Modify the uat-tester.md agent definition to:

Determine the appropriate milestone when filing a bug issue based on the feature area being tested:
- Map feature areas to milestones (e.g., TUI features → v3.7.0, plan correction → v3.3.0, invariants → v3.5.0, context → v3.4.0, etc.)
- Use the Forgejo API to set the milestone when creating the issue

Add milestone mapping guidance to the agent's issue creation section:

When filing a bug issue, determine the appropriate milestone:
- TUI features (tui-*, persona, session, sidebar) → v3.7.0 (milestone ID: 130)
- Plan correction (plan-correction-*) → v3.3.0 (milestone ID: 107)
- Invariant management (invariant-*) → v3.5.0 (milestone ID: 109)
- Context management (acms-*, context-*) → v3.4.0 (milestone ID: 108)
- Decision recording (decision-*, plan-tree) → v3.2.0 (milestone ID: 105)
- Subplans/checkpoints (subplan-*, checkpoint-*) → v3.3.0 (milestone ID: 107)
- A2A/facade (a2a-*) → v3.2.0 (milestone ID: 105)
- Plan lifecycle (plan-lifecycle-*) → v3.2.0 (milestone ID: 105)
- Validation (validation-*) → v3.2.0 (milestone ID: 105)
- Resources/projects (projects-*, resources-*) → v3.2.0 (milestone ID: 105)
- Tool router/MCP (tool-router-*, mcp-*) → v3.2.0 (milestone ID: 105)
- Database migrations → v3.2.0 (milestone ID: 105)
- CLI commands → v3.2.0 (milestone ID: 105)
- Git/sandbox → v3.3.0 (milestone ID: 107)

Set milestone in the issue creation API call:

POST /repos/{owner}/{repo}/issues
{
  "title": "UAT: ...",
  "body": "...",
  "milestone": <milestone_id>
}

Expected Impact

Implementation orchestrator can find UAT bugs: With milestones assigned, the orchestrator will discover and dispatch workers to fix UAT bugs
Faster bug resolution: Bugs will be picked up automatically instead of sitting unassigned
Better milestone tracking: Milestone progress will accurately reflect outstanding UAT bugs
Reduced manual triage: The backlog groomer won't need to manually assign milestones to UAT bugs

Risk Assessment

Low risk: Adding milestone assignments to new issues doesn't affect existing issues
Potential concern: Milestone mapping may be incorrect for some feature areas. Mitigation: the backlog groomer can correct incorrect milestone assignments
Potential concern: Milestone IDs may change if milestones are renamed. Mitigation: the agent should look up milestone IDs by name rather than hardcoding them

This is a proposal from the agent evolver. A human must approve this issue before the change will be implemented. To approve: remove the needs feedback label, add State/Verified, or comment with approval.

Automated by CleverAgents Bot
Supervisor: Agent Evolver | Agent: agent-evolver

## Agent Improvement Proposal ### Pattern Detected **Type**: workflow_fix **Affected Agent**: `uat-tester` **Evidence**: Analysis of UAT bug issues filed in cycles 1-2 shows that many bugs are filed without milestone assignments. Issues #5569, #5568, #5565, #5551, #5549, #5548, #5547, #5546, #5545, #5543, #5542, #5541, #5540, #5539, #5534, #5530, #5528, #5527, #5525, #5524, #5523 all have no milestone assigned. This means the implementation orchestrator (which filters by milestones v3.2.0-v3.7.0) cannot find and dispatch workers to fix these bugs. ### Detailed Evidence From the implementation orchestrator tracking issue #5564: > "Issues Found: 7 issues in target milestones" Yet there are 100+ UAT bugs filed. The discrepancy is because most UAT bugs don't have milestones assigned, so the orchestrator cannot find them. Example bugs without milestones: - #5569: `agents actor context clear` command missing - #5568: `agents actor context list` and `agents actor context show` missing - #5565: `LangGraph.parallel_groups` computed but never used - #5551: `plan_diff_artifacts.robot` test file missing - #5549: DefaultValidationRunner uses text-matching heuristic - #5548: TUI session database path mismatch These bugs are filed but never picked up for implementation because they lack milestone assignments. ### Proposed Change Modify the `uat-tester.md` agent definition to: 1. **Determine the appropriate milestone** when filing a bug issue based on the feature area being tested: - Map feature areas to milestones (e.g., TUI features → v3.7.0, plan correction → v3.3.0, invariants → v3.5.0, context → v3.4.0, etc.) - Use the Forgejo API to set the milestone when creating the issue 2. **Add milestone mapping guidance** to the agent's issue creation section: ``` When filing a bug issue, determine the appropriate milestone: - TUI features (tui-*, persona, session, sidebar) → v3.7.0 (milestone ID: 130) - Plan correction (plan-correction-*) → v3.3.0 (milestone ID: 107) - Invariant management (invariant-*) → v3.5.0 (milestone ID: 109) - Context management (acms-*, context-*) → v3.4.0 (milestone ID: 108) - Decision recording (decision-*, plan-tree) → v3.2.0 (milestone ID: 105) - Subplans/checkpoints (subplan-*, checkpoint-*) → v3.3.0 (milestone ID: 107) - A2A/facade (a2a-*) → v3.2.0 (milestone ID: 105) - Plan lifecycle (plan-lifecycle-*) → v3.2.0 (milestone ID: 105) - Validation (validation-*) → v3.2.0 (milestone ID: 105) - Resources/projects (projects-*, resources-*) → v3.2.0 (milestone ID: 105) - Tool router/MCP (tool-router-*, mcp-*) → v3.2.0 (milestone ID: 105) - Database migrations → v3.2.0 (milestone ID: 105) - CLI commands → v3.2.0 (milestone ID: 105) - Git/sandbox → v3.3.0 (milestone ID: 107) ``` 3. **Set milestone in the issue creation API call**: ``` POST /repos/{owner}/{repo}/issues { "title": "UAT: ...", "body": "...", "milestone": <milestone_id> } ``` ### Expected Impact - **Implementation orchestrator can find UAT bugs**: With milestones assigned, the orchestrator will discover and dispatch workers to fix UAT bugs - **Faster bug resolution**: Bugs will be picked up automatically instead of sitting unassigned - **Better milestone tracking**: Milestone progress will accurately reflect outstanding UAT bugs - **Reduced manual triage**: The backlog groomer won't need to manually assign milestones to UAT bugs ### Risk Assessment - **Low risk**: Adding milestone assignments to new issues doesn't affect existing issues - **Potential concern**: Milestone mapping may be incorrect for some feature areas. Mitigation: the backlog groomer can correct incorrect milestone assignments - **Potential concern**: Milestone IDs may change if milestones are renamed. Mitigation: the agent should look up milestone IDs by name rather than hardcoding them --- *This is a proposal from the agent evolver. A human must approve this issue before the change will be implemented. To approve: remove the `needs feedback` label, add `State/Verified`, or comment with approval.* --- **Automated by CleverAgents Bot** Supervisor: Agent Evolver | Agent: agent-evolver

Rows
Columns