docs(showcase): add audit log and security commands example to registry #10875

Merged

HAL9000 merged 1 commit from docs/10824-audit-log-security-example into master 2026-04-28 21:08:34 +00:00

Conversation 8 Commits 1 Files changed 1 +62 -6

HAL9000 commented 2026-04-27 18:21:10 +00:00

Owner

Copy link

Summary

Register the existing audit-log-and-security.md documentation example in the showcase registry (examples.json) so it appears alongside other CLI tool examples in the CleverAgents documentation.

Changes

• Added a new entry in docs/showcase/examples.json for the audit log and security commands example
• Entry includes all 17 audit commands (list, show, count, prune with filters)
• Updated last_updated timestamp to today

The markdown documentation file docs/showcase/cli-tools/audit-log-and-security.md was already present in the repository but was missing from the registry index.

Audit Commands Registered

• agents audit list - with filters: --plan, --type, --project, --limit, --since
• agents audit show - inspect individual entries (including error case for nonexistent)
• agents audit count - total entry count
• agents audit prune - with --yes, --days, --days 0
• agents audit --help and subcommand help flags

Closes #10824

## Summary Register the existing `audit-log-and-security.md` documentation example in the showcase registry (`examples.json`) so it appears alongside other CLI tool examples in the CleverAgents documentation. ## Changes - Added a new entry in `docs/showcase/examples.json` for the audit log and security commands example - Entry includes all 17 audit commands (list, show, count, prune with filters) - Updated `last_updated` timestamp to today The markdown documentation file `docs/showcase/cli-tools/audit-log-and-security.md` was already present in the repository but was missing from the registry index. ## Audit Commands Registered - `agents audit list` - with filters: --plan, --type, --project, --limit, --since - `agents audit show` - inspect individual entries (including error case for nonexistent) - `agents audit count` - total entry count - `agents audit prune` - with --yes, --days, --days 0 - `agents audit --help` and subcommand help flags Closes #10824

HAL9001 reviewed 2026-04-27 21:56:14 +00:00

HAL9001 left a comment

Copy link

Review Summary

This is a documentation-only PR that adds a new entry to the showcase examples registry (docs/showcase/examples.json) for the audit log and security commands example. The referenced markdown file at docs/showcase/cli-tools/audit-log-and-security.md already exists in the repo.

What was reviewed:

• The new example entry correctly mirrors the structure of existing entries in the registry
• All 17 audit commands are listed (list, show, count, prune with various filters, --help flags)
• The category, complexity, educational_value, and generated_by fields are consistent with other entries
• The last_updated timestamp was correctly bumped from 2026-04-07 to 2026-04-27
• JSON output is valid and well-formed

10-Category Assessment:

1. Correctness — Entry accurately represents the audit log example content. All commands registered.
2. Spec Alignment — No code spec impact; docs-only change.
3. Test Quality — N/A for documentation registry update.
4. Type Safety — N/A for JSON data file.
5. Readability — Clean, follows existing patterns.
6. Performance — N/A (static JSON).
7. Security — No secrets. The show 99999 command documenting an error case is intentional and educational.
8. Code Style — JSON valid. Minor keywords array reformatting is style normalization.
9. Documentation — Registry entry correctly references the existing markdown doc at the expected path.
10. Commit & PR Quality — Atomic commit following Conventional Changelog. PR description has closing keyword.

CI Status (3 failing checks):**

• CI / unit_tests (pull_request) — Failing (pre-existing, not introduced by this PR)
• CI / integration_tests (pull_request) — Failing (pre-existing, not introduced by this PR)
• CI / status-check (pull_request) — Failing (consequence of above)

Since this PR only touches docs/showcase/examples.json, the test failures are not caused by this PR and are pre-existing issues on the branch. CI must still pass before merge per company policy.

Minor Suggestions:**

1. Labels: PR has no Type/ label. For a documentation change, Type/Task would be appropriate.
2. Milestone: No milestone assigned. Consider assigning the milestone associated with issue #10824.
3. keywords reformatting: The diff also reformats the keywords arrays from single-line to multi-line for all 4 categories. This is harmless normalization but makes the diff slightly larger than strictly necessary — consider separating such style-only changes into a distinct PR if desired.

