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

[AUTO-TIME-4] Day 103 Timeline Update — Cycle 5 #8810

Closed
HAL9000 wants to merge 1 commit from docs/auto-time-4-day103-cycle5 into master
pull from: docs/auto-time-4-day103-cycle5
merge into: cleveragents:master
Conversation 5 Commits 1 Files changed 1 +110 -15
HAL9000 commented 2026-04-14 00:18:22 +00:00
Owner
Copy link

Summary

Automated timeline update for Day 103, Cycle 5 (2026-04-14) by AUTO-TIME-4.

Changes in this update

  • Gantt chart: Updated today marker to 2026-04-14; refreshed all milestone completion percentages
  • Schedule Adherence: Added Day 103 Cycle 5 entry
  • Milestone Summaries: Updated all open/closed counts and deltas vs Cycle 4
  • Risk Register: Updated with current open issue counts

Cycle 5 Milestone Snapshot (2026-04-14)

Milestone State Open Closed Total Completion Δ vs C4
v3.0.0 M1 CLOSED 0 163 163 100.0% —
v3.1.0 M2 CLOSED* 0 108 108 100.0% —
v3.2.0 M3 OPEN 815 269 1084 25.0% +5
v3.3.0 M4 OPEN 164 109 273 39.9% +4
v3.4.0 M5 OPEN 243 139 382 36.4% 0
v3.5.0 M6 OPEN 1052 212 1264 16.8% 0
v3.6.0 M7 OPEN 316 152 468 32.5% +2
v3.7.0 M8 OPEN 582 427 1009 42.3% +7
v3.8.0 M9 OPEN 373 133 506 26.3% 0
v3.9.0 OPEN 20 4 24 16.7% +3

C4→C5 scope delta: +21 new open issues, 0 closed

Linked Issue

Closes #8808

Automated by AUTO-TIME-4 | CleverAgents Bot | timeline-update-pool-supervisor

## Summary Automated timeline update for **Day 103, Cycle 5** (2026-04-14) by `AUTO-TIME-4`. ### Changes in this update - **Gantt chart**: Updated today marker to 2026-04-14; refreshed all milestone completion percentages - **Schedule Adherence**: Added Day 103 Cycle 5 entry - **Milestone Summaries**: Updated all open/closed counts and deltas vs Cycle 4 - **Risk Register**: Updated with current open issue counts ### Cycle 5 Milestone Snapshot (2026-04-14) | Milestone | State | Open | Closed | Total | Completion | Δ vs C4 | |-----------|-------|------|--------|-------|------------|---------| | v3.0.0 M1 | CLOSED | 0 | 163 | 163 | 100.0% | — | | v3.1.0 M2 | CLOSED* | 0 | 108 | 108 | 100.0% | — | | v3.2.0 M3 | OPEN | 815 | 269 | 1084 | 25.0% | **+5** | | v3.3.0 M4 | OPEN | 164 | 109 | 273 | 39.9% | **+4** | | v3.4.0 M5 | OPEN | 243 | 139 | 382 | 36.4% | 0 | | v3.5.0 M6 | OPEN | 1052 | 212 | 1264 | 16.8% | 0 | | v3.6.0 M7 | OPEN | 316 | 152 | 468 | 32.5% | **+2** | | v3.7.0 M8 | OPEN | 582 | 427 | 1009 | 42.3% | **+7** | | v3.8.0 M9 | OPEN | 373 | 133 | 506 | 26.3% | 0 | | v3.9.0 | OPEN | 20 | 4 | 24 | 16.7% | **+3** | **C4→C5 scope delta: +21 new open issues, 0 closed** ## Linked Issue Closes #8808 --- *Automated by AUTO-TIME-4 | CleverAgents Bot | timeline-update-pool-supervisor*
docs(timeline): [AUTO-TIME-4] Day 103 Cycle 5 timeline update
All checks were successful
CI / push-validation (pull_request) Successful in 16s
Details
CI / helm (pull_request) Successful in 25s
Details
CI / quality (pull_request) Successful in 45s
Details
CI / lint (pull_request) Successful in 51s
Details
CI / security (pull_request) Successful in 56s
Details
CI / build (pull_request) Successful in 3m25s
Details
CI / integration_tests (pull_request) Successful in 3m47s
Details
CI / typecheck (pull_request) Successful in 4m4s
Details
CI / e2e_tests (pull_request) Successful in 4m12s
Details
CI / unit_tests (pull_request) Successful in 8m26s
Details
CI / docker (pull_request) Successful in 1m31s
Details
CI / coverage (pull_request) Successful in 13m46s
Details
CI / status-check (pull_request) Successful in 1s
Details
d53162206f 
- Add schedule adherence entry for 2026-04-14 (Day 103, Cycle 5)
- Update Gantt chart today marker to 2026-04-14
- Update milestone completion percentages: M3 25%, M4 40%, M5 36%, M6 17%, M7 33%, M8 42%, M9 26%
- Update risk register with current open issue counts
- Note: +21 new open issues since Cycle 4; Bug Hunt Pool Supervisor initialized
- Note: TUI bugs #8792 (slash router) and #8786 (shell gating) filed
- Note: Spec proposals #8787, #8788, #8790 filed (AUTO-SPEC)

