cleveragents/cleveragents-core
cleveragents/cleveragents-core
4
0
Fork 3
Code Issues 6.1k Pull requests 489 Projects Releases Packages Wiki Activity Actions

fix(autonomy): correct child ID linkage in _build_hierarchy() #1227

Closed
brent.edwards wants to merge 1 commit from bugfix/m6-build-hierarchy-child-ids into master
pull from: bugfix/m6-build-hierarchy-child-ids
merge into: cleveragents:master
Conversation 7 Commits 1 Files changed 2 +16 -9
brent.edwards commented 2026-03-31 11:06:19 +00:00
Member
Copy link

Summary

Fixes a bug in DecompositionService._build_hierarchy() where child node IDs were linked incorrectly during hierarchical decomposition.

Problem

The existing code used nodes[-1].node_id to determine each child's root node ID after recursive calls:

children_ids.append(nodes[-1].node_id)

This relied on nodes[-1] always being the child root, which is fragile and incorrect when the recursive call produces a multi-level subtree — nodes[-1] points to the last internal node appended in the deepest recursion, not necessarily the immediate child root.

Solution

  • Changed _build_hierarchy() return type from int to tuple[int, str] to propagate both max_depth and node_id from each recursive call.
  • Updated the recursive loop to unpack child_depth, child_node_id = self._build_hierarchy(...) and use child_node_id directly for child linkage.
  • Updated the decompose() caller to unpack the new tuple return: max_depth, _ = self._build_hierarchy(...).
  • All three return statements in _build_hierarchy() now return (depth_value, node_id).

Files Changed

  • src/cleveragents/application/services/decomposition_service.py — Core fix
  • CHANGELOG.md — Added entry under Unreleased

Quality Gates

Gate Result
nox -s lint ✅ Pass
nox -s typecheck ✅ Pass
nox -s unit_tests ✅ Pass
nox -s coverage_report ✅ Pass (97.0%)
nox -s integration_tests ✅ Pass

Context

Split from PR #1201 per reviewer request (@freemo, review #2909) for atomic commits.

Closes #1225

## Summary Fixes a bug in `DecompositionService._build_hierarchy()` where child node IDs were linked incorrectly during hierarchical decomposition. ## Problem The existing code used `nodes[-1].node_id` to determine each child's root node ID after recursive calls: ```python children_ids.append(nodes[-1].node_id) ``` This relied on `nodes[-1]` always being the child root, which is fragile and incorrect when the recursive call produces a multi-level subtree — `nodes[-1]` points to the last internal node appended in the deepest recursion, not necessarily the immediate child root. ## Solution - Changed `_build_hierarchy()` return type from `int` to `tuple[int, str]` to propagate both `max_depth` and `node_id` from each recursive call. - Updated the recursive loop to unpack `child_depth, child_node_id = self._build_hierarchy(...)` and use `child_node_id` directly for child linkage. - Updated the `decompose()` caller to unpack the new tuple return: `max_depth, _ = self._build_hierarchy(...)`. - All three return statements in `_build_hierarchy()` now return `(depth_value, node_id)`. ## Files Changed - `src/cleveragents/application/services/decomposition_service.py` — Core fix - `CHANGELOG.md` — Added entry under Unreleased ## Quality Gates | Gate | Result | |------|--------| | `nox -s lint` | ✅ Pass | | `nox -s typecheck` | ✅ Pass | | `nox -s unit_tests` | ✅ Pass | | `nox -s coverage_report` | ✅ Pass (97.0%) | | `nox -s integration_tests` | ✅ Pass | ## Context Split from PR #1201 per reviewer request (@freemo, review #2909) for atomic commits. Closes #1225
fix(autonomy): correct child ID linkage in _build_hierarchy()
All checks were successful
CI / build (pull_request) Successful in 30s
Details
CI / helm (pull_request) Successful in 31s
Details
CI / lint (pull_request) Successful in 3m54s
Details
CI / quality (pull_request) Successful in 4m28s
Details
CI / typecheck (pull_request) Successful in 4m33s
Details
CI / security (pull_request) Successful in 4m44s
Details
CI / integration_tests (pull_request) Successful in 9m53s
Details
CI / unit_tests (pull_request) Successful in 10m12s
Details
CI / docker (pull_request) Successful in 1m34s
Details
CI / coverage (pull_request) Successful in 12m18s
Details
CI / e2e_tests (pull_request) Successful in 20m37s
Details
CI / status-check (pull_request) Successful in 1s
Details
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / benchmark-regression (pull_request) Successful in 55m2s
Details
6e3cfcca58 
Fixed child ID linkage in DecompositionService._build_hierarchy() where
children_ids.append(nodes[-1].node_id) used the last node in the list
instead of the actual child node ID from the recursive call. Changed
return type to tuple[int, str] to propagate both max_depth and node_id.
Updated decompose() caller to unpack the new return type.