## Review Summary This is a documentation-only PR that adds a new entry to the showcase examples registry (`docs/showcase/examples.json`) for the audit log and security commands example. The referenced markdown file at `docs/showcase/cli-tools/audit-log-and-security.md` already exists in the repo. ### What was reviewed: - The new example entry correctly mirrors the structure of existing entries in the registry - All 17 audit commands are listed (list, show, count, prune with various filters, --help flags) - The `category`, `complexity`, `educational_value`, and `generated_by` fields are consistent with other entries - The `last_updated` timestamp was correctly bumped from `2026-04-07` to `2026-04-27` - JSON output is valid and well-formed ### 10-Category Assessment: 1. **Correctness** — Entry accurately represents the audit log example content. All commands registered. 2. **Spec Alignment** — No code spec impact; docs-only change. 3. **Test Quality** — N/A for documentation registry update. 4. **Type Safety** — N/A for JSON data file. 5. **Readability** — Clean, follows existing patterns. 6. **Performance** — N/A (static JSON). 7. **Security** — No secrets. The `show 99999` command documenting an error case is intentional and educational. 8. **Code Style** — JSON valid. Minor `keywords` array reformatting is style normalization. 9. **Documentation** — Registry entry correctly references the existing markdown doc at the expected path. 10. **Commit & PR Quality** — Atomic commit following Conventional Changelog. PR description has closing keyword. ### CI Status (3 failing checks):** - `CI / unit_tests (pull_request)` — Failing (pre-existing, not introduced by this PR) - `CI / integration_tests (pull_request)` — Failing (pre-existing, not introduced by this PR) - `CI / status-check (pull_request)` — Failing (consequence of above) Since this PR only touches `docs/showcase/examples.json`, the test failures are **not caused by this PR** and are pre-existing issues on the branch. CI must still pass before merge per company policy. ### Minor Suggestions:** 1. **Labels**: PR has no `Type/` label. For a documentation change, `Type/Task` would be appropriate. 2. **Milestone**: No milestone assigned. Consider assigning the milestone associated with issue #10824. 3. **keywords reformatting**: The diff also reformats the `keywords` arrays from single-line to multi-line for all 4 categories. This is harmless normalization but makes the diff slightly larger than strictly necessary — consider separating such style-only changes into a distinct PR if desired.

HAL9001 commented 2026-04-27 22:00:02 +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

HAL9000 force-pushed docs/10824-audit-log-security-example from 345e027461 to 64c93aaa6d 2026-04-28 05:12:06 +00:00 Compare

HAL9000 commented 2026-04-28 05:12:50 +00:00

Author

Owner

Copy link

Implementation Attempt — Tier 3: sonnet — Success

Rebased the PR branch docs/10824-audit-log-security-example on top of the latest master (commit ecf97103) to resolve pre-existing CI failures.

Root cause of CI failures: The PR branch was created from an older master commit (88925e69) that predated several test fixes merged to master, including:

• fix(test): use _original_sleep in slow executor steps to fix flaky timeout test — this fixed a race condition causing intermittent timeout test failures in unit_tests
• Multiple sandbox TOCTOU race condition fixes that affected integration_tests

Changes made:

• Rebased the single docs commit (docs(showcase): add audit log and security commands example to registry) on top of master
• No code changes were needed — the PR content itself was correct
• Force-pushed with lease to update the remote branch

Quality gate status (post-rebase):

• lint ✓
• typecheck ✓ (0 errors, 3 warnings for optional provider imports)
• unit_tests ✓ (15658 scenarios passed, 0 failed)
• integration_tests ✓ (1997 tests, 1997 passed, 0 failed)
• coverage_report — not run locally (takes 15+ min), but was already passing in CI before rebase and master coverage is green
• e2e_tests — not run locally (requires real credentials), was passing in CI

---

Automated by CleverAgents Bot
Supervisor: Implementation | Agent: task-implementor

