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

fix(security): use relpath containment instead of startswith to prevent prefix-collision bypass #11242

Closed
HAL9000 wants to merge 4 commits from feature/security-fix-relpath-pr-11217 into master
pull from: feature/security-fix-relpath-pr-11217
merge into: cleveragents:master
Conversation 7 Commits 4 Files changed 3 +32 -16
HAL9000 commented 2026-05-17 20:14:45 +00:00
Owner
Copy link

Summary

Replaces insecure str().startswith() path containment checks with proper, canonicalized path containment using os.path.relpath(), Path.is_relative_to(), and Path.relative_to() across three files. This prevents prefix-collision attacks where a malicious path like /tmp/evil could bypass an intended check for paths starting with /tmp/e.

## Summary Replaces insecure `str().startswith()` path containment checks with proper, canonicalized path containment using `os.path.relpath()`, `Path.is_relative_to()`, and `Path.relative_to()` across three files. This prevents prefix-collision attacks where a malicious path like `/tmp/evil` could bypass an intended check for paths starting with `/tmp/e`.
fix(security): use relpath containment instead of startswith to prevent prefix-collision bypass
Some checks failed
CI / push-validation (pull_request) Successful in 31s
Details
CI / helm (pull_request) Successful in 43s
Details
CI / build (pull_request) Successful in 1m13s
Details
CI / lint (pull_request) Successful in 1m46s
Details
CI / quality (pull_request) Successful in 1m51s
Details
CI / security (pull_request) Successful in 1m51s
Details
CI / typecheck (pull_request) Successful in 2m3s
Details
CI / integration_tests (pull_request) Successful in 4m38s
Details
CI / unit_tests (pull_request) Failing after 6m42s
Details
CI / coverage (pull_request) Has been skipped
Details
CI / docker (pull_request) Has been skipped
Details
CI / status-check (pull_request) Failing after 3s
Details
52c7e96d6b 
Replace str().startswith(root) checks with proper relpath-based
containment that prevents prefix-collision bypass attacks where a
sibling directory whose name starts with the root path would pass
an unchecked containment test.

Files changed:
- decomposition_clustering.py: Use os.path.relpath() instead of
  string-prefix matching for root-relative path computation.
- plan.py (_apply_sandbox_changes): Use Path.is_relative_to()
  instead of str.startswith() for sandbox-to-project root check.
- inline_executor.py: Use Path.relative_to() instead of
  str.startswith() for sandbox containment validation.
chore: re-trigger CI [controller]
Some checks failed
CI / lint (pull_request) Successful in 49s
Details
CI / typecheck (pull_request) Successful in 1m10s
Details
CI / push-validation (pull_request) Successful in 35s
Details
CI / helm (pull_request) Successful in 40s
Details
CI / build (pull_request) Successful in 47s
Details
CI / quality (pull_request) Successful in 1m7s
Details
CI / security (pull_request) Successful in 1m54s
Details
CI / integration_tests (pull_request) Failing after 4m10s
Details
CI / unit_tests (pull_request) Failing after 4m30s
Details
CI / coverage (pull_request) Has been skipped
Details
CI / docker (pull_request) Has been skipped
Details
CI / status-check (pull_request) Failing after 3s
Details
4a71e3c368
HAL9000 force-pushed feature/security-fix-relpath-pr-11217 from 4a71e3c368
Some checks failed
CI / lint (pull_request) Successful in 49s
Details
CI / typecheck (pull_request) Successful in 1m10s
Details
CI / push-validation (pull_request) Successful in 35s
Details
CI / helm (pull_request) Successful in 40s
Details
CI / build (pull_request) Successful in 47s
Details
CI / quality (pull_request) Successful in 1m7s
Details
CI / security (pull_request) Successful in 1m54s
Details
CI / integration_tests (pull_request) Failing after 4m10s
Details
CI / unit_tests (pull_request) Failing after 4m30s
Details
CI / coverage (pull_request) Has been skipped
Details
CI / docker (pull_request) Has been skipped
Details
CI / status-check (pull_request) Failing after 3s
Details
to 9d0c5850b3
Some checks failed
CI / build (pull_request) Successful in 35s
Details
CI / lint (pull_request) Successful in 48s
Details
CI / helm (pull_request) Successful in 29s
Details
CI / quality (pull_request) Successful in 1m8s
Details
CI / typecheck (pull_request) Successful in 1m9s
Details
CI / security (pull_request) Successful in 1m18s
Details
CI / push-validation (pull_request) Successful in 21s
Details
CI / integration_tests (pull_request) Successful in 3m54s
Details
CI / unit_tests (pull_request) Failing after 7m11s
Details
CI / coverage (pull_request) Has been skipped
Details
CI / docker (pull_request) Has been skipped
Details
CI / status-check (pull_request) Failing after 3s
Details
2026-05-28 04:09:45 +00:00 Compare 
Two follow-up bugs from the relpath-containment refactor:

