fix(sandbox): use spec-required cleveragents/plan-<plan_id> branch naming in GitWorktreeSandbox #3263

Merged

freemo merged 1 commits from fix/git-worktree-branch-naming into master 2026-04-05 21:09:06 +00:00

Conversation 4 Commits 1 Files Changed 3

+7 -7

freemo commented 2026-04-05 08:44:10 +00:00

Owner

Copy Link

Copy Source

Summary

Fixes a branch naming convention bug in GitWorktreeSandbox.create() where sandbox branches were being created as sandbox/<plan_id> instead of the spec-required cleveragents/plan-<plan_id> format. This ensures all CleverAgents-managed git branches are correctly namespaced under the cleveragents/ prefix as defined in the specification.

Changes

• src/cleveragents/infrastructure/sandbox/git_worktree.py:

  • Updated branch name assignment from f"sandbox/{safe_plan_id}" to f"cleveragents/plan-{safe_plan_id}" to match the spec-required naming format.
  • Updated the method docstring to reflect the corrected branch name pattern (cleveragents/plan-<plan_id> instead of sandbox/<plan_id>), keeping documentation in sync with the implementation.

• features/steps/git_worktree_coverage_boost_steps.py:

  • Updated 4 test branch name fixtures to use the new naming convention:
    • sandbox/test → cleveragents/plan-test
    • sandbox/cleanup-test → cleveragents/plan-cleanup-test
    • sandbox/branch-delete-fail → cleveragents/plan-branch-delete-fail
  • Ensures all unit-level test scaffolding accurately reflects real-world branch names produced by the system under test.

• features/garbage_collection.feature:

  • Updated scenario branch name fixture from sandbox/test-plan to cleveragents/plan-test-plan to align with the corrected naming convention.

Design Decisions

• cleveragents/ namespace prefix: The spec designates cleveragents/ as the authoritative namespace for all branches managed by CleverAgents tooling. Using this prefix ensures branches are visually grouped in git clients, avoids collisions with user-created branches, and makes automated cleanup (garbage collection) unambiguous.
• plan- infix: The plan- segment distinguishes plan-execution branches from any other future branch types that may be introduced under the cleveragents/ namespace. This matches the format shown in agents plan execute output in the specification.
• Minimal blast radius: The fix is a single-line change to the production code path. All other changes are test fixture updates required to keep the test suite honest — no test logic was altered, only the expected branch name strings.
• No migration path needed: Sandbox branches are ephemeral and tied to a single plan execution lifecycle.

Testing

• lint: PASSED
• typecheck: PASSED (0 errors, 0 warnings)
• Python import verification: PASSED — confirmed cleveragents/plan-{safe_plan_id} is the branch name produced

Related Issues

Closes #2601

---

Automated by CleverAgents Bot
Supervisor: Implementation | Agent: ca-issue-worker

## Summary Fixes a branch naming convention bug in `GitWorktreeSandbox.create()` where sandbox branches were being created as `sandbox/<plan_id>` instead of the spec-required `cleveragents/plan-<plan_id>` format. This ensures all CleverAgents-managed git branches are correctly namespaced under the `cleveragents/` prefix as defined in the specification. ## Changes - **`src/cleveragents/infrastructure/sandbox/git_worktree.py`**: - Updated branch name assignment from `f"sandbox/{safe_plan_id}"` to `f"cleveragents/plan-{safe_plan_id}"` to match the spec-required naming format. - Updated the method docstring to reflect the corrected branch name pattern (`cleveragents/plan-<plan_id>` instead of `sandbox/<plan_id>`), keeping documentation in sync with the implementation. - **`features/steps/git_worktree_coverage_boost_steps.py`**: - Updated 4 test branch name fixtures to use the new naming convention: - `sandbox/test` → `cleveragents/plan-test` - `sandbox/cleanup-test` → `cleveragents/plan-cleanup-test` - `sandbox/branch-delete-fail` → `cleveragents/plan-branch-delete-fail` - Ensures all unit-level test scaffolding accurately reflects real-world branch names produced by the system under test. - **`features/garbage_collection.feature`**: - Updated scenario branch name fixture from `sandbox/test-plan` to `cleveragents/plan-test-plan` to align with the corrected naming convention. ## Design Decisions - **`cleveragents/` namespace prefix**: The spec designates `cleveragents/` as the authoritative namespace for all branches managed by CleverAgents tooling. Using this prefix ensures branches are visually grouped in git clients, avoids collisions with user-created branches, and makes automated cleanup (garbage collection) unambiguous. - **`plan-` infix**: The `plan-` segment distinguishes plan-execution branches from any other future branch types that may be introduced under the `cleveragents/` namespace. This matches the format shown in `agents plan execute` output in the specification. - **Minimal blast radius**: The fix is a single-line change to the production code path. All other changes are test fixture updates required to keep the test suite honest — no test logic was altered, only the expected branch name strings. - **No migration path needed**: Sandbox branches are ephemeral and tied to a single plan execution lifecycle. ## Testing - lint: PASSED - typecheck: PASSED (0 errors, 0 warnings) - Python import verification: PASSED — confirmed `cleveragents/plan-{safe_plan_id}` is the branch name produced ## Related Issues Closes #2601 --- **Automated by CleverAgents Bot** Supervisor: Implementation | Agent: ca-issue-worker

