fix(test): remove lingering @tdd_expected_fail tags for closed bugs #821 and #932 #1229

Merged

freemo merged 1 commit from feature/m3-tdd-tag-cleanup-821-932 into master 2026-04-02 16:51:16 +00:00

Conversation 5 Commits 1 Files changed 2 +12 -26

brent.edwards commented 2026-03-31 11:33:04 +00:00

Member

Copy link

Summary

Removes stale @tdd_expected_fail references from TDD test files for fixed bugs #821 (ACMS context tier runtime) and #932 (plan apply --yes flag). Both bugs are closed on Forgejo and the @tdd_expected_fail tags were already absent from the tag lines, but the feature description and step-definition docstring for bug #821 still referenced the tag and described the bug as unfixed.

Changes

features/tdd_context_tier_runtime.feature (bug #821)

• Updated feature description to reflect that bug #821 is fixed and ContextTierService now has working runtime promotion/demotion/eviction logic.
• Removed stale references to @tdd_expected_fail tag and "will FAIL until the bug is fixed" language.
• Permanent tags @tdd_issue @tdd_issue_821 @mock_only remain in place per CONTRIBUTING.md.

features/steps/tdd_context_tier_runtime_steps.py (bug #821)

• Updated module docstring to reflect that the bug is fixed and these tests serve as permanent regression guards.
• Removed stale references to @tdd_expected_fail tag.

features/tdd_plan_apply_yes_flag.feature (bug #932)

• No changes needed — the @tdd_expected_fail tag was already absent and no stale descriptions existed.
• Permanent tags @tdd_issue @tdd_issue_932 remain in place per CONTRIBUTING.md.

Tag Naming Convention Note

The issue acceptance criteria reference @tdd_bug / @tdd_bug_<N> as permanent tags. Per CONTRIBUTING.md (TDD Issue Test Tags section), the correct permanent tag naming is @tdd_issue / @tdd_issue_<N>. Both files already use the correct convention. No tag rename is needed.

Quality Gates

All nox sessions pass:

Session	Result
lint	✅ PASS
format	✅ PASS
typecheck	✅ PASS
security_scan	✅ PASS
dead_code	✅ PASS
unit_tests-3.13	✅ PASS (508 features, 12985 scenarios, 0 failures)
integration_tests-3.13	✅ PASS
docs	✅ PASS
build-3.13	✅ PASS
benchmark	✅ PASS
coverage_report	✅ PASS (97%, meets ≥97% threshold)

Closes #1206

## Summary Removes stale `@tdd_expected_fail` references from TDD test files for fixed bugs #821 (ACMS context tier runtime) and #932 (plan apply --yes flag). Both bugs are closed on Forgejo and the `@tdd_expected_fail` tags were already absent from the tag lines, but the feature description and step-definition docstring for bug #821 still referenced the tag and described the bug as unfixed. ## Changes ### `features/tdd_context_tier_runtime.feature` (bug #821) - Updated feature description to reflect that bug #821 is fixed and ContextTierService now has working runtime promotion/demotion/eviction logic. - Removed stale references to `@tdd_expected_fail` tag and "will FAIL until the bug is fixed" language. - Permanent tags `@tdd_issue @tdd_issue_821 @mock_only` remain in place per CONTRIBUTING.md. ### `features/steps/tdd_context_tier_runtime_steps.py` (bug #821) - Updated module docstring to reflect that the bug is fixed and these tests serve as permanent regression guards. - Removed stale references to `@tdd_expected_fail` tag. ### `features/tdd_plan_apply_yes_flag.feature` (bug #932) - No changes needed — the `@tdd_expected_fail` tag was already absent and no stale descriptions existed. - Permanent tags `@tdd_issue @tdd_issue_932` remain in place per CONTRIBUTING.md. ## Tag Naming Convention Note The issue acceptance criteria reference `@tdd_bug` / `@tdd_bug_<N>` as permanent tags. Per CONTRIBUTING.md (TDD Issue Test Tags section), the correct permanent tag naming is `@tdd_issue` / `@tdd_issue_<N>`. Both files already use the correct convention. No tag rename is needed. ## Quality Gates All nox sessions pass: | Session | Result | |---------|--------| | `lint` | ✅ PASS | | `format` | ✅ PASS | | `typecheck` | ✅ PASS | | `security_scan` | ✅ PASS | | `dead_code` | ✅ PASS | | `unit_tests-3.13` | ✅ PASS (508 features, 12985 scenarios, 0 failures) | | `integration_tests-3.13` | ✅ PASS | | `docs` | ✅ PASS | | `build-3.13` | ✅ PASS | | `benchmark` | ✅ PASS | | `coverage_report` | ✅ PASS (97%, meets ≥97% threshold) | Closes #1206

brent.edwards added 1 commit 2026-03-31 11:33:04 +00:00

fix(test): remove lingering @tdd_expected_fail tags for closed bugs #821 and #932 ... 2fc6fe83c0

The @tdd_expected_fail tag was already absent from the tag lines of both
features/tdd_context_tier_runtime.feature (bug #821) and
features/tdd_plan_apply_yes_flag.feature (bug #932). However, the feature
description and step-definition docstring for bug #821 still referenced the
@tdd_expected_fail tag and described the bug as unfixed.

Updated the feature description in tdd_context_tier_runtime.feature and the
module docstring in tdd_context_tier_runtime_steps.py to reflect that bug #821
has been fixed and these tests now serve as permanent regression guards. No
changes were needed for bug #932 as its files had no stale references.

Permanent tags @tdd_issue / @tdd_issue_821 and @tdd_issue / @tdd_issue_932
remain in place per the CONTRIBUTING.md TDD Issue Test Tags convention.

All nox sessions pass: lint, format, typecheck, security_scan, dead_code,
unit_tests (508 features, 12985 scenarios, 0 failures), integration_tests,
docs, build, benchmark, coverage_report (97%).

ISSUES CLOSED: #1206

brent.edwards added the

Type

Task

label 2026-03-31 11:33:10 +00:00

brent.edwards added this to the v3.2.0 milestone 2026-03-31 11:33:10 +00:00

freemo approved these changes 2026-04-02 04:20:47 +00:00

Dismissed

freemo left a comment

Copy link

Review: APPROVED ✅

PR #1229 — fix(test): remove lingering @tdd_expected_fail tags for closed bugs #821 and #932

What was reviewed

• features/tdd_context_tier_runtime.feature — Updated feature description to reflect bug #821 is fixed
• features/steps/tdd_context_tier_runtime_steps.py — Updated module docstring to reflect fix status

Assessment

• Spec alignment: ✅ Correctly follows CONTRIBUTING.md TDD Issue Test Tags convention (@tdd_issue / @tdd_issue_<N> permanent tags retained)
• Code quality: ✅ Pure documentation cleanup — no functional code changes
• Test coverage: ✅ No test logic changed; descriptions now accurately reflect that tests serve as regression guards
• Risk: Very low — only feature descriptions and docstrings updated
• Quality gates: All 11 nox sessions pass (508 features, 12985 scenarios, 97% coverage)

Clean, minimal change. No concerns.

## Review: APPROVED ✅ **PR #1229 — fix(test): remove lingering @tdd_expected_fail tags for closed bugs #821 and #932** ### What was reviewed - `features/tdd_context_tier_runtime.feature` — Updated feature description to reflect bug #821 is fixed - `features/steps/tdd_context_tier_runtime_steps.py` — Updated module docstring to reflect fix status ### Assessment - **Spec alignment**: ✅ Correctly follows CONTRIBUTING.md TDD Issue Test Tags convention (`@tdd_issue` / `@tdd_issue_<N>` permanent tags retained) - **Code quality**: ✅ Pure documentation cleanup — no functional code changes - **Test coverage**: ✅ No test logic changed; descriptions now accurately reflect that tests serve as regression guards - **Risk**: Very low — only feature descriptions and docstrings updated - **Quality gates**: All 11 nox sessions pass (508 features, 12985 scenarios, 97% coverage) Clean, minimal change. No concerns.

freemo referenced this pull request 2026-04-02 04:21:48 +00:00

fix(test): remove lingering @tdd_expected_fail tags for closed bugs #821 and #932 #1206

freemo referenced this pull request 2026-04-02 04:25:14 +00:00

[Automated] Product Build Session State #1259

freemo self-assigned this 2026-04-02 06:15:12 +00:00

freemo commented 2026-04-02 08:03:07 +00:00

Owner

Copy link

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

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

freemo approved these changes 2026-04-02 08:06:08 +00:00

Dismissed

freemo left a comment

Copy link

Independent Review: APPROVED ✅

PR #1229 — fix(test): remove lingering @tdd_expected_fail tags for closed bugs #821 and #932

Review Summary

Verified that both bugs #821 (ACMS context tier runtime) and #932 (plan apply --yes flag) are closed on Forgejo. The @tdd_expected_fail tag was already absent from the actual Behave tag lines in both feature files — this PR correctly cleans up stale descriptive text that still referenced the tag and described the bugs as unfixed.

Files Reviewed

File	Change	Verdict
features/tdd_context_tier_runtime.feature	Feature description updated to reflect bug #821 is fixed; removed "will FAIL until the bug is fixed" and @tdd_expected_fail references	✅ Correct
features/steps/tdd_context_tier_runtime_steps.py	Module docstring updated to reflect fix status; removed stale "before the fix" language	✅ Correct
features/tdd_plan_apply_yes_flag.feature	No changes (confirmed identical SHA on master and branch)	✅ Correct — no stale references existed

Verification Checklist

• ✅ Spec alignment: Follows CONTRIBUTING.md TDD Issue Test Tags convention — permanent @tdd_issue / @tdd_issue_<N> tags retained, @tdd_expected_fail references removed from descriptions
• ✅ Tag integrity: @tdd_issue @tdd_issue_821 @mock_only and @tdd_issue @tdd_issue_932 remain on tag lines
• ✅ No functional changes: Only feature descriptions and docstrings updated — test logic untouched
• ✅ Commit format: Conventional Changelog format with ISSUES CLOSED: #1206
• ✅ PR metadata: Milestone v3.2.0, Type/Task label, Closes #1206 in body
• ✅ Quality gates: All nox sessions reported passing (508 features, 12985 scenarios, 97% coverage)
• ✅ No merge conflicts: PR is mergeable

Pre-existing Note (out of scope)

features/steps/tdd_context_tier_runtime_steps.py line 48 contains a pre-existing # type: ignore[arg-type] suppression that violates project rules. This was NOT introduced by this PR and should be tracked separately.

Clean, minimal, well-documented change. Approving for merge.

## Independent Review: APPROVED ✅ **PR #1229 — fix(test): remove lingering @tdd_expected_fail tags for closed bugs #821 and #932** ### Review Summary Verified that both bugs #821 (ACMS context tier runtime) and #932 (plan apply --yes flag) are **closed** on Forgejo. The `@tdd_expected_fail` tag was already absent from the actual Behave tag lines in both feature files — this PR correctly cleans up stale descriptive text that still referenced the tag and described the bugs as unfixed. ### Files Reviewed | File | Change | Verdict | |------|--------|---------| | `features/tdd_context_tier_runtime.feature` | Feature description updated to reflect bug #821 is fixed; removed "will FAIL until the bug is fixed" and `@tdd_expected_fail` references | ✅ Correct | | `features/steps/tdd_context_tier_runtime_steps.py` | Module docstring updated to reflect fix status; removed stale "before the fix" language | ✅ Correct | | `features/tdd_plan_apply_yes_flag.feature` | No changes (confirmed identical SHA on master and branch) | ✅ Correct — no stale references existed | ### Verification Checklist - ✅ **Spec alignment**: Follows CONTRIBUTING.md TDD Issue Test Tags convention — permanent `@tdd_issue` / `@tdd_issue_<N>` tags retained, `@tdd_expected_fail` references removed from descriptions - ✅ **Tag integrity**: `@tdd_issue @tdd_issue_821 @mock_only` and `@tdd_issue @tdd_issue_932` remain on tag lines - ✅ **No functional changes**: Only feature descriptions and docstrings updated — test logic untouched - ✅ **Commit format**: Conventional Changelog format with `ISSUES CLOSED: #1206` - ✅ **PR metadata**: Milestone v3.2.0, Type/Task label, `Closes #1206` in body - ✅ **Quality gates**: All nox sessions reported passing (508 features, 12985 scenarios, 97% coverage) - ✅ **No merge conflicts**: PR is mergeable ### Pre-existing Note (out of scope) `features/steps/tdd_context_tier_runtime_steps.py` line 48 contains a pre-existing `# type: ignore[arg-type]` suppression that violates project rules. This was NOT introduced by this PR and should be tracked separately. Clean, minimal, well-documented change. Approving for merge.

freemo referenced this pull request 2026-04-02 08:06:22 +00:00

fix(test): remove lingering @tdd_expected_fail tags for closed bugs #821 and #932 #1206

freemo commented 2026-04-02 16:48:01 +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 approved these changes 2026-04-02 16:51:03 +00:00

freemo left a comment

Copy link

Independent Review: APPROVED ✅

PR #1229 — fix(test): remove lingering @tdd_expected_fail tags for closed bugs #821 and #932

Review Methodology

Performed a full content comparison of all three files referenced in the PR across both master and the feature branch using the Forgejo file content API. Verified the linked issue (#1206) acceptance criteria against the actual changes.

Files Reviewed

File	Master SHA	Branch SHA	Change Summary
features/tdd_context_tier_runtime.feature	091bcc1f	3038defb	Feature description updated: removed "will FAIL until the bug is fixed" and @tdd_expected_fail references; added "The bug has been fixed" language and regression guard framing
features/steps/tdd_context_tier_runtime_steps.py	3c2bfb76	518532fc	Module docstring updated: removed "before the fix" / "will fail until the bug is fixed" / @tdd_expected_fail references; added "The bug has been fixed" regression guard language
features/tdd_plan_apply_yes_flag.feature	1ad55715	1ad55715	Identical — correctly no changes needed (no stale references existed)

Verification Checklist

• ✅ Spec alignment: Follows CONTRIBUTING.md TDD Issue Test Tags convention — permanent @tdd_issue / @tdd_issue_<N> tags retained on tag lines
• ✅ Tag integrity: @tdd_issue @tdd_issue_821 @mock_only and @tdd_issue @tdd_issue_932 remain on their respective tag lines, untouched
• ✅ No functional changes: Only feature descriptions and module docstrings updated — all test logic, step definitions, and assertions are identical
• ✅ Commit format: fix(test): remove lingering @tdd_expected_fail tags for closed bugs #821 and #932 — valid Conventional Changelog format
• ✅ Commit footer: ISSUES CLOSED: #1206 present
• ✅ PR metadata: Milestone v3.2.0 ✅, Type/Task label ✅, Closes #1206 in body ✅
• ✅ Single atomic commit: One commit, one logical change
• ✅ No merge conflicts: PR is mergeable
• ✅ Quality gates: All 11 nox sessions reported passing (508 features, 12985 scenarios, 97% coverage)
• ✅ No needs feedback label: Safe to merge

Pre-existing Note (out of scope)

features/steps/tdd_context_tier_runtime_steps.py line 48 contains a pre-existing # type: ignore[arg-type] suppression that violates project rules. This was not introduced by this PR and should be tracked as a separate issue.

Clean, minimal, well-documented change. Approving for merge.

## Independent Review: APPROVED ✅ **PR #1229 — fix(test): remove lingering @tdd_expected_fail tags for closed bugs #821 and #932** ### Review Methodology Performed a full content comparison of all three files referenced in the PR across both `master` and the feature branch using the Forgejo file content API. Verified the linked issue (#1206) acceptance criteria against the actual changes. ### Files Reviewed | File | Master SHA | Branch SHA | Change Summary | |------|-----------|------------|----------------| | `features/tdd_context_tier_runtime.feature` | `091bcc1f` | `3038defb` | Feature description updated: removed "will FAIL until the bug is fixed" and `@tdd_expected_fail` references; added "The bug has been fixed" language and regression guard framing | | `features/steps/tdd_context_tier_runtime_steps.py` | `3c2bfb76` | `518532fc` | Module docstring updated: removed "before the fix" / "will **fail** until the bug is fixed" / `@tdd_expected_fail` references; added "The bug has been fixed" regression guard language | | `features/tdd_plan_apply_yes_flag.feature` | `1ad55715` | `1ad55715` | **Identical** — correctly no changes needed (no stale references existed) | ### Verification Checklist - ✅ **Spec alignment**: Follows CONTRIBUTING.md TDD Issue Test Tags convention — permanent `@tdd_issue` / `@tdd_issue_<N>` tags retained on tag lines - ✅ **Tag integrity**: `@tdd_issue @tdd_issue_821 @mock_only` and `@tdd_issue @tdd_issue_932` remain on their respective tag lines, untouched - ✅ **No functional changes**: Only feature descriptions and module docstrings updated — all test logic, step definitions, and assertions are identical - ✅ **Commit format**: `fix(test): remove lingering @tdd_expected_fail tags for closed bugs #821 and #932` — valid Conventional Changelog format - ✅ **Commit footer**: `ISSUES CLOSED: #1206` present - ✅ **PR metadata**: Milestone v3.2.0 ✅, `Type/Task` label ✅, `Closes #1206` in body ✅ - ✅ **Single atomic commit**: One commit, one logical change - ✅ **No merge conflicts**: PR is mergeable - ✅ **Quality gates**: All 11 nox sessions reported passing (508 features, 12985 scenarios, 97% coverage) - ✅ **No `needs feedback` label**: Safe to merge ### Pre-existing Note (out of scope) `features/steps/tdd_context_tier_runtime_steps.py` line 48 contains a pre-existing `# type: ignore[arg-type]` suppression that violates project rules. This was **not introduced** by this PR and should be tracked as a separate issue. Clean, minimal, well-documented change. Approving for merge.

freemo merged commit f324575a3b into master 2026-04-02 16:51:15 +00:00

freemo deleted branch feature/m3-tdd-tag-cleanup-821-932 2026-04-02 16:51:16 +00:00

freemo referenced this pull request from a commit 2026-04-02 16:51:17 +00:00

fix(test): remove lingering @tdd_expected_fail tags for closed bugs #821 and #932 (#1229)

freemo referenced this pull request 2026-04-02 16:51:26 +00:00

fix(test): remove lingering @tdd_expected_fail tags for closed bugs #821 and #932 #1206

freemo referenced this pull request 2026-04-02 17:11:30 +00:00

[Automated] Product Build Session State #1314

freemo referenced this pull request 2026-04-02 17:34:52 +00:00

[Automated] Product Build Session State #1393

freemo referenced this pull request 2026-04-02 17:42:02 +00:00

[Automated] Product Build Session State #1393

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.2.0

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

freemo

2 participants

Notifications

Subscribe

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!1229

No description provided.