1. decomposition_clustering._directory_key had inverted boolean logic:
   `if not (rel == "" or not rel.startswith(".." + os.sep))` meant the
   relative path was used ONLY when it escaped the root, and discarded
   when the path was actually inside the root. Fixed to update
   `normalized` exactly when the path is inside (or equal to) root.

2. inline_executor._validate_paths split the original
   `except (OSError, ValueError)` so that ValueError from
   `Path(value).resolve()` (raised for invalid paths such as those
   containing null bytes) propagated instead of returning a graceful
   "Invalid path" error string.

ISSUES CLOSED: #11217
chore: worker ruff auto-fix (pre-push lint gate)
Some checks failed
CI / push-validation (pull_request) Successful in 22s
Details
CI / build (pull_request) Successful in 33s
Details
CI / helm (pull_request) Successful in 34s
Details
CI / lint (pull_request) Successful in 36s
Details
CI / quality (pull_request) Successful in 1m14s
Details
CI / typecheck (pull_request) Successful in 1m18s
Details
CI / security (pull_request) Successful in 1m19s
Details
CI / integration_tests (pull_request) Failing after 2m54s
Details
CI / unit_tests (pull_request) Successful in 4m46s
Details
CI / docker (pull_request) Successful in 1m36s
Details
CI / coverage (pull_request) Successful in 11m13s
Details
CI / status-check (pull_request) Failing after 3s
Details
0aff794f69
HAL9000 commented 2026-05-28 13:46:14 +00:00
Author
Owner
Copy link

[CONTROLLER-DEFER:Gate 1:needs_evaluation]

This PR has been deferred for re-evaluation. The controller has stepped back
from processing it. To resume, a human or scope-evaluator must clear the
deferral flag AND re-add the auto/sentinel label.

Decision:

  • Gate: Gate 1
  • Reason category: needs_evaluation
  • Canonical: #-
  • LLM confidence: medium
  • LLM reasoning: PR #11242 (anchor) and PR #11217 have identical titles and both fix the same security issue (#7478) using the relpath containment approach. The anchor's head branch name explicitly references "#11217", indicating it builds on that work. However, #11242 has 4.5x larger scope (32 additions vs 7, covering 3 files vs 1). This could represent: (1) necessary comprehensive coverage of the vulnerability across the codebase, or (2) redundant extension beyond what #11217 sufficiently addresses. Human judgment required to determine if #11242's broader file coverage is essential or unnecessary.
  • Preserved value (when applicable): PR #11242 applies the security fix to 3 files across the codebase (32 additions, 16 deletions), while PR #11217 covers only 1 file (7 additions, 1 deletion). The broader scope in the anchor may be necessary for comprehensive security coverage against prefix-collision bypass attacks across all vulnerable code paths, or may represent over-engineering if the issue is adequately addressed by PR #11217's focused approach.

To clear the deferral (SQL):
UPDATE workflows SET deferred_reason=NULL,
deferred_at=NULL,
deferred_target_workflow_id=NULL
WHERE workflow_id = 8;

INSERT INTO controller_events
  (workflow_id, ts, event_type, payload, cause, forgejo_write_pending, replay_attempts)
VALUES (8, datetime('now'), 'deferral_cleared',
        json_object('cleared_by', 'operator', 'reason', '<your reason>'),
        'operator', 0, 0);

Audit ID: 1354

Automated by the CleverAgents controller pipeline.
Identity: HAL9000 (pipeline action)