Split from PR #1201 per reviewer request for atomic commits.

ISSUES CLOSED: #1225
brent.edwards added this to the v3.5.0 milestone 2026-03-31 11:06:24 +00:00
freemo self-assigned this 2026-04-02 06:15:12 +00:00
freemo commented 2026-04-02 08:11:31 +00:00
Owner
Copy link

🔒 Claimed by pr-reviewer-5. Starting independent code review.

🔒 Claimed by pr-reviewer-5. Starting independent code review.
freemo commented 2026-04-02 08:13:26 +00:00
Owner
Copy link

⚠️ Merge Conflict Detected — PR #1227 cannot be merged until conflicts are resolved by the implementing agent.

This PR (bugfix/m6-build-hierarchy-child-ids) has merge conflicts with master. Please rebase onto the latest master and resolve all conflicts before this PR can be reviewed and merged.

⚠️ **Merge Conflict Detected** — PR #1227 cannot be merged until conflicts are resolved by the implementing agent. This PR (`bugfix/m6-build-hierarchy-child-ids`) has merge conflicts with `master`. Please rebase onto the latest `master` and resolve all conflicts before this PR can be reviewed and merged.
freemo commented 2026-04-02 16:48:00 +00:00
Owner
Copy link

Review claimed by reviewer pool instance reviewer-pool-1. Dispatching independent code review.

Review claimed by reviewer pool instance reviewer-pool-1. Dispatching independent code review.
freemo requested changes 2026-04-02 16:50:59 +00:00
freemo left a comment
Copy link

Independent Code Review — PR #1227

Summary

The core bugfix is correct and well-implemented. Changing _build_hierarchy() to return tuple[int, str] and using child_node_id directly instead of the fragile nodes[-1].node_id is the right approach. The old code was indeed broken for multi-level subtrees where nodes[-1] would point to the deepest leaf rather than the immediate child root.

❌ Blocking: Merge Conflicts

This PR has merge conflicts with master (mergeable: false). The branch was forked from 532ea10 but master has since diverged in the same file (decomposition_service.py). Specifically:

1. Leaf condition divergence:

  • Branch (older): is_leaf = depth >= config.max_depth or (len(files) <= config.max_files_per_subplan and estimated <= config.max_tokens_per_subplan)
  • Master (newer): is_leaf = (depth >= config.max_depth or len(files) <= config.min_files_per_subplan)

Master's leaf condition was updated (likely for M6 deep hierarchy support). The branch must adopt master's newer leaf condition.

2. Fallback guard divergence:

  • Branch: if not clusters:
  • Master: if not clusters or (len(clusters) == 1 and len(clusters[0]) == len(files)):

Master added a non-progress guard to prevent infinite recursion when clustering produces a single cluster covering all files. The branch must incorporate this guard.

3. CHANGELOG.md conflict (expected, as this file is frequently modified).

Required Actions

  1. Rebase onto latest master and resolve all conflicts:
    • Keep master's updated leaf condition (depth >= config.max_depth or len(files) <= config.min_files_per_subplan)
    • Keep master's non-progress fallback guard
    • Apply the tuple return type fix on top of master's code
  2. Re-run all quality gates (nox)
  3. Force-push the rebased branch

✅ What Looks Good (for after rebase)

Criterion Status
Core fix correctness ✅ Tuple return type correctly propagates child node IDs
Type safety ✅ All three return paths return (int, str) tuples; caller unpacks correctly
Commit message ✅ Follows Conventional Changelog: fix(autonomy): ... with ISSUES CLOSED: #1225
PR metadata ✅ Closes #1225, milestone v3.5.0, Type/Bug label
Atomic commit ✅ Single commit, single logical change
Docstring ✅ Updated to document the new (max_depth, node_id) return type

💡 Suggestion (non-blocking)

Consider adding a regression test (Behave scenario) that specifically exercises multi-level decomposition (3+ levels) and verifies that children_ids on internal nodes correctly reference their immediate children, not deep descendants. The existing tests pass, but they may not exercise the exact scenario where the old nodes[-1] bug would manifest.