freemo added 1 commit 2026-04-05 08:44:10 +00:00

fix(sandbox): use spec-required cleveragents/plan- branch prefix in GitWorktreeSandbox ... 4b9798bc40

- Implemented branch naming change in GitWorktreeSandbox.create() from sandbox/<plan_id> to cleveragents/plan-<plan_id>, located in src/cleveragents/infrastructure/sandbox/git_worktree.py
- Updated the create() method docstring to reflect the new branch naming convention
- Updated test fixtures:
  - features/steps/git_worktree_coverage_boost_steps.py: sandbox/test -> cleveragents/plan-test, sandbox/cleanup-test -> cleveragents/plan-cleanup-test, sandbox/branch-delete-fail -> cleveragents/plan-branch-delete-fail
- Updated scenario:
  - features/garbage_collection.feature: sandbox/test-plan -> cleveragents/plan-test-plan
- Design rationale:
  - Adopted the spec-required format: cleveragents/plan-{safe_plan_id} to align with the spec-defined namespace for all CleverAgents-managed git branches
  - Ensures consistent branch naming across code, tests, and features for easier policy enforcement and maintainability

ISSUES CLOSED: #2601

freemo added this to the v3.3.0 milestone 2026-04-05 08:46:18 +00:00

freemo referenced this pull request 2026-04-05 08:48:00 +00:00

UAT: `GitWorktreeSandbox` creates branch named `sandbox/<plan_id>` instead of spec-required `cleveragents/plan-<plan_id>` #2601

freemo commented 2026-04-05 09:16:44 +00:00

Author

Owner

Copy Link

Copy Source

🔒 Review claimed by reviewer-pool-1 [claim-token: reviewer-pool-1-3263-1775374200]

---

Automated by CleverAgents Bot
Supervisor: PR Review | Agent: ca-continuous-pr-reviewer

🔒 Review claimed by reviewer-pool-1 [claim-token: reviewer-pool-1-3263-1775374200] --- **Automated by CleverAgents Bot** Supervisor: PR Review | Agent: ca-continuous-pr-reviewer

freemo commented 2026-04-05 09:24:34 +00:00

Author

Owner

Copy Link

Copy Source

🔒 Review claimed by reviewer-pool-1 [claim-token: reviewer-pool-1-3263-1775373000]

---

Automated by CleverAgents Bot
Supervisor: PR Review | Agent: ca-continuous-pr-reviewer

🔒 Review claimed by reviewer-pool-1 [claim-token: reviewer-pool-1-3263-1775373000] --- **Automated by CleverAgents Bot** Supervisor: PR Review | Agent: ca-continuous-pr-reviewer

freemo reviewed 2026-04-05 10:02:11 +00:00

freemo left a comment

Author

Owner

Copy Link

Copy Source

✅ Review Complete — Clean, spec-aligned bug fix

Review Summary

Scope: Single-line production fix + test fixture updates (3 files, 7 insertions, 7 deletions)

Specification Alignment ✅

• The spec's agents plan execute output clearly shows Branch: cleveragents/plan-01HXM8C2 — this fix aligns the implementation with that requirement.
• The cleveragents/ namespace prefix is the spec-defined namespace for all CleverAgents-managed git branches.
• The plan- infix correctly distinguishes plan-execution branches from other potential future branch types.

Correctness ✅

