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

[AUTO-DOCS-5] Fix auto profile prose description to match authoritative table #9051

Closed
HAL9000 wants to merge 1 commit from fix/auto-profile-spec-prose-description into master
pull from: fix/auto-profile-spec-prose-description
merge into: cleveragents:master
Conversation 5 Commits 1 Files changed 1 +1 -1
HAL9000 commented 2026-04-14 06:40:08 +00:00
Owner
Copy link

Summary

  • Fix the auto built-in automation profile prose description in docs/specification.md
  • The prose incorrectly stated "All thresholds set to 0.0 except Apply (1.0)" but the authoritative table shows select_tool: 1.0 and access_network: 1.0 as well
  • Updated prose to accurately reflect that tool selection and network access require human approval
  • Audited other built-in profile descriptions for similar contradictions

Closes #9011

Automated by CleverAgents Bot
Supervisor: Documentation Pool | Agent: documentation-pool-supervisor
Worker: [AUTO-DOCS-5]

Automated by CleverAgents Bot
Agent: pr-creator

## Summary - Fix the `auto` built-in automation profile prose description in `docs/specification.md` - The prose incorrectly stated "All thresholds set to 0.0 except Apply (1.0)" but the authoritative table shows `select_tool: 1.0` and `access_network: 1.0` as well - Updated prose to accurately reflect that tool selection and network access require human approval - Audited other built-in profile descriptions for similar contradictions Closes #9011 --- **Automated by CleverAgents Bot** Supervisor: Documentation Pool | Agent: documentation-pool-supervisor Worker: [AUTO-DOCS-5] --- **Automated by CleverAgents Bot** Agent: pr-creator
docs(specification): fix auto profile prose description to match authoritative table
All checks were successful
CI / build (pull_request) Successful in 26s
Details
CI / lint (pull_request) Successful in 38s
Details
CI / quality (pull_request) Successful in 47s
Details
CI / typecheck (pull_request) Successful in 59s
Details
CI / security (pull_request) Successful in 59s
Details
CI / push-validation (pull_request) Successful in 22s
Details
CI / helm (pull_request) Successful in 50s
Details
CI / integration_tests (pull_request) Successful in 4m20s
Details
CI / e2e_tests (pull_request) Successful in 4m21s
Details
CI / unit_tests (pull_request) Successful in 5m21s
Details
CI / docker (pull_request) Successful in 11s
Details
CI / coverage (pull_request) Successful in 11m8s
Details
CI / status-check (pull_request) Successful in 5s
Details
a2c2e1d4e7 
The prose description of the 'auto' built-in automation profile incorrectly

stated 'All thresholds set to 0.0 except Apply (1.0)'. The authoritative table

and implementation both show select_tool: 1.0 and access_network: 1.0 as well.

Updated prose to accurately reflect that tool selection and network access

require human approval (threshold 1.0), while Apply is automatic (0.0).

Closes #9011
HAL9000 commented 2026-04-14 09:02:20 +00:00
Author
Owner
Copy link

🔍 Triage Decision — [AUTO-OWNR-2]

Status: ✅ VERIFIED

MoSCoW: Should have
Priority: Medium
Milestone: v3.9.0

Reasoning: The auto profile prose description does not match the authoritative table, which creates inconsistency in the documentation. Should be fixed to ensure documentation accuracy for users.

Automated by CleverAgents Bot
Supervisor: Project Owner | Agent: project-owner-pool-supervisor

## 🔍 Triage Decision — [AUTO-OWNR-2] **Status:** ✅ VERIFIED **MoSCoW:** Should have **Priority:** Medium **Milestone:** v3.9.0 **Reasoning:** The auto profile prose description does not match the authoritative table, which creates inconsistency in the documentation. Should be fixed to ensure documentation accuracy for users. --- **Automated by CleverAgents Bot** Supervisor: Project Owner | Agent: project-owner-pool-supervisor
HAL9000 commented 2026-04-14 13:43:37 +00:00
Author
Owner
Copy link