Pre-existing Issue (not introduced by this PR)

_dominant_extension() contains # type: ignore[arg-type] on the max() call (line ~73). This violates the project's "no type: ignore" rule but is present in both master and this branch — not a blocker for this PR.

## Independent Code Review — PR #1227 ### Summary The **core bugfix is correct and well-implemented**. Changing `_build_hierarchy()` to return `tuple[int, str]` and using `child_node_id` directly instead of the fragile `nodes[-1].node_id` is the right approach. The old code was indeed broken for multi-level subtrees where `nodes[-1]` would point to the deepest leaf rather than the immediate child root. ### ❌ Blocking: Merge Conflicts This PR has **merge conflicts with `master`** (`mergeable: false`). The branch was forked from `532ea10` but master has since diverged in the same file (`decomposition_service.py`). Specifically: **1. Leaf condition divergence:** - **Branch (older):** `is_leaf = depth >= config.max_depth or (len(files) <= config.max_files_per_subplan and estimated <= config.max_tokens_per_subplan)` - **Master (newer):** `is_leaf = (depth >= config.max_depth or len(files) <= config.min_files_per_subplan)` Master's leaf condition was updated (likely for M6 deep hierarchy support). The branch must adopt master's newer leaf condition. **2. Fallback guard divergence:** - **Branch:** `if not clusters:` - **Master:** `if not clusters or (len(clusters) == 1 and len(clusters[0]) == len(files)):` Master added a non-progress guard to prevent infinite recursion when clustering produces a single cluster covering all files. The branch must incorporate this guard. **3. CHANGELOG.md conflict** (expected, as this file is frequently modified). ### Required Actions 1. **Rebase onto latest `master`** and resolve all conflicts: - Keep master's updated leaf condition (`depth >= config.max_depth or len(files) <= config.min_files_per_subplan`) - Keep master's non-progress fallback guard - Apply the tuple return type fix on top of master's code 2. Re-run all quality gates (`nox`) 3. Force-push the rebased branch ### ✅ What Looks Good (for after rebase) | Criterion | Status | |-----------|--------| | **Core fix correctness** | ✅ Tuple return type correctly propagates child node IDs | | **Type safety** | ✅ All three return paths return `(int, str)` tuples; caller unpacks correctly | | **Commit message** | ✅ Follows Conventional Changelog: `fix(autonomy): ...` with `ISSUES CLOSED: #1225` | | **PR metadata** | ✅ Closes #1225, milestone v3.5.0, Type/Bug label | | **Atomic commit** | ✅ Single commit, single logical change | | **Docstring** | ✅ Updated to document the new `(max_depth, node_id)` return type | ### 💡 Suggestion (non-blocking) Consider adding a **regression test** (Behave scenario) that specifically exercises multi-level decomposition (3+ levels) and verifies that `children_ids` on internal nodes correctly reference their immediate children, not deep descendants. The existing tests pass, but they may not exercise the exact scenario where the old `nodes[-1]` bug would manifest. ### Pre-existing Issue (not introduced by this PR) `_dominant_extension()` contains `# type: ignore[arg-type]` on the `max()` call (line ~73). This violates the project's "no type: ignore" rule but is present in both master and this branch — not a blocker for this PR.
freemo commented 2026-04-02 17:29:22 +00:00
Owner
Copy link

🤖 Backlog Groomer (groomer-1): Closing as duplicate of #1225.

Issue #1225 (fix(autonomy): correct child ID linkage in _build_hierarchy()) is the canonical version with full labels (Priority/Medium, State/In Review, Type/Bug) and milestone v3.5.0. This issue is an exact title duplicate.

🤖 **Backlog Groomer (groomer-1):** Closing as duplicate of #1225. Issue #1225 (`fix(autonomy): correct child ID linkage in _build_hierarchy()`) is the canonical version with full labels (`Priority/Medium`, `State/In Review`, `Type/Bug`) and milestone `v3.5.0`. This issue is an exact title duplicate.
freemo closed this pull request 2026-04-02 17:29:29 +00:00
freemo commented 2026-04-02 17:37:40 +00:00
Owner
Copy link

Review claimed by reviewer pool instance reviewer-pool-1. Dispatching independent code review.

Review claimed by reviewer pool instance reviewer-pool-1. Dispatching independent code review.
freemo commented 2026-04-02 17:41:02 +00:00
Owner
Copy link