• The production change is a single-line format string update: f"sandbox/{safe_plan_id}" → f"cleveragents/plan-{safe_plan_id}".
• The _sanitise_branch_name() function already handles slashes in its allowed character set, so the cleveragents/plan- prefix won't be mangled.
• The fallback in _sanitise_branch_name() (empty input → "sandbox") would produce cleveragents/plan-sandbox, which is still correctly namespaced.
• No other code paths reference the old sandbox/ branch prefix — the change is self-contained.

Test Quality ✅

• All 4 test fixture updates in git_worktree_coverage_boost_steps.py correctly mirror the new naming convention.
• The garbage_collection.feature scenario fixture is updated to match.
• No test logic was altered — only expected branch name strings, which is correct for a naming convention fix.
• Verified via grep that no stale sandbox/<plan_id> branch name references remain in test files on this branch.

PR Metadata ✅

• Commit message: Conventional Changelog format (fix(sandbox): ...) with ISSUES CLOSED: #2601 footer ✓
• PR body: Contains Closes #2601 ✓
• Label: Type/Bug ✓
• Milestone: v3.3.0 ✓
• Single commit: Clean history ✓

CI Status

• lint ✅ | typecheck ✅ | security ✅ | quality ✅ | unit_tests ✅ | integration_tests ✅ | e2e_tests ✅ | build ✅ | helm ✅
• coverage, benchmark, docker, status-check: pending (waiting for upstream jobs)

Scheduling merge for when all checks complete.

---

Automated by CleverAgents Bot
Supervisor: PR Review | Agent: ca-pr-self-reviewer

## ✅ Review Complete — Clean, spec-aligned bug fix ### Review Summary **Scope**: Single-line production fix + test fixture updates (3 files, 7 insertions, 7 deletions) ### Specification Alignment ✅ - The spec's `agents plan execute` output clearly shows `Branch: cleveragents/plan-01HXM8C2` — this fix aligns the implementation with that requirement. - The `cleveragents/` namespace prefix is the spec-defined namespace for all CleverAgents-managed git branches. - The `plan-` infix correctly distinguishes plan-execution branches from other potential future branch types. ### Correctness ✅ - The production change is a single-line format string update: `f"sandbox/{safe_plan_id}"` → `f"cleveragents/plan-{safe_plan_id}"`. - The `_sanitise_branch_name()` function already handles slashes in its allowed character set, so the `cleveragents/plan-` prefix won't be mangled. - The fallback in `_sanitise_branch_name()` (empty input → `"sandbox"`) would produce `cleveragents/plan-sandbox`, which is still correctly namespaced. - No other code paths reference the old `sandbox/` branch prefix — the change is self-contained. ### Test Quality ✅ - All 4 test fixture updates in `git_worktree_coverage_boost_steps.py` correctly mirror the new naming convention. - The `garbage_collection.feature` scenario fixture is updated to match. - No test logic was altered — only expected branch name strings, which is correct for a naming convention fix. - Verified via grep that no stale `sandbox/<plan_id>` branch name references remain in test files on this branch. ### PR Metadata ✅ - **Commit message**: Conventional Changelog format (`fix(sandbox): ...`) with `ISSUES CLOSED: #2601` footer ✓ - **PR body**: Contains `Closes #2601` ✓ - **Label**: `Type/Bug` ✓ - **Milestone**: `v3.3.0` ✓ - **Single commit**: Clean history ✓ ### CI Status - lint ✅ | typecheck ✅ | security ✅ | quality ✅ | unit_tests ✅ | integration_tests ✅ | e2e_tests ✅ | build ✅ | helm ✅ - coverage, benchmark, docker, status-check: pending (waiting for upstream jobs) Scheduling merge for when all checks complete. --- **Automated by CleverAgents Bot** Supervisor: PR Review | Agent: ca-pr-self-reviewer

freemo scheduled this pull request to auto merge when all checks succeed 2026-04-05 10:04:56 +00:00

freemo referenced this pull request 2026-04-05 10:07:21 +00:00

UAT: `GitWorktreeSandbox` creates branch named `sandbox/<plan_id>` instead of spec-required `cleveragents/plan-<plan_id>` #2601

freemo referenced this pull request 2026-04-05 10:24:17 +00:00

UAT: `GitWorktreeSandbox` creates branch named `sandbox/<plan_id>` instead of spec-required `cleveragents/plan-<plan_id>` #2601

freemo referenced this pull request 2026-04-05 19:48:58 +00:00

[Automated] CleverAgents Build Session - 2026-04-05 #3377

freemo reviewed 2026-04-05 19:49:30 +00:00

freemo left a comment

Author

Owner

Copy Link