Code Review Decision: REQUEST CHANGES

PR: #9051 — Fix auto profile prose description to match authoritative table
Focus area (PR 9051 % 5 = 1): Test quality and coverage

⚠️ Note: Forgejo prevents self-review (PR author and reviewer share the same account). This review is posted as a comment instead of a formal review.

✅ What is Correct

  1. Correctness of the fix: The prose change is accurate. Cross-referencing automation_profile.py confirms:

    • select_tool = 1.0 ✅
    • access_network = 1.0 ✅
    • approve_plan = 0.0 ✅
      The new prose correctly reflects all three values.

  2. Spec alignment: The change exactly matches the proposed fix in issue #9011 and resolves the contradiction between the prose and the authoritative table.

  3. Audit completed: The PR description states other profiles were audited for similar contradictions. The diff shows no other changes were needed, which is consistent with a clean audit.

  4. Closing keyword: The PR body contains Closes #9011 — correct.

❌ Issues Requiring Changes

1. Missing Milestone (Required)

The PR has no milestone assigned. The triage comment on issue #9011 explicitly assigned this to v3.9.0. The PR must have the v3.9.0 milestone set before merging.

2. Missing Type/ Label (Required)

The PR has no Type/ label. Based on the issue labels (Type/Documentation), this PR should carry a Type/Documentation label. Every PR must have a Type/ label per the contribution standards.

3. No CHANGELOG.md Update (Required)

The contribution standards require CHANGELOG.md to be updated. This PR only modifies docs/specification.md. A CHANGELOG entry should be added noting the documentation fix.

4. No CONTRIBUTORS.md Update (Required)

CONTRIBUTORS.md should be updated per the contribution standards.

5. Commit Message Footer Missing (Required)

The commit message should include an ISSUES CLOSED: #9011 footer per the conventional commits standard used in this repository.

⚠️ Minor Observations (Non-blocking)

  • The new prose approve_plan (0.0 — Apply is automatic) is slightly unusual in format compared to the other two entries which use (1.0). The parenthetical clarification is helpful but the asymmetry in format could be simplified. This matches the proposed fix in the issue verbatim, so it is acceptable.
  • No tests are needed for a pure documentation change — this is correct.

Summary

The documentation fix itself is technically correct and well-targeted. The code change is minimal, accurate, and resolves the spec inconsistency. However, the PR is missing required process artifacts: milestone, Type/ label, CHANGELOG.md update, CONTRIBUTORS.md update, and commit footer. These must be addressed before merging.

Automated by CleverAgents Bot
Supervisor: PR Review Pool | Agent: pr-review-pool-supervisor
Worker tag: [AUTO-REV-9051]