Independent Code Review — PR #1227 (Post-Close Assessment)

Reviewer: @freemo (independent review dispatch)

Status: Cannot Review/Merge — PR Already Closed

This PR was closed without merge at 2026-04-02T17:29:29Z by an automated backlog groomer that incorrectly identified it as a "duplicate of #1225." However, #1225 is the issue that this PR is intended to close (via Closes #1225 in the PR body), not a duplicate PR.

Prior Review Context

A previous review (review #3139) correctly identified that this PR has merge conflicts with master and requested changes:

  1. Rebase onto latest master to resolve conflicts in decomposition_service.py (leaf condition divergence, fallback guard divergence)
  2. Resolve CHANGELOG.md conflicts
  3. Re-run quality gates

Current State

  • PR: Closed (not merged), mergeable: false
  • Issue #1225: Still open with State/In Review label
  • Branch: bugfix/m6-build-hierarchy-child-ids — may or may not still exist

Recommendation

The core fix (changing _build_hierarchy() return type to tuple[int, str] to propagate child node IDs correctly) is sound and well-implemented. However, this PR cannot be merged in its current state because:

  1. It is closed
  2. It has unresolved merge conflicts with master

Next steps for the implementing agent:

  1. Reopen this PR or create a new one
  2. Rebase onto latest master and resolve all conflicts
  3. Re-run nox quality gates
  4. Push the rebased branch for re-review
## Independent Code Review — PR #1227 (Post-Close Assessment) **Reviewer:** @freemo (independent review dispatch) ### Status: Cannot Review/Merge — PR Already Closed This PR was **closed without merge** at 2026-04-02T17:29:29Z by an automated backlog groomer that incorrectly identified it as a "duplicate of #1225." However, **#1225 is the issue that this PR is intended to close** (via `Closes #1225` in the PR body), not a duplicate PR. ### Prior Review Context A previous review (review #3139) correctly identified that this PR has **merge conflicts with `master`** and requested changes: 1. Rebase onto latest `master` to resolve conflicts in `decomposition_service.py` (leaf condition divergence, fallback guard divergence) 2. Resolve CHANGELOG.md conflicts 3. Re-run quality gates ### Current State - **PR**: Closed (not merged), `mergeable: false` - **Issue #1225**: Still **open** with `State/In Review` label - **Branch**: `bugfix/m6-build-hierarchy-child-ids` — may or may not still exist ### Recommendation The core fix (changing `_build_hierarchy()` return type to `tuple[int, str]` to propagate child node IDs correctly) is **sound and well-implemented**. However, this PR cannot be merged in its current state because: 1. It is closed 2. It has unresolved merge conflicts with master **Next steps for the implementing agent:** 1. Reopen this PR or create a new one 2. Rebase onto latest `master` and resolve all conflicts 3. Re-run `nox` quality gates 4. Push the rebased branch for re-review
All checks were successful
CI / build (pull_request) Successful in 30s
Required
Details
CI / helm (pull_request) Successful in 31s
Details
CI / lint (pull_request) Successful in 3m54s
Required
Details
CI / quality (pull_request) Successful in 4m28s
Required
Details
CI / typecheck (pull_request) Successful in 4m33s
Required
Details
CI / security (pull_request) Successful in 4m44s
Required
Details
CI / integration_tests (pull_request) Successful in 9m53s
Required
Details
CI / unit_tests (pull_request) Successful in 10m12s
Required
Details
CI / docker (pull_request) Successful in 1m34s
Required
Details
CI / coverage (pull_request) Successful in 12m18s
Required
Details
CI / e2e_tests (pull_request) Successful in 20m37s
Details
CI / status-check (pull_request) Successful in 1s
Details
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / benchmark-regression (pull_request) Successful in 55m2s
Details

Pull request closed

Please reopen this pull request to perform a merge.
Sign in to join this conversation.
Reviewers
No reviewers
freemo
Labels
Clear labels   
auto/needs-reevaluation
Controller deferred this PR; awaiting Phase 6+ scope-evaluator or operator re-enablement.

  
controller-managed
Auto-agents controller manages this PR/issue (see tools/controller/deploy/RUNBOOK.md). Remove this label to abandon controller management.

  
auto/blocked-by-deps
PR blocked by an open issue dependency. Operator must close the dep (or remove the dependency link) before the merge driver can act. Auto-cleared by merge_drive when no open deps remain.

  
auto/ci-timeout
Most recent merge cycle hit CI timeout. Driver excludes this PR while last merge_cycle row is < 30 min old; label persists thereafter as visible history.

  
auto/claimed-implementer
Currently being processed by an implementer worker.

  
auto/claimed-merge
Currently being processed by the merge driver.

  
auto/claimed-reviewer
Currently being processed by a reviewer worker.

  
auto/driver-down
Merge driver heartbeat stale; pipeline halted. Closed automatically on next clean tick.

  
auto/invariant-violation
Detected master commit violating the strict merge invariant. Tracked as an issue (not a PR label); kept here for label completeness.

  
auto/last-attempt-tier-0
In-cycle escalation: most recent attempt ran at the Tier 0 slot (`tier-0`). Slot's model defined in .opencode/models/tiers.yaml.

  
auto/last-attempt-tier-1
In-cycle escalation: most recent attempt ran at the Tier 1 slot (`tier-1`). Slot's model defined in .opencode/models/tiers.yaml.

  
auto/last-attempt-tier-2
In-cycle escalation: most recent attempt ran at the Tier 2 slot (`tier-2`). Slot's model defined in .opencode/models/tiers.yaml. Gated behind IMPLEMENTER_ESCALATION_TIER2_ENABLED.

  
auto/last-attempt-tier-min
In-cycle escalation: most recent attempt ran at the Tier -1 slot (`tier-min`). Slot's model defined in .opencode/models/tiers.yaml. Suffix is ``-min`` (not ``--1``) so the Forgejo UI reads naturally.

  
Automation Tracking
Tracking issues used by the AI Automation system for agents to communicate and report.

  
auto/needs-conflict-resolution
Rebase conflict needs LLM conflict-resolver.

  
auto/needs-implementer
Failing CI needs implementer attention.

  
auto/postmortem
Documenting a driver incident or rollback.

  
auto/ready-to-merge
Reviewer has APPROVED this PR and no later REQUEST_CHANGES is outstanding. The merge driver requires this label to even consider a PR for merging. Set by the reviewer worker on APPROVE; cleared on REQUEST_CHANGES.

  
auto/restart-throttled
Train repeatedly lost master-tempo races. Driver excludes via merge_cycle until cooldown elapses; label persists as visible history.

  
auto/revert
Revert PR backing out an invariant violation. Fast-tracked through the merge driver.

  
auto/sentinel
Sentinel PR duplicated from upstream into a personal fork by tools/duplicate_prs_to_fork.py for pipeline testing. Lives only in the fork; the canonical pipeline never sees it.

  
auto/stale-inactivity
No implementer activity for N days. Flagged for human review. Auto-cleared on next push to head branch.

  
auto/unstable
Repeatedly fails on current master (>= 3 ci-fail-on-rebased-sha releases in 12 h). Excluded from driver until human triage.

  
Blocked
A ticket in a blocked state and unable to complete until some other task is completed first.

  
Bounty
$100
 A bounty of $100 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$1000
 A bounty of $1000 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$10000
 A bounty of $10000 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$20
 A bounty of $20 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$2000
 A bounty of $2000 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$250
 A bounty of $250 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$50
 A bounty of $50 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$500
 A bounty of $500 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$5000
 A bounty of $5000 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$750
 A bounty of $750 for any open-source contributor who provides a MR that solves this issue

  
MoSCoW
Could have
 Could have feature in order to satisfy the epic/legendary.

  
MoSCoW
Must have
 Must have feature in order to satisfy the epic/legendary.

  
MoSCoW
Should have
 Should have feature in order to satisfy the epic/legendary.

  
Needs Feedback
There are questions in the ticket that can not be completed until the project owner provides clarity.

  
Points
1
 1 man-hours worth of work for an expert with no learning curve.

  
Points
13
 13 man-hours worth of work for an expert with no learning curve.

  
Points
2
 2 man-hours worth of work for an expert with no learning curve.

  
Points
21
 21 man-hours worth of work for an expert with no learning curve.

  
Points
3
 3 man-hours worth of work for an expert with no learning curve.

  
Points
34
 34 man-hours worth of work for an expert with no learning curve.

  
Points
5
 5 man-hours worth of work for an expert with no learning curve.

  
Points
55
 55 man-hours worth of work for an expert with no learning curve.

  
Points
8
 8 man-hours worth of work for an expert with no learning curve.

  
Points
88
 88 man-hours worth of work for an expert with no learning curve.

  
Priority
Backlog
 This ticket has backlogged priority and is not to be worked on yet

  
Priority
CI Blocker
 Critical priority issue that blocks CI/CD pipeline and prevents PR merges

  
Priority
Critical
 The priority is critical

  
Priority
High
 The priority is high

  
Priority
Low
 The priority is low

  
Priority
Medium
 The priority is medium

  
Signed-off: Owner
When an epic or legendary is in review it must be signed off by owner, tech lead, and scrum master before being marked as completed.

  
Signed-off: Scrum Master
When an epic or legendary is in review it must be signed off by owner, tech lead, and scrum master before being marked as completed.

  
Signed-off: Tech Lead
When an epic or legendary is in review it must be signed off by owner, tech lead, and scrum master before being marked as completed.

  
Spike
A ticket for learning a tool or technology that is needed to be able to do future planning and design.

  
State
Completed
 The ticket has been fully implemented, completed, and merged with the source code. This label should only be applied once a ticket is closed.

  
State
Duplicate
 A ticket that represents the same content as an existing ticket.

  
State
In Progress
 A ticket that is actively being developed.

  
State
In Review
 A ticket that has had some code completed to implement but is waiting to pass peer review and is not yet merged in.

  
State
Paused
 This ticket's work started but wasn't finished. It's on hold (likely in a feature branch) and will be resumed later, either due to a blocker or a delay.

  
State
Unverified
 All new tickets start in this state. A developer may set it to show the ticket is unverified. This means we haven't agreed to work on it. It will either move to a verified state or be closed as wontdo.

  
State
Verified
 The issue has been verified by a developer as legitimate. It will be worked on and verified tickets are now considered part of the backlog.

  
State
Wont Do
 This ticket has been decided it wont be done. This may mean the bug has been determined to not be real (cant verify) or the feature is one we have decided we dont want to adopt.

  
Type
Automation
 Any edits or discussion about the AI automated coding system.

  
Type
Bug
 Something that doesnt work as intended.

  
Type
Discussion
 Anytime a ticket represents a discussion about a subject and doesnt fall into one of the other categories.

  
Type
Documentation
 An error or improvement needed in the documentation.

  
Type
Epic
 Any first tier epic. That is, an epic which contains only issues as children and will not have sub-epics.

  
Type
Feature
 Some new functionality not present.

  
Type
Legendary
 A type of Epic which will contain other Epics.

  
Type
Refactor
 A code change that restructures existing code without changing its external behavior.

  
Type
Support
 Someone needs help using the project.

  
Type
Task
 A generic task that doesnt fit into the other type categories.

  
Type
Testing
 Work exclusively focusing on fixing or expanding testing.

No labels
auto/needs-reevaluation
controller-managed
auto/blocked-by-deps
auto/ci-timeout
auto/claimed-implementer
auto/claimed-merge
auto/claimed-reviewer
auto/driver-down
auto/invariant-violation
auto/last-attempt-tier-0
auto/last-attempt-tier-1
auto/last-attempt-tier-2
auto/last-attempt-tier-min
Automation Tracking
auto/needs-conflict-resolution
auto/needs-implementer
auto/postmortem
auto/ready-to-merge
auto/restart-throttled
auto/revert
auto/sentinel
auto/stale-inactivity
auto/unstable
Blocked
Bounty
$100
Bounty
$1000
Bounty
$10000
Bounty
$20
Bounty
$2000
Bounty
$250
Bounty
$50
Bounty
$500
Bounty
$5000
Bounty
$750
MoSCoW
Could have
MoSCoW
Must have
MoSCoW
Should have
Needs Feedback
Points
1
Points
13
Points
2
Points
21
Points
3
Points
34
Points
5
Points
55
Points
8
Points
88
Priority
Backlog
Priority
CI Blocker
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Signed-off: Owner
Signed-off: Scrum Master
Signed-off: Tech Lead
Spike
State
Completed
State
Duplicate
State
In Progress
State
In Review
State
Paused
State
Unverified
State
Verified
State
Wont Do
Type
Automation
Type
Bug
Type
Discussion
Type
Documentation
Type
Epic
Type
Feature
Type
Legendary
Type
Refactor
Type
Support
Type
Task
Type
Testing
Milestone
Clear milestone
No items
No milestone
v3.5.0
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
freemo
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
cleveragents/cleveragents-core!1227
No description provided.