Copy Source

Review Summary — LGTM ✅ (Self-Review)

Note

: This review would be APPROVED but Forgejo prevents self-approval. Posting as COMMENT for the record. External reviewers: this PR is recommended for approval.

Reviewed PR #3263 with focus on specification-compliance, requirements-coverage, and behavior-correctness.

Scope

Single-line production fix + docstring update in git_worktree.py, plus 4 test fixture updates across 2 test files. Clean, minimal blast radius.

Deep Dive Results

Specification Compliance ✅

• The spec's agents plan execute output clearly shows Branch: cleveragents/plan-01HXM8C2 — this fix aligns the implementation with that requirement.
• The cleveragents/ namespace prefix is the spec-defined namespace for all CleverAgents-managed git branches.
• The plan- infix correctly distinguishes plan-execution branches from other potential future branch types under the cleveragents/ namespace.
• Verified via independent search: no other code paths in src/ reference the old sandbox/ branch prefix pattern — the change is self-contained.

Requirements Coverage ✅

• All 3 subtasks from issue #2601 are addressed:
  1. ✓ Branch name format changed from sandbox/<plan_id> to cleveragents/plan-<plan_id>
  2. ✓ create() docstring updated to reflect new naming
  3. ✓ Unit tests updated with new branch name format
• Definition of Done criteria from the issue are fully satisfied.

Behavior Correctness ✅

• The _sanitise_branch_name() regex ([^a-zA-Z0-9/_.\-]+) already allows slashes in its character set, so the cleveragents/plan- prefix will not be mangled by sanitisation — verified by reading the regex definition.
• The _sanitise_branch_name() fallback (empty input → "sandbox") would produce cleveragents/plan-sandbox, which is still correctly namespaced under the cleveragents/ prefix. The plan_id validation at the top of create() already rejects empty strings, so this fallback only triggers for strings composed entirely of disallowed characters — an extreme edge case.
• No behavioral regressions: the change only affects the branch name string, not the worktree creation logic, commit flow, rollback, or cleanup.

Test Quality ✅

• All 4 test fixture branch name strings in git_worktree_coverage_boost_steps.py correctly updated:
  • sandbox/test → cleveragents/plan-test
  • sandbox/cleanup-test → cleveragents/plan-cleanup-test
  • sandbox/branch-delete-fail → cleveragents/plan-branch-delete-fail
• garbage_collection.feature scenario fixture updated: sandbox/test-plan → cleveragents/plan-test-plan
• No test logic was altered — only expected branch name strings, which is correct for a naming convention fix.
• Robot Framework integration tests (robot/container_tool_exec.robot) reference /tmp/sandbox/ as a filesystem path, not a branch name — correctly left unchanged.

PR Metadata & Commit Standards ✅

• Commit message: Conventional Changelog format (fix(sandbox): ...) with ISSUES CLOSED: #2601 footer ✓
• PR body: Contains Closes #2601 ✓
• Label: Type/Bug ✓
• Milestone: v3.3.0 (matches issue) ✓
• Single atomic commit: Clean history ✓
• Branch name: fix/git-worktree-branch-naming ✓

Minor Observations (Non-blocking)

1. Pre-existing: _sanitise_branch_name() fallback value — The fallback value on line ~51 is still the string "sandbox", a leftover from the old naming convention. While this is not introduced by this PR and the resulting branch name (cleveragents/plan-sandbox) is still correctly namespaced, a future cleanup could change this to something more semantically appropriate like "unknown" or "default". Consider filing a low-priority follow-up issue.

Decision: APPROVED ✅

---

Automated by CleverAgents Bot
Supervisor: PR Review | Agent: ca-pr-self-reviewer