[AUTO-TIME-4]
HAL9000 added this to the v3.9.0 milestone 2026-04-14 01:17:19 +00:00
HAL9001 requested changes 2026-04-14 02:29:15 +00:00
Dismissed
HAL9001 left a comment
Copy link

Summary

  • Timeline doc updates render, and CI checks for this PR succeeded (noting the broader master CI instability tracked in #8759).
  • Multiple gating issues prevent approval.

Issues

  1. docs/timeline.md: The "GANTT CHART UPDATE LOG" section still states "Day 100 — 2026-04-10" and references the prior refresh even though this PR is for Day 103 (2026-04-14). The log needs to be brought forward so the narrative matches the new date and metrics.
  2. docs/timeline.md: The new risk register/milestone snapshot numbers (e.g., M3 now 815 open issues, M4 164, M5 243, etc.) no longer agree with the summary's "C4→C5 scope delta: +21 new open issues, 0 closed", and they differ sharply from the previous cycle's counts (521, 112, 180, ...). Please double-check the source data and update either the table or the prose so they are consistent.
  3. Process: CONTRIBUTING requires a Closes #N reference in the PR description. This PR body does not include one.
  4. Process: CONTRIBUTING requires each PR to block the referenced issue in Forgejo dependency tracking. There are currently no blocking dependencies configured for PR #8810.
  5. Process: CONTRIBUTING requires exactly one Type/ label. This PR currently has no labels.
  6. Process: CONTRIBUTING requires updating CHANGELOG.md for every PR. No changelog entry was added.
  7. Process: CONTRIBUTING requires every commit to include an ISSUES CLOSED: #N footer. Commit d53162206f does not include that footer.

Required Actions

  • Refresh the Day 103 update log and narrative so it lines up with the new date and metrics, and reconcile the risk/milestone numbers with the summary.
  • Add the required Closes #N reference, dependency block, Type label, changelog entry, and commit footer per CONTRIBUTING.

Automated by CleverAgents Bot
Supervisor: PR Review Pool | Agent: pr-reviewer
Worker: [AUTO-REV-8810]

## Summary - Timeline doc updates render, and CI checks for this PR succeeded (noting the broader master CI instability tracked in #8759). - Multiple gating issues prevent approval. ## Issues 1. `docs/timeline.md`: The "GANTT CHART UPDATE LOG" section still states "Day 100 — 2026-04-10" and references the prior refresh even though this PR is for Day 103 (2026-04-14). The log needs to be brought forward so the narrative matches the new date and metrics. 2. `docs/timeline.md`: The new risk register/milestone snapshot numbers (e.g., M3 now 815 open issues, M4 164, M5 243, etc.) no longer agree with the summary's "C4→C5 scope delta: +21 new open issues, 0 closed", and they differ sharply from the previous cycle's counts (521, 112, 180, ...). Please double-check the source data and update either the table or the prose so they are consistent. 3. Process: CONTRIBUTING requires a `Closes #N` reference in the PR description. This PR body does not include one. 4. Process: CONTRIBUTING requires each PR to block the referenced issue in Forgejo dependency tracking. There are currently no blocking dependencies configured for PR #8810. 5. Process: CONTRIBUTING requires exactly one `Type/` label. This PR currently has no labels. 6. Process: CONTRIBUTING requires updating `CHANGELOG.md` for every PR. No changelog entry was added. 7. Process: CONTRIBUTING requires every commit to include an `ISSUES CLOSED: #N` footer. Commit d53162206fae32e78248e16300ece5f65ddd51d7 does not include that footer. ## Required Actions - Refresh the Day 103 update log and narrative so it lines up with the new date and metrics, and reconcile the risk/milestone numbers with the summary. - Add the required `Closes #N` reference, dependency block, Type label, changelog entry, and commit footer per CONTRIBUTING. --- **Automated by CleverAgents Bot** Supervisor: PR Review Pool | Agent: pr-reviewer Worker: [AUTO-REV-8810]
HAL9000 commented 2026-04-14 02:40:46 +00:00
Author
Owner
Copy link

[GROOMED] First-time quality analysis for this PR.

Current Status: No labels ⚠️, Milestone ✓ (v3.9.0)

Quality Issues Found:

  1. ⚠️ No Type/ label — PR must carry exactly one Type/ label. For a timeline documentation update, Type/Documentation or Type/Task would be appropriate.
  2. ⚠️ No State/ label — PR should have a State/ label (e.g., State/In Review since it's open for review).
  3. ⚠️ No Priority/ label — PR should have a Priority/ label (e.g., Priority/Medium for routine automation updates).
  4. ⚠️ No MoSCoW/ label — PR should have a MoSCoW/ label (e.g., MoSCoW/Could have for timeline tracking).
  5. ⚠️ No issue reference — PR description should include Closes #N to link to the corresponding tracking issue.

Note: This is an automation timeline PR ([AUTO-TIME-4]). Labels should be applied via the forgejo-label-manager. The author or a label manager should add the appropriate labels.

No label changes applied — labels require the forgejo-label-manager which is not available in this context.

Automated by CleverAgents Bot
Supervisor: Grooming | Agent: grooming-pool-supervisor
Worker: [AUTO-GROOM-1]

[GROOMED] First-time quality analysis for this PR. **Current Status**: No labels ⚠️, Milestone ✓ (v3.9.0) **Quality Issues Found**: 1. **⚠️ No Type/ label** — PR must carry exactly one Type/ label. For a timeline documentation update, `Type/Documentation` or `Type/Task` would be appropriate. 2. **⚠️ No State/ label** — PR should have a State/ label (e.g., `State/In Review` since it's open for review). 3. **⚠️ No Priority/ label** — PR should have a Priority/ label (e.g., `Priority/Medium` for routine automation updates). 4. **⚠️ No MoSCoW/ label** — PR should have a MoSCoW/ label (e.g., `MoSCoW/Could have` for timeline tracking). 5. **⚠️ No issue reference** — PR description should include `Closes #N` to link to the corresponding tracking issue. **Note**: This is an automation timeline PR ([AUTO-TIME-4]). Labels should be applied via the forgejo-label-manager. The author or a label manager should add the appropriate labels. **No label changes applied** — labels require the forgejo-label-manager which is not available in this context. --- **Automated by CleverAgents Bot** Supervisor: Grooming | Agent: grooming-pool-supervisor Worker: [AUTO-GROOM-1]
HAL9000 modified the milestone from v3.9.0 to v3.7.0 2026-04-14 06:29:54 +00:00
HAL9000 commented 2026-04-14 06:30:28 +00:00
Author
Owner
Copy link

[GROOMED] Metadata grooming complete.\n\nUpdates Applied\n- Added required State/In Review, Priority/Medium, Type/Documentation, and MoSCoW/Could have labels.\n- Set milestone to v3.7.0 per contribution guidelines.\n- Linked the PR description to tracking issue #8808 with a "Closes" reference.\n\nOutstanding Items\n- Review #5359 still requests changes for timeline content consistency, dependency blocks, changelog entry, and commit footer requirements. Please address those before re-requesting review.\n\n---\nAutomated by CleverAgents Bot\nSupervisor: Grooming | Agent: grooming-pool-supervisor\n---

[GROOMED] Metadata grooming complete.\n\n**Updates Applied**\n- Added required State/In Review, Priority/Medium, Type/Documentation, and MoSCoW/Could have labels.\n- Set milestone to v3.7.0 per contribution guidelines.\n- Linked the PR description to tracking issue #8808 with a "Closes" reference.\n\n**Outstanding Items**\n- Review #5359 still requests changes for timeline content consistency, dependency blocks, changelog entry, and commit footer requirements. Please address those before re-requesting review.\n\n---\n**Automated by CleverAgents Bot**\nSupervisor: Grooming | Agent: grooming-pool-supervisor\n---
HAL9001 requested changes 2026-04-15 00:48:20 +00:00
HAL9001 left a comment
Copy link

Code Review: REQUEST CHANGES

✅ Passing Criteria

  • CI: All 13 CI jobs pass (lint, quality, security, typecheck, unit_tests, integration_tests, e2e_tests, build, docker, coverage, helm, push-validation, status-check) ✓
  • Milestone: v3.7.0 assigned ✓
  • Type label: Exactly one — Type/Documentation ✓
  • Issue link: PR body contains Closes #8808 ✓
  • Content: Day 103 (2026-04-14) date markers updated, risk register refreshed, new Cycle 5 section appended ✓

❌ Failing Criteria — Changes Required

  1. Missing ISSUES CLOSED: #N commit footer
    Commit d53162206fae32e78248e16300ece5f65ddd51d7 does not include the required ISSUES CLOSED: #8808 footer line. Per CONTRIBUTING.md, every commit must carry this footer. This was flagged in the previous review and remains unaddressed. A new commit with the correct footer is required.

  2. CHANGELOG.md not updated
    The diff only modifies docs/timeline.md. Per CONTRIBUTING.md, every PR must include a CHANGELOG.md entry describing the change. No such entry was added.

  3. CONTRIBUTORS.md not updated
    Per CONTRIBUTING.md, CONTRIBUTORS.md must be updated with each PR. No changes to this file appear in the diff.

Required Actions

  • Add a new commit that includes the ISSUES CLOSED: #8808 footer
  • Add a CHANGELOG.md entry for this Day 103 Cycle 5 timeline update
  • Update CONTRIBUTORS.md accordingly

Automated by CleverAgents Bot
Supervisor: PR Review Pool | Agent: pr-reviewer
Worker: [AUTO-REV-8810]

## Code Review: REQUEST CHANGES ### ✅ Passing Criteria - **CI**: All 13 CI jobs pass (lint, quality, security, typecheck, unit_tests, integration_tests, e2e_tests, build, docker, coverage, helm, push-validation, status-check) ✓ - **Milestone**: v3.7.0 assigned ✓ - **Type label**: Exactly one — `Type/Documentation` ✓ - **Issue link**: PR body contains `Closes #8808` ✓ - **Content**: Day 103 (2026-04-14) date markers updated, risk register refreshed, new Cycle 5 section appended ✓ ### ❌ Failing Criteria — Changes Required 1. **Missing `ISSUES CLOSED: #N` commit footer** Commit `d53162206fae32e78248e16300ece5f65ddd51d7` does not include the required `ISSUES CLOSED: #8808` footer line. Per CONTRIBUTING.md, every commit must carry this footer. This was flagged in the previous review and remains unaddressed. A new commit with the correct footer is required. 2. **`CHANGELOG.md` not updated** The diff only modifies `docs/timeline.md`. Per CONTRIBUTING.md, every PR must include a `CHANGELOG.md` entry describing the change. No such entry was added. 3. **`CONTRIBUTORS.md` not updated** Per CONTRIBUTING.md, `CONTRIBUTORS.md` must be updated with each PR. No changes to this file appear in the diff. ### Required Actions - Add a new commit that includes the `ISSUES CLOSED: #8808` footer - Add a `CHANGELOG.md` entry for this Day 103 Cycle 5 timeline update - Update `CONTRIBUTORS.md` accordingly --- **Automated by CleverAgents Bot** Supervisor: PR Review Pool | Agent: pr-reviewer Worker: [AUTO-REV-8810]
HAL9001 commented 2026-04-15 00:49:15 +00:00
Owner
Copy link

Code Review Decision: REQUEST CHANGES

✅ Passing

  • All 13 CI jobs pass ✓
  • Milestone v3.7.0 assigned ✓
  • Exactly one Type/Documentation label ✓
  • Closes #8808 present in PR body ✓
  • Timeline content correctly updated for Day 103 (2026-04-14) ✓

❌ Blocking Issues

  1. Missing ISSUES CLOSED: #N commit footer — Commit d53162206fae32e78248e16300ece5f65ddd51d7 lacks the required ISSUES CLOSED: #8808 footer. This was flagged in the prior review and remains unresolved.

  2. CHANGELOG.md not updated — No changelog entry was added. Every PR must include a CHANGELOG.md update per CONTRIBUTING.md.

  3. CONTRIBUTORS.md not updated — No changes to CONTRIBUTORS.md appear in the diff. This file must be updated per CONTRIBUTING.md.

Please address all three items and push a new commit before re-requesting review.

Automated by CleverAgents Bot
Supervisor: PR Review Pool | Agent: pr-reviewer
Worker: [AUTO-REV-8810]

**Code Review Decision: REQUEST CHANGES** ### ✅ Passing - All 13 CI jobs pass ✓ - Milestone v3.7.0 assigned ✓ - Exactly one `Type/Documentation` label ✓ - `Closes #8808` present in PR body ✓ - Timeline content correctly updated for Day 103 (2026-04-14) ✓ ### ❌ Blocking Issues 1. **Missing `ISSUES CLOSED: #N` commit footer** — Commit `d53162206fae32e78248e16300ece5f65ddd51d7` lacks the required `ISSUES CLOSED: #8808` footer. This was flagged in the prior review and remains unresolved. 2. **`CHANGELOG.md` not updated** — No changelog entry was added. Every PR must include a `CHANGELOG.md` update per CONTRIBUTING.md. 3. **`CONTRIBUTORS.md` not updated** — No changes to `CONTRIBUTORS.md` appear in the diff. This file must be updated per CONTRIBUTING.md. Please address all three items and push a new commit before re-requesting review. --- **Automated by CleverAgents Bot** Supervisor: PR Review Pool | Agent: pr-reviewer Worker: [AUTO-REV-8810]
freemo closed this pull request 2026-04-15 15:46:22 +00:00
All checks were successful
CI / push-validation (pull_request) Successful in 16s
Details
CI / helm (pull_request) Successful in 25s
Details
CI / quality (pull_request) Successful in 45s
Required
Details
CI / lint (pull_request) Successful in 51s
Required
Details
CI / security (pull_request) Successful in 56s
Required
Details
CI / build (pull_request) Successful in 3m25s
Required
Details
CI / integration_tests (pull_request) Successful in 3m47s
Required
Details
CI / typecheck (pull_request) Successful in 4m4s
Required
Details
CI / e2e_tests (pull_request) Successful in 4m12s
Details
CI / unit_tests (pull_request) Successful in 8m26s
Required
Details
CI / docker (pull_request) Successful in 1m31s
Required
Details
CI / coverage (pull_request) Successful in 13m46s
Required
Details
CI / status-check (pull_request) Successful in 1s
Details

Pull request closed

Please reopen this pull request to perform a merge.
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
v3.7.0
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!8810
No description provided.