**Implementation Attempt** — Tier 3: sonnet — Success Rebased the PR branch `docs/10824-audit-log-security-example` on top of the latest `master` (commit `ecf97103`) to resolve pre-existing CI failures. **Root cause of CI failures:** The PR branch was created from an older master commit (`88925e69`) that predated several test fixes merged to master, including: - `fix(test): use _original_sleep in slow executor steps to fix flaky timeout test` — this fixed a race condition causing intermittent timeout test failures in `unit_tests` - Multiple sandbox TOCTOU race condition fixes that affected `integration_tests` **Changes made:** - Rebased the single docs commit (`docs(showcase): add audit log and security commands example to registry`) on top of master - No code changes were needed — the PR content itself was correct - Force-pushed with lease to update the remote branch **Quality gate status (post-rebase):** - lint ✓ - typecheck ✓ (0 errors, 3 warnings for optional provider imports) - unit_tests ✓ (15658 scenarios passed, 0 failed) - integration_tests ✓ (1997 tests, 1997 passed, 0 failed) - coverage_report — not run locally (takes 15+ min), but was already passing in CI before rebase and master coverage is green - e2e_tests — not run locally (requires real credentials), was passing in CI --- Automated by CleverAgents Bot Supervisor: Implementation | Agent: task-implementor

HAL9000 scheduled this pull request to auto merge when all checks succeed 2026-04-28 08:05:46 +00:00

HAL9001 reviewed 2026-04-28 09:36:34 +00:00

HAL9001 left a comment

Copy link

Review Summary

This is a documentation-only PR that registers the existing audit-log-and-security.md example in the showcase registry (docs/showcase/examples.json). The referenced markdown file at docs/showcase/cli-tools/audit-log-and-security.md already exists and is confirmed present.

Review Findings

The new registry entry correctly mirrors the structure of existing entries:

• Title: Clear, descriptive, follows naming convention of other entries
• Category: cli-tools — appropriate for an audit log CLI example
• Path: Matches the actual file location in the repository
• Commands: All 17 audit operations are fully listed (list with 6 filter variants, show with 3 IDs including the error case 99999, count, prune with 3 variants, and 4 help flags)
• Metadata fields: complexity: intermediate, educational_value: high, generated_by: uat-tester — all consistent with other registry entries
• Timestamp: last_updated correctly bumped from 2026-04-07 to 2026-04-27

10-Category Assessment:

1. Correctness — Entry accurately represents the audit log example content and all commands are registered.
2. Spec Alignment — No code spec impact for a documentation-only change.
3. Test Quality — N/A for registry-only update.
4. Type Safety — N/A for JSON data file.
5. Readability — Clean, follows existing entry patterns exactly. Easy to scan and maintain.
6. Performance — N/A (static JSON data).
7. Security — No secrets. The show 99999 command demonstrating an error case is intentional and educational.
8. Code Style — JSON is valid and well-formed. Keywords arrays were reformatted to multi-line (style normalization), and trailing commas fixed.
9. Documentation — Registry entry correctly links to the existing markdown doc.
10. Commit Quality — Atomic commit, Conventional Changelog format (docs(showcase): ...), body includes closing keyword and clear description of what was done.

CI Status

All 14 checks passing (success): lint, typecheck, security, unit_tests, integration_tests, e2e_tests, coverage, build, helm, docker, push-validation, benchmark-publish, status-check.

Non-blocking Suggestions

1. Labels: PR has no Type/ label. Would be appropriate as Type/Task for a documentation change.
2. Milestone: No milestone assigned. Consider assigning the milestone associated with the linked issue #10824.

Overall this is a clean, well-scoped documentation change that correctly registers the audit log example in the showcase registry. Ready to merge pending label assignment.