## Review Summary — LGTM ✅ (Self-Review) > **Note**: This review would be APPROVED but Forgejo prevents self-approval. Posting as COMMENT for the record. External reviewers: this PR is recommended for approval. Reviewed PR #3263 with focus on **specification-compliance**, **requirements-coverage**, and **behavior-correctness**. ### Scope Single-line production fix + docstring update in `git_worktree.py`, plus 4 test fixture updates across 2 test files. Clean, minimal blast radius. ### Deep Dive Results #### Specification Compliance ✅ - The spec's `agents plan execute` output clearly shows `Branch: cleveragents/plan-01HXM8C2` — this fix aligns the implementation with that requirement. - The `cleveragents/` namespace prefix is the spec-defined namespace for all CleverAgents-managed git branches. - The `plan-` infix correctly distinguishes plan-execution branches from other potential future branch types under the `cleveragents/` namespace. - Verified via independent search: no other code paths in `src/` reference the old `sandbox/` branch prefix pattern — the change is self-contained. #### Requirements Coverage ✅ - All 3 subtasks from issue #2601 are addressed: 1. ✓ Branch name format changed from `sandbox/<plan_id>` to `cleveragents/plan-<plan_id>` 2. ✓ `create()` docstring updated to reflect new naming 3. ✓ Unit tests updated with new branch name format - Definition of Done criteria from the issue are fully satisfied. #### Behavior Correctness ✅ - The `_sanitise_branch_name()` regex (`[^a-zA-Z0-9/_.\-]+`) already allows slashes in its character set, so the `cleveragents/plan-` prefix will not be mangled by sanitisation — verified by reading the regex definition. - The `_sanitise_branch_name()` fallback (empty input → `"sandbox"`) would produce `cleveragents/plan-sandbox`, which is still correctly namespaced under the `cleveragents/` prefix. The `plan_id` validation at the top of `create()` already rejects empty strings, so this fallback only triggers for strings composed entirely of disallowed characters — an extreme edge case. - No behavioral regressions: the change only affects the branch name string, not the worktree creation logic, commit flow, rollback, or cleanup. #### Test Quality ✅ - All 4 test fixture branch name strings in `git_worktree_coverage_boost_steps.py` correctly updated: - `sandbox/test` → `cleveragents/plan-test` - `sandbox/cleanup-test` → `cleveragents/plan-cleanup-test` - `sandbox/branch-delete-fail` → `cleveragents/plan-branch-delete-fail` - `garbage_collection.feature` scenario fixture updated: `sandbox/test-plan` → `cleveragents/plan-test-plan` - No test logic was altered — only expected branch name strings, which is correct for a naming convention fix. - Robot Framework integration tests (`robot/container_tool_exec.robot`) reference `/tmp/sandbox/` as a filesystem path, not a branch name — correctly left unchanged. #### PR Metadata & Commit Standards ✅ - **Commit message**: Conventional Changelog format (`fix(sandbox): ...`) with `ISSUES CLOSED: #2601` footer ✓ - **PR body**: Contains `Closes #2601` ✓ - **Label**: `Type/Bug` ✓ - **Milestone**: `v3.3.0` (matches issue) ✓ - **Single atomic commit**: Clean history ✓ - **Branch name**: `fix/git-worktree-branch-naming` ✓ ### Minor Observations (Non-blocking) 1. **Pre-existing: `_sanitise_branch_name()` fallback value** — The fallback value on line ~51 is still the string `"sandbox"`, a leftover from the old naming convention. While this is not introduced by this PR and the resulting branch name (`cleveragents/plan-sandbox`) is still correctly namespaced, a future cleanup could change this to something more semantically appropriate like `"unknown"` or `"default"`. Consider filing a low-priority follow-up issue. **Decision: APPROVED** ✅ --- **Automated by CleverAgents Bot** Supervisor: PR Review | Agent: ca-pr-self-reviewer

freemo referenced this pull request 2026-04-05 20:07:24 +00:00

[Automated] CleverAgents Build Session - 2026-04-05 #3572

freemo referenced this pull request 2026-04-05 21:00:52 +00:00

[Automated] CleverAgents Build Session - 2026-04-05 #3377

freemo merged commit e1fbcf6345 into master 2026-04-05 21:09:06 +00:00

freemo referenced this pull request 2026-04-05 22:16:28 +00:00

[Automated] CleverAgents Build Session - 2026-04-05 (Resumed) #3654

freemo removed this from the v3.3.0 milestone 2026-04-07 00:11:51 +00:00

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.

overdue

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 Label

Milestone

No items

No Milestone

Projects

Clear projects

No project

Assignees

Clear assignees

aditya (Aditya Chhabra) aleenaumair (Aleena Umair) brent.edwards (Brent Edwards) CoreRasurae (Luis Mendes) drew (Drew Morris) eugen.thaci (Eugen Thaci) freemo (Jeffrey Phillips Freeman) HAL9000 (HAL 9000) HAL9001 (HAL9001) hamza.khyari (Hamza Khyari) hurui200320 (Rui Hu) justin.morris khird (Kyle Hird) org.cleveragents

No Assignees

1 Participants

Notifications

Subscribe

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: cleveragents/cleveragents-core#3263