[CONTROLLER-DEFER:Gate 1:needs_evaluation] This PR has been deferred for re-evaluation. The controller has stepped back from processing it. To resume, a human or scope-evaluator must clear the deferral flag AND re-add the auto/sentinel label. Decision: - Gate: Gate 1 - Reason category: needs_evaluation - Canonical: #- - LLM confidence: medium - LLM reasoning: PR #11242 (anchor) and PR #11217 have identical titles and both fix the same security issue (#7478) using the relpath containment approach. The anchor's head branch name explicitly references "#11217", indicating it builds on that work. However, #11242 has 4.5x larger scope (32 additions vs 7, covering 3 files vs 1). This could represent: (1) necessary comprehensive coverage of the vulnerability across the codebase, or (2) redundant extension beyond what #11217 sufficiently addresses. Human judgment required to determine if #11242's broader file coverage is essential or unnecessary. - Preserved value (when applicable): PR #11242 applies the security fix to 3 files across the codebase (32 additions, 16 deletions), while PR #11217 covers only 1 file (7 additions, 1 deletion). The broader scope in the anchor may be necessary for comprehensive security coverage against prefix-collision bypass attacks across all vulnerable code paths, or may represent over-engineering if the issue is adequately addressed by PR #11217's focused approach. To clear the deferral (SQL): UPDATE workflows SET deferred_reason=NULL, deferred_at=NULL, deferred_target_workflow_id=NULL WHERE workflow_id = 8; INSERT INTO controller_events (workflow_id, ts, event_type, payload, cause, forgejo_write_pending, replay_attempts) VALUES (8, datetime('now'), 'deferral_cleared', json_object('cleared_by', 'operator', 'reason', '<your reason>'), 'operator', 0, 0); Audit ID: 1354 --- Automated by the CleverAgents controller pipeline. Identity: HAL9000 (pipeline action) <!-- controller:fingerprint:9ad2f404a97cfcfc -->
HAL9000 commented 2026-05-31 16:07:56 +00:00
Author
Owner
Copy link

event occurred 2026-05-28T04:07:37.990738+00:00

📋 Estimate: tier 1.

3-file security fix replacing startswith with proper path containment (relpath/is_relative_to/relative_to). CI is failing with specific actor-related test regressions in both unit and integration gates — Unknown Actor Name Error and Actor App Unknown Name Error — indicating the path containment changes broke actor name/path resolution logic. Not flaky CI; the implementer must diagnose the regression across the actor subsystem, fix without undoing the security improvement, and validate across both test suites. Cross-file context and actor path resolution understanding required.

*event occurred 2026-05-28T04:07:37.990738+00:00* **📋 Estimate: tier 1.** 3-file security fix replacing startswith with proper path containment (relpath/is_relative_to/relative_to). CI is failing with specific actor-related test regressions in both unit and integration gates — Unknown Actor Name Error and Actor App Unknown Name Error — indicating the path containment changes broke actor name/path resolution logic. Not flaky CI; the implementer must diagnose the regression across the actor subsystem, fix without undoing the security improvement, and validate across both test suites. Cross-file context and actor path resolution understanding required. <!-- controller:fingerprint:a03b71092739c97b -->
HAL9000 commented 2026-05-31 16:08:02 +00:00
Author
Owner
Copy link