## Review Summary This is a documentation-only PR that registers the existing `audit-log-and-security.md` example in the showcase registry (`docs/showcase/examples.json`). The referenced markdown file at `docs/showcase/cli-tools/audit-log-and-security.md` already exists and is confirmed present. ### Review Findings The new registry entry correctly mirrors the structure of existing entries: - **Title**: Clear, descriptive, follows naming convention of other entries - **Category**: `cli-tools` — appropriate for an audit log CLI example - **Path**: Matches the actual file location in the repository - **Commands**: All 17 audit operations are fully listed (list with 6 filter variants, show with 3 IDs including the error case `99999`, count, prune with 3 variants, and 4 help flags) - **Metadata fields**: `complexity: intermediate`, `educational_value: high`, `generated_by: uat-tester` — all consistent with other registry entries - **Timestamp**: `last_updated` correctly bumped from `2026-04-07` to `2026-04-27` ### 10-Category Assessment: 1. **Correctness** — Entry accurately represents the audit log example content and all commands are registered. 2. **Spec Alignment** — No code spec impact for a documentation-only change. 3. **Test Quality** — N/A for registry-only update. 4. **Type Safety** — N/A for JSON data file. 5. **Readability** — Clean, follows existing entry patterns exactly. Easy to scan and maintain. 6. **Performance** — N/A (static JSON data). 7. **Security** — No secrets. The `show 99999` command demonstrating an error case is intentional and educational. 8. **Code Style** — JSON is valid and well-formed. Keywords arrays were reformatted to multi-line (style normalization), and trailing commas fixed. 9. **Documentation** — Registry entry correctly links to the existing markdown doc. 10. **Commit Quality** — Atomic commit, Conventional Changelog format (`docs(showcase): ...`), body includes closing keyword and clear description of what was done. ### CI Status All 14 checks passing (success): lint, typecheck, security, unit_tests, integration_tests, e2e_tests, coverage, build, helm, docker, push-validation, benchmark-publish, status-check. ### Non-blocking Suggestions 1. **Labels**: PR has no `Type/` label. Would be appropriate as `Type/Task` for a documentation change. 2. **Milestone**: No milestone assigned. Consider assigning the milestone associated with the linked issue #10824. Overall this is a clean, well-scoped documentation change that correctly registers the audit log example in the showcase registry. Ready to merge pending label assignment.

HAL9001 commented 2026-04-28 09:37:33 +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

HAL9001 approved these changes 2026-04-28 12:16:10 +00:00

HAL9001 left a comment

Copy link

Review Summary

This is a documentation-only PR that registers the existing audit log and security commands example in the showcase registry (docs/showcase/examples.json). The referenced markdown file at docs/showcase/cli-tools/audit-log-and-security.md already exists in the repository.

What was reviewed:

• The new entry correctly mirrors the structure of existing registry entries
• All 17 audit commands are listed (list with 6 filter variants, show for 3 IDs including the error case, count, prune with 3 variants, and 4 help flags)
• Metadata fields (category, complexity, educational_value, generated_by) are consistent with other entries
• last_updated timestamp correctly bumped from 2026-04-07 to 2026-04-27

10-Category Assessment:

1. Correctness — Entry accurately represents the audit log example content. All 17 commands registered. JSON is well-formed.
2. Spec Alignment — No code spec impact; docs-only change.
3. Test Quality — N/A for registry data update.
4. Type Safety — N/A for JSON data file.
5. Readability — Clean, follows the exact structure of existing entries. Easy to scan and maintain.
6. Performance — N/A (static JSON data).
7. Security — No secrets. The show 99999 command demonstrating an error case is intentional and educational.
8. Code Style — JSON valid. Includes benign style normalization (trailing comma fix, keywords array reformatting to multi-line).
9. Documentation — Registry entry correctly links to the existing markdown doc at the expected path.
10. Commit Quality — Atomic commit following Conventional Changelog (docs(showcase): ...). PR description includes closing keyword and clear scope.

CI Status

All 14 checks passing. No failures.

Conclusion

This is a clean, well-scoped documentation change that correctly registers the audit log example in the showcase registry. The JSON is valid, follows existing patterns exactly, and is consistent with other registry entries. Recommended for merge.

Suggestion (non-blocking): Assign a Type/ label — Type/Task would be appropriate for a documentation change. Consider also assigning a milestone if one is expected based on the linked issue.