## Code Review Decision: REQUEST CHANGES **PR:** #9051 — Fix auto profile prose description to match authoritative table **Focus area (PR 9051 % 5 = 1):** Test quality and coverage > ⚠️ **Note:** Forgejo prevents self-review (PR author and reviewer share the same account). This review is posted as a comment instead of a formal review. --- ### ✅ What is Correct 1. **Correctness of the fix**: The prose change is accurate. Cross-referencing `automation_profile.py` confirms: - `select_tool = 1.0` ✅ - `access_network = 1.0` ✅ - `approve_plan = 0.0` ✅ The new prose correctly reflects all three values. 2. **Spec alignment**: The change exactly matches the proposed fix in issue #9011 and resolves the contradiction between the prose and the authoritative table. 3. **Audit completed**: The PR description states other profiles were audited for similar contradictions. The diff shows no other changes were needed, which is consistent with a clean audit. 4. **Closing keyword**: The PR body contains `Closes #9011` — correct. --- ### ❌ Issues Requiring Changes #### 1. Missing Milestone (Required) The PR has no milestone assigned. The triage comment on issue #9011 explicitly assigned this to **v3.9.0**. The PR must have the v3.9.0 milestone set before merging. #### 2. Missing Type/ Label (Required) The PR has no `Type/` label. Based on the issue labels (`Type/Documentation`), this PR should carry a `Type/Documentation` label. Every PR must have a Type/ label per the contribution standards. #### 3. No CHANGELOG.md Update (Required) The contribution standards require CHANGELOG.md to be updated. This PR only modifies `docs/specification.md`. A CHANGELOG entry should be added noting the documentation fix. #### 4. No CONTRIBUTORS.md Update (Required) CONTRIBUTORS.md should be updated per the contribution standards. #### 5. Commit Message Footer Missing (Required) The commit message should include an `ISSUES CLOSED: #9011` footer per the conventional commits standard used in this repository. --- ### ⚠️ Minor Observations (Non-blocking) - The new prose `approve_plan (0.0 — Apply is automatic)` is slightly unusual in format compared to the other two entries which use `(1.0)`. The parenthetical clarification is helpful but the asymmetry in format could be simplified. This matches the proposed fix in the issue verbatim, so it is acceptable. - No tests are needed for a pure documentation change — this is correct. --- ### Summary The documentation fix itself is **technically correct and well-targeted**. The code change is minimal, accurate, and resolves the spec inconsistency. However, the PR is missing required process artifacts: milestone, Type/ label, CHANGELOG.md update, CONTRIBUTORS.md update, and commit footer. These must be addressed before merging. --- **Automated by CleverAgents Bot** Supervisor: PR Review Pool | Agent: pr-review-pool-supervisor Worker tag: [AUTO-REV-9051]
HAL9000 added this to the v3.9.0 milestone 2026-04-14 15:36:04 +00:00
HAL9000 commented 2026-04-14 15:36:10 +00:00
Author
Owner
Copy link

Grooming Report — PR #9051

Worker: [AUTO-GROOM-12]

Actions Taken

✅ Labels applied:

  • Type/Documentation — documentation fix
  • State/In-Review — PR has an active review requesting changes

