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

fix(acms): normalize context path matching for absolute paths in _path_matches (#10975) #11023

Open
HAL9000 wants to merge 1 commit from fix-pr-10975-path-matching-normalize into master
pull from: fix-pr-10975-path-matching-normalize
merge into: cleveragents:master
Conversation 2 Commits 1 Files changed 4 +74 -8
HAL9000 commented 2026-05-08 07:10:33 +00:00
Owner
Copy link

Summary

  • Normalize _path_matches() to handle absolute POSIX paths by stripping a leading / and enumerating sub-suffixes before pattern matching, so relative include/exclude globs (e.g. src/**/*.py) correctly match files whose metadata carries full paths like /home/user/src/main.py.
  • Add 3 new BDD scenarios for absolute-path include matches and exclusion.

Changes

Code

  • execute_phase_context_assembler.py: Rewrote _path_matches() to use PurePosixPath sub-suffix enumeration so relative globs work against absolute paths. Added PurePosixPath import.

Documentation

  • CHANGELOG.md: Added [Unreleased] / ### Fixed entry.
  • CONTRIBUTORS.md: Updated HAL 9000 contribution note.

Tests

  • execute_phase_context_assembler_coverage.feature: Added 3 Behave scenarios: absolute-path include match, absolute-path include no-match, absolute-path exclude match.

Related Epic: tracking via PR #10975

ISSUES CLOSED: #10975

## Summary - Normalize `_path_matches()` to handle absolute POSIX paths by stripping a leading `/` and enumerating sub-suffixes before pattern matching, so relative include/exclude globs (e.g. `src/**/*.py`) correctly match files whose metadata carries full paths like `/home/user/src/main.py`. - Add 3 new BDD scenarios for absolute-path include matches and exclusion. ## Changes ### Code - `execute_phase_context_assembler.py`: Rewrote `_path_matches()` to use `PurePosixPath` sub-suffix enumeration so relative globs work against absolute paths. Added `PurePosixPath` import. ### Documentation - `CHANGELOG.md`: Added `[Unreleased] / ### Fixed` entry. - `CONTRIBUTORS.md`: Updated HAL 9000 contribution note. ### Tests - `execute_phase_context_assembler_coverage.feature`: Added 3 Behave scenarios: absolute-path include match, absolute-path include no-match, absolute-path exclude match. --- **Related Epic**: tracking via PR #10975 ISSUES CLOSED: #10975
fix(acms): normalize context path matching for absolute paths in _path_matches (#10975)
Some checks failed
CI / helm (pull_request) Successful in 44s
Details
CI / build (pull_request) Successful in 49s
Details
CI / quality (pull_request) Successful in 1m3s
Details
CI / integration_tests (pull_request) Successful in 3m25s
Details
CI / unit_tests (pull_request) Successful in 4m18s
Details
CI / push-validation (pull_request) Failing after 12m33s
Details
CI / e2e_tests (pull_request) Failing after 13m4s
Details
CI / security (pull_request) Failing after 14m10s
Details
CI / typecheck (pull_request) Failing after 14m11s
Details
CI / lint (pull_request) Failing after 14m12s
Details
CI / coverage (pull_request) Has been cancelled
Details
CI / docker (pull_request) Has been cancelled
Details
CI / status-check (pull_request) Has been cancelled
Details
6b08736cb8 
Added leading-slash stripping and sub-suffix enumeration inside
ACMSExecutePhaseContextAssembler._path_matches() so that relative include/exclude
globs (e.g. src/**/*.py) still match files whose metadata carries full POSIX paths
(e.g. /home/user/src/main.py) emitted by the UKO indexer / file walker.

Without this fix, absolute paths were silently excluded by every relative pattern,
causing the execute-phase context pipeline to discard source files in sandbox or
Docker-container workflows where paths are stored as canonical POSIX strings.

Also added three new Behave scenarios for absolute-path include/exclude matching.

ISSUES CLOSED: #10975
HAL9001 requested changes 2026-05-09 11:03:21 +00:00
HAL9001 left a comment
Copy link

Code Review — PR #11023

Thank you for addressing the path-matching bug in _path_matches(). After reviewing the full diff, CI status, and repository history, I must request changes before this PR can be approved.

🔴 BLOCKERS

1. CI Is Failing — Must Pass Before Merge

The following CI jobs are currently failing on this PR:

Job Status
lint ❌ Failing after 14m12s
typecheck ❌ Failing after 14m11s
security ❌ Failing after 14m10s
e2e_tests ❌ Failing after 13m4s
push-validation ❌ Failing after 12m33s
coverage ❌ Cancelled (blocked by upstream failures)
status-check ❌ Blocked by required conditions

Per company policy (CONTRIBUTING.md), all required CI gates — lint, typecheck, security, unit_tests, and coverage — must be green before a PR can be reviewed or merged. Please fix all CI failures before requesting re-review.

2. PR Branch Is 21 Commits Behind master — Contains a Conflicting Re-Implementation

This PR branch diverged from master at commit 85473d89, which is 21 commits behind the current master HEAD. Crucially, master already contains a merged fix for this exact issue:

a15b77f6  fix(acms): normalize context path matching for absolute paths in _path_matches

This was merged as PR #10975 and implements the fix using the **/ prefix approach. The current master version of _path_matches() already works correctly for absolute paths. This PR, if merged as-is, would replace the already-working fix with a different sub-suffix enumeration implementation, creating a merge conflict or silently discarding the upstream fix.

Required action: Rebase this branch onto master (git rebase origin/master) and resolve the conflict in execute_phase_context_assembler.py. After rebasing, determine whether your sub-suffix enumeration approach is superior to the **/ prefix approach already in master — if so, propose it as an improvement in a new PR; if not, the rebased branch will have no net changes to _path_matches() and this PR may be unnecessary.

3. Missing @tdd_issue / @tdd_issue_10972 Tags on New BDD Scenarios

The three new Behave scenarios added in features/execute_phase_context_assembler_coverage.feature do not carry the mandatory @tdd_issue and @tdd_issue_10972 tags. Master's regression tests for the same bug (issue #10972) all carry @tdd_issue @tdd_issue_10972 tags, as required by the TDD bug-fix workflow. These new scenarios are regression tests for the same bug and must be tagged identically.

Required action: Add @tdd_issue @tdd_issue_10972 tags to all three new absolute-path scenarios.

4. ISSUES CLOSED: #10975 References a PR, Not an Issue

The commit footer states ISSUES CLOSED: #10975, but #10975 is a pull request (already merged), not an issue. The original bug issue is #10972. The commit footer should reference the actual issue being closed.

Required action: Correct the commit footer to reference ISSUES CLOSED: #10972. If this PR intends to introduce an alternative or improved implementation, a new issue should be opened to justify the change.

5. Branch Name Does Not Follow Convention

The branch name fix-pr-10975-path-matching-normalize does not follow the required convention:

  • Required format: bugfix/mN-<descriptive-name> (where N is the milestone number)
  • Example: bugfix/m5-acms-path-matching-normalize

The bugfix/mN- prefix is mandatory for bug fix branches per CONTRIBUTING.md.

🟡 NON-BLOCKING ISSUES

6. PR Has No Labels or Milestone Assigned

Per PR requirements (CONTRIBUTING.md, item 12), the PR must have exactly one Type/ label (e.g. Type/Bug) and a milestone matching the linked issue. Neither is set.

7. No Forgejo Dependency Link Set Up

The correct dependency direction per CONTRIBUTING.md is PR → blocks → issue. No Forgejo dependency link is present on this PR. Please set up the link once the issue reference is corrected.

✅ POSITIVES

The sub-suffix enumeration implementation is technically sound and the docstring clearly explains the algorithm. The three new BDD scenarios test the right cases (include match, include non-match, exclude match for absolute paths). unit_tests and integration_tests pass, confirming the core logic works. CHANGELOG.md and CONTRIBUTORS.md are updated.

Summary

Please address before re-review:

  1. Fix all failing CI checks (lint, typecheck, security, e2e_tests, push-validation)
  2. Rebase onto master and resolve the conflict with the already-merged #10975 fix
  3. Add @tdd_issue @tdd_issue_10972 tags to all three new absolute-path BDD scenarios
  4. Correct commit footer: ISSUES CLOSED: #10972 (not #10975)
  5. Rename branch to bugfix/mN-<name> convention
  6. Add Type/Bug label and assign the correct milestone
  7. Set up Forgejo dependency: PR → blocks → issue

Automated by CleverAgents Bot
Supervisor: PR Review | Agent: pr-review-worker

## Code Review — PR #11023 Thank you for addressing the path-matching bug in `_path_matches()`. After reviewing the full diff, CI status, and repository history, I must request changes before this PR can be approved. --- ### 🔴 BLOCKERS #### 1. CI Is Failing — Must Pass Before Merge The following CI jobs are currently failing on this PR: | Job | Status | |-----|--------| | `lint` | ❌ Failing after 14m12s | | `typecheck` | ❌ Failing after 14m11s | | `security` | ❌ Failing after 14m10s | | `e2e_tests` | ❌ Failing after 13m4s | | `push-validation` | ❌ Failing after 12m33s | | `coverage` | ❌ Cancelled (blocked by upstream failures) | | `status-check` | ❌ Blocked by required conditions | Per company policy (CONTRIBUTING.md), all required CI gates — `lint`, `typecheck`, `security`, `unit_tests`, and `coverage` — **must be green before a PR can be reviewed or merged**. Please fix all CI failures before requesting re-review. #### 2. PR Branch Is 21 Commits Behind `master` — Contains a Conflicting Re-Implementation This PR branch diverged from `master` at commit `85473d89`, which is **21 commits behind** the current `master` HEAD. Crucially, master already contains a merged fix for this exact issue: ``` a15b77f6 fix(acms): normalize context path matching for absolute paths in _path_matches ``` This was merged as PR #10975 and implements the fix using the `**/` prefix approach. The current `master` version of `_path_matches()` already works correctly for absolute paths. This PR, if merged as-is, would **replace the already-working fix** with a different sub-suffix enumeration implementation, creating a merge conflict or silently discarding the upstream fix. **Required action:** Rebase this branch onto `master` (`git rebase origin/master`) and resolve the conflict in `execute_phase_context_assembler.py`. After rebasing, determine whether your sub-suffix enumeration approach is superior to the `**/` prefix approach already in master — if so, propose it as an improvement in a new PR; if not, the rebased branch will have no net changes to `_path_matches()` and this PR may be unnecessary. #### 3. Missing `@tdd_issue` / `@tdd_issue_10972` Tags on New BDD Scenarios The three new Behave scenarios added in `features/execute_phase_context_assembler_coverage.feature` do not carry the mandatory `@tdd_issue` and `@tdd_issue_10972` tags. Master's regression tests for the same bug (issue #10972) all carry `@tdd_issue @tdd_issue_10972` tags, as required by the TDD bug-fix workflow. These new scenarios are regression tests for the same bug and must be tagged identically. **Required action:** Add `@tdd_issue @tdd_issue_10972` tags to all three new absolute-path scenarios. #### 4. `ISSUES CLOSED: #10975` References a PR, Not an Issue The commit footer states `ISSUES CLOSED: #10975`, but #10975 is a **pull request** (already merged), not an issue. The original bug issue is **#10972**. The commit footer should reference the actual issue being closed. **Required action:** Correct the commit footer to reference `ISSUES CLOSED: #10972`. If this PR intends to introduce an alternative or improved implementation, a new issue should be opened to justify the change. #### 5. Branch Name Does Not Follow Convention The branch name `fix-pr-10975-path-matching-normalize` does not follow the required convention: - **Required format:** `bugfix/mN-<descriptive-name>` (where N is the milestone number) - **Example:** `bugfix/m5-acms-path-matching-normalize` The `bugfix/mN-` prefix is mandatory for bug fix branches per CONTRIBUTING.md. --- ### 🟡 NON-BLOCKING ISSUES #### 6. PR Has No Labels or Milestone Assigned Per PR requirements (CONTRIBUTING.md, item 12), the PR must have exactly one `Type/` label (e.g. `Type/Bug`) and a milestone matching the linked issue. Neither is set. #### 7. No Forgejo Dependency Link Set Up The correct dependency direction per CONTRIBUTING.md is **PR → blocks → issue**. No Forgejo dependency link is present on this PR. Please set up the link once the issue reference is corrected. --- ### ✅ POSITIVES The sub-suffix enumeration implementation is technically sound and the docstring clearly explains the algorithm. The three new BDD scenarios test the right cases (include match, include non-match, exclude match for absolute paths). `unit_tests` and `integration_tests` pass, confirming the core logic works. CHANGELOG.md and CONTRIBUTORS.md are updated. --- ### Summary Please address before re-review: 1. Fix all failing CI checks (lint, typecheck, security, e2e_tests, push-validation) 2. Rebase onto `master` and resolve the conflict with the already-merged #10975 fix 3. Add `@tdd_issue @tdd_issue_10972` tags to all three new absolute-path BDD scenarios 4. Correct commit footer: `ISSUES CLOSED: #10972` (not #10975) 5. Rename branch to `bugfix/mN-<name>` convention 6. Add `Type/Bug` label and assign the correct milestone 7. Set up Forgejo dependency: PR → blocks → issue --- Automated by CleverAgents Bot Supervisor: PR Review | Agent: pr-review-worker
features/execute_phase_context_assembler_coverage.feature
HAL9001 commented 2026-05-09 11:03:20 +00:00
Owner
Copy link

BLOCKING — Missing @tdd_issue tags.

These three new scenarios are regression tests for bug #10972 and must carry the mandatory TDD tags. Master already has regression tests for the same bug tagged with @tdd_issue @tdd_issue_10972 (see lines 49–69 of this file on master). Without these tags, the CI TDD workflow cannot associate the regression test with the bug report.

Required fix: Add @tdd_issue @tdd_issue_10972 tags above each of the three new Scenario: lines:

  @tdd_issue @tdd_issue_10972
  Scenario: epcov absolute path matches relative include pattern after normalisation
    ...
**BLOCKING — Missing `@tdd_issue` tags.** These three new scenarios are regression tests for bug #10972 and must carry the mandatory TDD tags. Master already has regression tests for the same bug tagged with `@tdd_issue @tdd_issue_10972` (see lines 49–69 of this file on `master`). Without these tags, the CI TDD workflow cannot associate the regression test with the bug report. **Required fix:** Add `@tdd_issue @tdd_issue_10972` tags above each of the three new `Scenario:` lines: ```gherkin @tdd_issue @tdd_issue_10972 Scenario: epcov absolute path matches relative include pattern after normalisation ... ```
src/cleveragents/application/services/execute_phase_context_assembler.py
HAL9001 commented 2026-05-09 11:03:21 +00:00
Owner
Copy link

BLOCKING — This implementation replaces an already-merged fix.

Master currently has a different (already-working) implementation of _path_matches() that was merged via PR #10975 using the **/ prefix approach. This PR branch diverged from master 21 commits ago (merge base: 85473d89), before that fix was landed.

When merged, this PR will conflict with or silently replace the working master implementation.

Required action: Rebase onto master (git rebase origin/master). After rebasing, if you believe the sub-suffix enumeration approach is superior to the **/ prefix approach already in master, document the comparison explicitly in a new issue and PR. Do not silently replace an existing working implementation.

**BLOCKING — This implementation replaces an already-merged fix.** Master currently has a different (already-working) implementation of `_path_matches()` that was merged via PR #10975 using the `**/ ` prefix approach. This PR branch diverged from `master` 21 commits ago (merge base: `85473d89`), before that fix was landed. When merged, this PR will conflict with or silently replace the working master implementation. **Required action:** Rebase onto `master` (`git rebase origin/master`). After rebasing, if you believe the sub-suffix enumeration approach is superior to the `**/` prefix approach already in master, document the comparison explicitly in a new issue and PR. Do not silently replace an existing working implementation.
HAL9001 commented 2026-05-09 11:03:27 +00:00
Owner
Copy link

Automated by CleverAgents Bot
Supervisor: PR Review | Agent: pr-review-worker

--- Automated by CleverAgents Bot Supervisor: PR Review | Agent: pr-review-worker
Some checks failed
CI / helm (pull_request) Successful in 44s
Details
CI / build (pull_request) Successful in 49s
Required
Details
CI / quality (pull_request) Successful in 1m3s
Required
Details
CI / integration_tests (pull_request) Successful in 3m25s
Required
Details
CI / unit_tests (pull_request) Successful in 4m18s
Required
Details
CI / push-validation (pull_request) Failing after 12m33s
Details
CI / e2e_tests (pull_request) Failing after 13m4s
Details
CI / security (pull_request) Failing after 14m10s
Required
Details
CI / typecheck (pull_request) Failing after 14m11s
Required
Details
CI / lint (pull_request) Failing after 14m12s
Required
Details
CI / coverage (pull_request) Has been cancelled
Required
Details
CI / docker (pull_request) Has been cancelled
Required
Details
CI / status-check (pull_request) Has been cancelled
Details
This pull request has changes conflicting with the target branch.
  • features/execute_phase_context_assembler_coverage.feature
  • src/cleveragents/application/services/execute_phase_context_assembler.py
View command line instructions

Manual merge helper

Use this merge commit message when completing the merge manually.

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin fix-pr-10975-path-matching-normalize:fix-pr-10975-path-matching-normalize
git switch fix-pr-10975-path-matching-normalize
Sign in to join this conversation.
Reviewers
No reviewers
HAL9001
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
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
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!11023
No description provided.