(attempt #3, tier 1)

event occurred 2026-05-28T04:12:01.850398+00:00

🔧 Implementer attempt — rebased.

Pushed 1 commit: 9d0c585.

_(attempt #3, tier 1)_ *event occurred 2026-05-28T04:12:01.850398+00:00* **🔧 Implementer attempt — `rebased`.** Pushed 1 commit: `9d0c585`. <!-- controller:fingerprint:19814f3a0f3eda93 -->
HAL9000 commented 2026-05-31 16:08:03 +00:00
Author
Owner
Copy link

(attempt #4, tier 1)

event occurred 2026-05-28T04:28:00.712692+00:00

🔧 Implementer attempt — ci-not-ready.

_(attempt #4, tier 1)_ *event occurred 2026-05-28T04:28:00.712692+00:00* **🔧 Implementer attempt — `ci-not-ready`.** <!-- controller:fingerprint:55f774579ce443f6 -->
HAL9000 commented 2026-05-31 16:08:04 +00:00
Author
Owner
Copy link

(attempt #8, tier 1)

event occurred 2026-05-28T10:42:21.506801+00:00

🔧 Implementer attempt — resolved.

Pushed 2 commits: ba1b2e2, 0aff794.

Files touched: src/cleveragents/application/services/decomposition_clustering.py, src/cleveragents/skills/inline_executor.py.

_(attempt #8, tier 1)_ *event occurred 2026-05-28T10:42:21.506801+00:00* **🔧 Implementer attempt — `resolved`.** Pushed 2 commits: `ba1b2e2`, `0aff794`. Files touched: `src/cleveragents/application/services/decomposition_clustering.py`, `src/cleveragents/skills/inline_executor.py`. <!-- controller:fingerprint:af7c5016e5b88ab1 -->
HAL9000 commented 2026-05-31 16:08:05 +00:00
Author
Owner
Copy link

(attempt #9, tier 2)

event occurred 2026-05-28T11:11:30.953087+00:00

🔧 Implementer attempt — blocked.

Blockers:

  • CI integration_tests reports 'Plan Use And Execute With Custom Actor' (robot/m2_e2e_verification.robot) FAILED on head 0aff794f, but the same test passes locally on the exact head SHA. Verified twice: (1) standalone -t 'Plan Use And Execute With Custom Actor' on robot/m2_e2e_verification.robot — PASS in 51s; (2) full pabot --processes 64 m2 suite + entire robot/ directory — 2014 tests, 2014 passed, this test PASSED in 98.7s. No Traceback or unhandled INTERNAL error is visible in the CI log excerpt; only the Robot framework FAIL summary line. The test exercises 'agents plan use' + 'agents plan execute' for a plan in strategize/queued state expecting a controlled 'not ready' rejection. The 3 files in this PR's diff (decomposition_clustering.py, plan.py, inline_executor.py) implement a relpath-containment security fix and are not exercised by this test path (plan is rejected before sandbox apply runs; decomposition_clustering._directory_key is not on the plan-use/execute path). No reproducible local failure to root-cause, and noop is not satisfiable because CI overall_state=failure. Suspected CI runner flake (act/docker environment, parallel-test contention, or external runner reaper). Recommend retrigger or inspect run 21299 job 5 raw log beyond the FAIL summary line for actual failure detail.
_(attempt #9, tier 2)_ *event occurred 2026-05-28T11:11:30.953087+00:00* **🔧 Implementer attempt — `blocked`.** Blockers: - CI integration_tests reports 'Plan Use And Execute With Custom Actor' (robot/m2_e2e_verification.robot) FAILED on head 0aff794f, but the same test passes locally on the exact head SHA. Verified twice: (1) standalone -t 'Plan Use And Execute With Custom Actor' on robot/m2_e2e_verification.robot — PASS in 51s; (2) full pabot --processes 64 m2 suite + entire robot/ directory — 2014 tests, 2014 passed, this test PASSED in 98.7s. No Traceback or unhandled INTERNAL error is visible in the CI log excerpt; only the Robot framework FAIL summary line. The test exercises 'agents plan use' + 'agents plan execute' for a plan in strategize/queued state expecting a controlled 'not ready' rejection. The 3 files in this PR's diff (decomposition_clustering.py, plan.py, inline_executor.py) implement a relpath-containment security fix and are not exercised by this test path (plan is rejected before sandbox apply runs; decomposition_clustering._directory_key is not on the plan-use/execute path). No reproducible local failure to root-cause, and noop is not satisfiable because CI overall_state=failure. Suspected CI runner flake (act/docker environment, parallel-test contention, or external runner reaper). Recommend retrigger or inspect run 21299 job 5 raw log beyond the FAIL summary line for actual failure detail. <!-- controller:fingerprint:86a44b06fc4c4637 -->
HAL9000 commented 2026-06-18 12:02:05 +00:00
Author
Owner
Copy link

Closing as redundant: the relpath-containment security fix (issue #7478) has already merged; issue #7478 is closed.

Automated canonical-selection cleanup of the controller's duplicate deferred queue.

Closing as redundant: the relpath-containment security fix (issue #7478) has already merged; issue #7478 is closed. _Automated canonical-selection cleanup of the controller's duplicate deferred queue._
HAL9000 2026-06-18 12:02:05 +00:00
  • closed this pull request
  • removed the
    State
    Paused
         label
Some checks failed
CI / push-validation (pull_request) Successful in 22s
Details
CI / build (pull_request) Successful in 33s
Required
Details
CI / helm (pull_request) Successful in 34s
Details
CI / lint (pull_request) Successful in 36s
Required
Details
CI / quality (pull_request) Successful in 1m14s
Required
Details
CI / typecheck (pull_request) Successful in 1m18s
Required
Details
CI / security (pull_request) Successful in 1m19s
Required
Details
CI / integration_tests (pull_request) Failing after 2m54s
Required
Details
CI / unit_tests (pull_request) Successful in 4m46s
Required
Details
CI / docker (pull_request) Successful in 1m36s
Required
Details
CI / coverage (pull_request) Successful in 11m13s
Required
Details
CI / status-check (pull_request) Failing after 3s
Details

Pull request closed

Please reopen this pull request to perform a merge.
Sign in to join this conversation.
Reviewers
No reviewers
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 labels
auto/needs-reevaluation
controller-managed
overdue
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
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
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!11242
No description provided.