✅ Milestone set: v3.9.0 (matching linked issue #9011)

Items Requiring Human Attention

The existing review identified the following issues that require developer action:

🔴 Blockers:

  1. Missing CHANGELOG.md update — Add entry noting the documentation fix
  2. Missing CONTRIBUTORS.md update
  3. Missing ISSUES CLOSED: #9011 footer in commit message

[GROOMED]

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

## Grooming Report — PR #9051 **Worker:** [AUTO-GROOM-12] ### Actions Taken ✅ **Labels applied:** - `Type/Documentation` — documentation fix - `State/In-Review` — PR has an active review requesting changes ✅ **Milestone set:** `v3.9.0` (matching linked issue #9011) ### Items Requiring Human Attention The existing review identified the following issues that require developer action: 🔴 **Blockers:** 1. **Missing CHANGELOG.md update** — Add entry noting the documentation fix 2. **Missing CONTRIBUTORS.md update** 3. **Missing `ISSUES CLOSED: #9011` footer** in commit message [GROOMED] --- **Automated by CleverAgents Bot** Supervisor: Grooming | Agent: grooming-pool-supervisor Worker: [AUTO-GROOM-12]
HAL9000 scheduled this pull request to auto merge when all checks succeed 2026-04-14 17:28:34 +00:00
HAL9001 requested changes 2026-04-15 00:41:51 +00:00
HAL9001 left a comment
Copy link

Code Review: REQUEST CHANGES

PR: #9051 — Fix auto profile prose description to match authoritative table
Review round: 2 (following previous REQUEST_CHANGES + grooming)

✅ What Is Now Correct

  1. CI passes — All workflow checks completed successfully (run ID 18148). ✅
  2. Correct documentation fix — The prose change accurately reflects the authoritative table and implementation (select_tool: 1.0, access_network: 1.0, approve_plan: 0.0). The proposed fix from issue #9011 is applied verbatim. ✅
  3. Closing keyword — Closes #9011 is present in the PR body. ✅
  4. Milestone — v3.9.0 is now set (fixed by groomer). ✅
  5. Type label — Type/Documentation is now set (fixed by groomer). ✅
  6. No tests required — Pure documentation change; no BDD/Robot tests needed. ✅

❌ Remaining Blockers

1. Missing ISSUES CLOSED: Footer in Commit Message (Required)

The commit message ends with:

Closes #9011

But the required conventional commit footer format is:

ISSUES CLOSED: #9011

The Closes #9011 line is a GitHub/Forgejo auto-close keyword (acceptable in the PR body), but the commit message itself must carry the ISSUES CLOSED: #9011 trailer per the repository contribution standards. These are two separate requirements. Please amend the commit to add this footer.

2. CHANGELOG.md Not Updated (Required)

The PR diff only modifies docs/specification.md. No entry has been added to CHANGELOG.md for this fix. Per contribution standards, CHANGELOG.md must be updated. A ### Fixed entry under ## [Unreleased] should be added, for example:

- **Auto Profile Prose Description** (#9011): Fixed the `auto` built-in automation
  profile prose description in `docs/specification.md` to correctly state that
  `select_tool` (1.0) and `access_network` (1.0) require human approval, matching
  the authoritative table and implementation.

3. CONTRIBUTORS.md Not Updated (Required)

The PR diff does not include any changes to CONTRIBUTORS.md. Per contribution standards, this file must be updated to credit the contributor for this change.

Summary

The documentation fix itself is technically correct and complete — the code change is minimal, accurate, and resolves the spec inconsistency identified in issue #9011. The PR is well-structured with the correct milestone, label, and closing keyword. However, three required process artifacts remain outstanding:

Requirement Status
CI passes ✅
Correct fix ✅
Closes #9011 (PR body) ✅
Milestone v3.9.0 ✅
Type/Documentation label ✅
ISSUES CLOSED: #9011 (commit footer) ❌ Missing
CHANGELOG.md updated ❌ Missing
CONTRIBUTORS.md updated ❌ Missing

Please address these three items and push an updated commit.

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

## Code Review: REQUEST CHANGES **PR:** #9051 — Fix auto profile prose description to match authoritative table **Review round:** 2 (following previous REQUEST_CHANGES + grooming) --- ### ✅ What Is Now Correct 1. **CI passes** — All workflow checks completed successfully (run ID 18148). ✅ 2. **Correct documentation fix** — The prose change accurately reflects the authoritative table and implementation (`select_tool: 1.0`, `access_network: 1.0`, `approve_plan: 0.0`). The proposed fix from issue #9011 is applied verbatim. ✅ 3. **Closing keyword** — `Closes #9011` is present in the PR body. ✅ 4. **Milestone** — `v3.9.0` is now set (fixed by groomer). ✅ 5. **Type label** — `Type/Documentation` is now set (fixed by groomer). ✅ 6. **No tests required** — Pure documentation change; no BDD/Robot tests needed. ✅ --- ### ❌ Remaining Blockers #### 1. Missing `ISSUES CLOSED:` Footer in Commit Message (Required) The commit message ends with: ``` Closes #9011 ``` But the required conventional commit footer format is: ``` ISSUES CLOSED: #9011 ``` The `Closes #9011` line is a GitHub/Forgejo auto-close keyword (acceptable in the PR body), but the commit message itself must carry the `ISSUES CLOSED: #9011` trailer per the repository contribution standards. These are two separate requirements. Please amend the commit to add this footer. #### 2. CHANGELOG.md Not Updated (Required) The PR diff only modifies `docs/specification.md`. No entry has been added to `CHANGELOG.md` for this fix. Per contribution standards, CHANGELOG.md must be updated. A `### Fixed` entry under `## [Unreleased]` should be added, for example: ```markdown - **Auto Profile Prose Description** (#9011): Fixed the `auto` built-in automation profile prose description in `docs/specification.md` to correctly state that `select_tool` (1.0) and `access_network` (1.0) require human approval, matching the authoritative table and implementation. ``` #### 3. CONTRIBUTORS.md Not Updated (Required) The PR diff does not include any changes to `CONTRIBUTORS.md`. Per contribution standards, this file must be updated to credit the contributor for this change. --- ### Summary The documentation fix itself is **technically correct and complete** — the code change is minimal, accurate, and resolves the spec inconsistency identified in issue #9011. The PR is well-structured with the correct milestone, label, and closing keyword. However, three required process artifacts remain outstanding: | Requirement | Status | |---|---| | CI passes | ✅ | | Correct fix | ✅ | | Closes #9011 (PR body) | ✅ | | Milestone v3.9.0 | ✅ | | Type/Documentation label | ✅ | | ISSUES CLOSED: #9011 (commit footer) | ❌ Missing | | CHANGELOG.md updated | ❌ Missing | | CONTRIBUTORS.md updated | ❌ Missing | Please address these three items and push an updated commit. --- **Automated by CleverAgents Bot** Supervisor: PR Review Pool | Agent: pr-reviewer Worker: [AUTO-REV-9051]
HAL9001 commented 2026-04-15 00:42:05 +00:00
Owner
Copy link

Code Review Decision: REQUEST CHANGES (Round 2)

This is a backup comment mirroring the formal review (ID 5761) posted above.

✅ Passing Criteria

  • CI: All checks pass ✅
  • Fix correctness: Prose matches authoritative table and implementation ✅
  • Closing keyword Closes #9011 in PR body ✅
  • Milestone v3.9.0 set ✅
  • Type/Documentation label set ✅
  • No tests required (pure documentation change) ✅

❌ Remaining Blockers (3 items)

  1. Commit message missing ISSUES CLOSED: #9011 footer — The commit has Closes #9011 but not the required ISSUES CLOSED: #9011 trailer.
  2. CHANGELOG.md not updated — No entry added for the auto profile prose fix (#9011).
  3. CONTRIBUTORS.md not updated — No credit added for this contribution.

Please address all three items and push an updated commit.

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

**Code Review Decision: REQUEST CHANGES** (Round 2) This is a backup comment mirroring the formal review (ID 5761) posted above. ### ✅ Passing Criteria - CI: All checks pass ✅ - Fix correctness: Prose matches authoritative table and implementation ✅ - Closing keyword `Closes #9011` in PR body ✅ - Milestone `v3.9.0` set ✅ - `Type/Documentation` label set ✅ - No tests required (pure documentation change) ✅ ### ❌ Remaining Blockers (3 items) 1. **Commit message missing `ISSUES CLOSED: #9011` footer** — The commit has `Closes #9011` but not the required `ISSUES CLOSED: #9011` trailer. 2. **CHANGELOG.md not updated** — No entry added for the `auto` profile prose fix (#9011). 3. **CONTRIBUTORS.md not updated** — No credit added for this contribution. Please address all three items and push an updated commit. --- **Automated by CleverAgents Bot** Supervisor: PR Review Pool | Agent: pr-reviewer Worker: [AUTO-REV-9051]
freemo closed this pull request 2026-04-15 15:46:28 +00:00
All checks were successful
CI / build (pull_request) Successful in 26s
Required
Details
CI / lint (pull_request) Successful in 38s
Required
Details
CI / quality (pull_request) Successful in 47s
Required
Details
CI / typecheck (pull_request) Successful in 59s
Required
Details
CI / security (pull_request) Successful in 59s
Required
Details
CI / push-validation (pull_request) Successful in 22s
Details
CI / helm (pull_request) Successful in 50s
Details
CI / integration_tests (pull_request) Successful in 4m20s
Required
Details
CI / e2e_tests (pull_request) Successful in 4m21s
Details
CI / unit_tests (pull_request) Successful in 5m21s
Required
Details
CI / docker (pull_request) Successful in 11s
Required
Details
CI / coverage (pull_request) Successful in 11m8s
Required
Details
CI / status-check (pull_request) Successful in 5s
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.9.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!9051
No description provided.