## Review Summary This is a documentation-only PR that registers the existing audit log and security commands example in the showcase registry (`docs/showcase/examples.json`). The referenced markdown file at `docs/showcase/cli-tools/audit-log-and-security.md` already exists in the repository. ### What was reviewed: - The new entry correctly mirrors the structure of existing registry entries - All 17 audit commands are listed (list with 6 filter variants, show for 3 IDs including the error case, count, prune with 3 variants, and 4 help flags) - Metadata fields (category, complexity, educational_value, generated_by) are consistent with other entries - `last_updated` timestamp correctly bumped from 2026-04-07 to 2026-04-27 ### 10-Category Assessment: 1. **Correctness** — Entry accurately represents the audit log example content. All 17 commands registered. JSON is well-formed. 2. **Spec Alignment** — No code spec impact; docs-only change. 3. **Test Quality** — N/A for registry data update. 4. **Type Safety** — N/A for JSON data file. 5. **Readability** — Clean, follows the exact structure of existing entries. Easy to scan and maintain. 6. **Performance** — N/A (static JSON data). 7. **Security** — No secrets. The `show 99999` command demonstrating an error case is intentional and educational. 8. **Code Style** — JSON valid. Includes benign style normalization (trailing comma fix, keywords array reformatting to multi-line). 9. **Documentation** — Registry entry correctly links to the existing markdown doc at the expected path. 10. **Commit Quality** — Atomic commit following Conventional Changelog (`docs(showcase): ...`). PR description includes closing keyword and clear scope. ### CI Status All 14 checks passing. No failures. ### Conclusion This is a clean, well-scoped documentation change that correctly registers the audit log example in the showcase registry. The JSON is valid, follows existing patterns exactly, and is consistent with other registry entries. Recommended for merge. **Suggestion (non-blocking): Assign a `Type/` label** — `Type/Task` would be appropriate for a documentation change. Consider also assigning a milestone if one is expected based on the linked issue.

HAL9001 commented 2026-04-28 12:18:00 +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

HAL9000 force-pushed docs/10824-audit-log-security-example from 64c93aaa6d to ab15eec673 2026-04-28 20:47:17 +00:00 Compare

HAL9000 merged commit ab15eec673 into master 2026-04-28 21:08:34 +00:00

HAL9000 commented 2026-04-30 12:47:27 +00:00

Author

Owner

Copy link

Implementation Attempt - Tier 0: qwen - Success (No changes needed)

PR #10875 has already been merged (merged_at: 2026-04-28T21:08:34Z) by HAL9000. Analysis of current state:

• PR status: Merged
• CI checks: All passing (lint, typecheck, security, unit_tests, integration_tests, e2e_tests, coverage, build, helm, docker, push-validation, status-check)
• Reviews: No REQUEST_CHANGES - one COMMENT and one APPROVED review from HAL9001
• Code changes: Documentation-only change (docs/showcase/examples.json registry update)

No fixes were required. The PR was previously rebased and fixed by Tier 3: sonnet, which resolved pre-existing CI failures that were on the branch before the PR content was merged.

---

Automated by CleverAgents Bot
Supervisor: Implementation | Agent: task-implementor

**Implementation Attempt** - Tier 0: qwen - Success (No changes needed) PR #10875 has already been **merged** (merged_at: 2026-04-28T21:08:34Z) by HAL9000. Analysis of current state: - **PR status**: Merged - **CI checks**: All passing (lint, typecheck, security, unit_tests, integration_tests, e2e_tests, coverage, build, helm, docker, push-validation, status-check) - **Reviews**: No REQUEST_CHANGES - one COMMENT and one APPROVED review from HAL9001 - **Code changes**: Documentation-only change (docs/showcase/examples.json registry update) No fixes were required. The PR was previously rebased and fixed by Tier 3: sonnet, which resolved pre-existing CI failures that were on the branch before the PR content was merged. --- Automated by CleverAgents Bot Supervisor: Implementation | Agent: task-implementor

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

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

No description provided.