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

fix(session): correct field names and data types in Session.as_cli_dict() for spec compliance #3461

Merged
freemo merged 1 commit from bugfix/session-show-as-cli-dict-field-names into master 2026-04-05 18:19:20 +00:00
Conversation 1 Commits 1 Files changed 5 +216 -41
freemo commented 2026-04-05 17:56:28 +00:00
Owner
Copy link

Summary

Fixes issue #3440: agents session show JSON output uses wrong field names and wrong data types for recent_messages and linked_plans.

Problem

Session.as_cli_dict() returned incorrect field names and data structures throughout, breaking spec compliance for the agents session show JSON output:

# Current key / value Spec-required key / value
1 session_id id (inside session_summary)
2 actor_name actor (inside session_summary)
3 message_count messages (inside session_summary)
4 created_at created (inside session_summary)
5 updated_at updated (inside session_summary)
6 namespace (present) not in spec's session_summary
7 (missing) automation field in session_summary
8 recent_messages[].content recent_messages[].text
9 linked_plan_ids (flat list[str]) linked_plans (list of {plan_id, phase, state} objects)
10 estimated_cost as float estimated_cost as formatted string e.g. "$0.0184"

Solution

Architectural decision: Added LinkedPlan value object to the Session domain model to store plan phase and state alongside the plan ID. This is the cleanest approach — the domain model owns its data.

Changes:

  • session.py: Added LinkedPlan value object with plan_id, phase, state fields; added automation field to Session; rewrote as_cli_dict() to produce spec-compliant output with session_summary wrapper, correct field names, text key in recent_messages, linked_plans as objects, and estimated_cost as formatted string
  • session.py (CLI): Updated rich output to use spec-compliant labels (ID:, Automation:) and render linked_plans as a table with Plan ID / Phase / State columns
  • __init__.py: Export LinkedPlan from domain models core
  • consolidated_domain_models.feature: Updated tests to assert new spec-compliant field names; added new scenarios for automation, linked_plans, and estimated_cost format
  • session_model_steps.py: Added step definitions for new assertions

Quality Gates

  • ✅ nox -s lint — passes
  • ✅ nox -s typecheck — 0 errors, 0 warnings
  • ✅ Manual Python unit tests — all assertions pass
  • ⚠️ nox -s unit_tests — behave-parallel hangs in local environment (pre-existing infrastructure issue, not caused by this change — verified by testing without changes)

Closes #3440

Automated by CleverAgents Bot
Supervisor: Implementation | Agent: ca-issue-worker

## Summary Fixes issue #3440: `agents session show` JSON output uses wrong field names and wrong data types for `recent_messages` and `linked_plans`. ### Problem `Session.as_cli_dict()` returned incorrect field names and data structures throughout, breaking spec compliance for the `agents session show` JSON output: | # | Current key / value | Spec-required key / value | |---|---|---| | 1 | `session_id` | `id` (inside `session_summary`) | | 2 | `actor_name` | `actor` (inside `session_summary`) | | 3 | `message_count` | `messages` (inside `session_summary`) | | 4 | `created_at` | `created` (inside `session_summary`) | | 5 | `updated_at` | `updated` (inside `session_summary`) | | 6 | `namespace` (present) | not in spec's `session_summary` | | 7 | *(missing)* | `automation` field in `session_summary` | | 8 | `recent_messages[].content` | `recent_messages[].text` | | 9 | `linked_plan_ids` (flat `list[str]`) | `linked_plans` (list of `{plan_id, phase, state}` objects) | | 10 | `estimated_cost` as `float` | `estimated_cost` as formatted string e.g. `"$0.0184"` | ### Solution **Architectural decision**: Added `LinkedPlan` value object to the Session domain model to store plan phase and state alongside the plan ID. This is the cleanest approach — the domain model owns its data. **Changes:** - **`session.py`**: Added `LinkedPlan` value object with `plan_id`, `phase`, `state` fields; added `automation` field to `Session`; rewrote `as_cli_dict()` to produce spec-compliant output with `session_summary` wrapper, correct field names, `text` key in `recent_messages`, `linked_plans` as objects, and `estimated_cost` as formatted string - **`session.py` (CLI)**: Updated rich output to use spec-compliant labels (`ID:`, `Automation:`) and render `linked_plans` as a table with Plan ID / Phase / State columns - **`__init__.py`**: Export `LinkedPlan` from domain models core - **`consolidated_domain_models.feature`**: Updated tests to assert new spec-compliant field names; added new scenarios for `automation`, `linked_plans`, and `estimated_cost` format - **`session_model_steps.py`**: Added step definitions for new assertions ### Quality Gates - ✅ `nox -s lint` — passes - ✅ `nox -s typecheck` — 0 errors, 0 warnings - ✅ Manual Python unit tests — all assertions pass - ⚠️ `nox -s unit_tests` — behave-parallel hangs in local environment (pre-existing infrastructure issue, not caused by this change — verified by testing without changes) Closes #3440 --- **Automated by CleverAgents Bot** Supervisor: Implementation | Agent: ca-issue-worker
fix(session): correct field names and data types in Session.as_cli_dict() for spec compliance
Some checks failed
CI / lint (pull_request) Successful in 32s
Details
CI / quality (pull_request) Successful in 34s
Details
CI / typecheck (pull_request) Successful in 54s
Details
CI / security (pull_request) Successful in 1m7s
Details
CI / build (pull_request) Successful in 28s
Details
CI / helm (pull_request) Successful in 23s
Details
CI / unit_tests (pull_request) Successful in 6m47s
Details
CI / e2e_tests (pull_request) Successful in 17m15s
Details
CI / integration_tests (pull_request) Failing after 22m54s
Details
CI / docker (pull_request) Successful in 1m22s
Details
CI / coverage (pull_request) Successful in 11m0s
Details
CI / status-check (pull_request) Failing after 2s
Details
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / benchmark-regression (pull_request) Successful in 57m15s
Details
c1ab8c86b3 
Fixes issue #3440: agents session show JSON output uses wrong field names
and wrong data types for recent_messages and linked_plans.

Changes:
- Add LinkedPlan value object to session domain model with plan_id, phase,
  state fields for spec-compliant linked_plans output
- Add automation field to Session domain model for automation profile name
- Rewrite as_cli_dict() to produce spec-compliant output:
  - Wrap session fields in session_summary sub-dict
  - Rename session_id -> id, actor_name -> actor, message_count -> messages,
    created_at -> created, updated_at -> updated
  - Remove namespace from session_summary (not in spec)
  - Add automation field to session_summary
  - Use 'text' key (not 'content') in recent_messages items
  - Replace linked_plan_ids (flat list) with linked_plans (list of objects
    with plan_id, phase, state)
  - Format estimated_cost as string (e.g. '$0.0184') not raw float
- Update session show rich output to use spec-compliant labels and
  render linked_plans as a table with Plan ID / Phase / State columns
- Update consolidated_domain_models.feature tests to assert new field names
- Add new Behave step definitions for spec-compliant field assertions
- Export LinkedPlan from domain models core __init__.py

ISSUES CLOSED: #3440
freemo reviewed 2026-04-05 17:59:54 +00:00
freemo left a comment
Copy link

PR #3461 Review — fix(session): correct field names and data types in Session.as_cli_dict() for spec compliance

Review Focus: specification-compliance, behavior-correctness, api-consistency
Linked Issue: #3440 (UAT: agents session show JSON output uses wrong field names)

✅ What Looks Good

  1. Specification Compliance: The rewritten as_cli_dict() correctly produces the spec-required structure with session_summary wrapper, renamed fields (id, actor, messages, created, updated), automation field, text key in recent_messages, linked_plans as objects, and estimated_cost as formatted string. This directly addresses all 9 violations listed in #3440.

  2. Architectural Decision: Adding LinkedPlan as a value object in the domain model is the right approach — it keeps the domain model as the owner of its data rather than requiring service-layer lookups at display time.

  3. Commit Message: ✅ Follows Conventional Changelog format exactly as specified in the issue metadata.

  4. ISSUES CLOSED Footer: ✅ Present (ISSUES CLOSED: #3440).

  5. PR Description: ✅ Thorough, well-structured, includes Closes #3440.

  6. No Forbidden Patterns: ✅ No # type: ignore, imports at top of file, proper type annotations throughout.

  7. LinkedPlan Model: Clean Pydantic BaseModel with proper Field descriptors, str_strip_whitespace, and validate_assignment.

  8. __init__.py Export: LinkedPlan correctly added to both the import block and __all__ list, maintaining alphabetical ordering.

⚠️ Issues Requiring Attention

1. [API-CONSISTENCY] Dual Representation Creates Consistency Risk — linked_plan_ids vs linked_plans

  • Location: src/cleveragents/domain/models/core/session.py — Session model fields
  • Issue: The Session model now has both linked_plan_ids: list[str] and linked_plans: list[LinkedPlan]. The existing link_plan() method (which is the primary API for linking plans) only appends to linked_plan_ids — it does not create a corresponding LinkedPlan entry. This means after calling link_plan("some-ulid"), the as_cli_dict() method will fall through to the fallback path and emit {"plan_id": "some-ulid", "phase": "", "state": ""} with empty strings.
  • Risk: Any code path that uses link_plan() (the existing API) will produce degraded output. The two lists can drift out of sync with no validation preventing it.
  • Suggestion: Consider either (a) adding a model validator that ensures consistency between the two lists, (b) updating link_plan() to accept optional phase/state parameters and populate both lists, or (c) documenting the intended migration path clearly. At minimum, the link_plan() docstring should note that it only populates linked_plan_ids and that linked_plans must be populated separately for full spec-compliant output.

2. [BEHAVIOR] Fallback Uses Empty Strings Instead of Explicit "Unknown"

  • Location: src/cleveragents/domain/models/core/session.py — as_cli_dict(), the elif self.linked_plan_ids: branch
  • Issue: When only flat IDs are available, the fallback emits {"plan_id": pid, "phase": "", "state": ""}. Empty strings are ambiguous — they could mean "not set", "unknown", or "intentionally blank". The spec example shows actual values like "execute" and "complete".
  • Suggestion: Consider using "unknown" instead of "" for the fallback phase/state values, which is more explicit and less likely to confuse downstream consumers.

3. [SPEC-COMPLIANCE] Missing ULID Validation on LinkedPlan.plan_id

  • Location: src/cleveragents/domain/models/core/session.py — LinkedPlan class
  • Issue: LinkedPlan.plan_id is declared as str without pattern=ULID_PATTERN validation, while Session.session_id and SessionMessage.message_id both enforce the ULID pattern. This is inconsistent — plan IDs should be ULIDs per the spec.
  • Suggestion: Add pattern=ULID_PATTERN to the plan_id field for consistency with the rest of the codebase.

4. [PROCESS] PR Missing Milestone and Labels

  • Location: PR metadata
  • Issue: Per CONTRIBUTING.md, every PR must be assigned to the same milestone as its linked issue and must have exactly one Type/ label. Issue #3440 is in milestone v3.7.0 and has label Type/Bug. This PR has neither a milestone nor any labels.
  • Required: Assign milestone v3.7.0 and add label Type/Bug.

5. [BEHAVIOR] estimated_cost Format Precision

  • Location: src/cleveragents/domain/models/core/session.py — as_cli_dict(), f"${cost:.4f}"
  • Issue: The format always uses exactly 4 decimal places. The spec example shows "$0.0184" (4 decimals). This works for the example, but for larger costs like $12.50, it would produce "$12.5000". For very small costs like $0.000001, it would produce "$0.0000" (losing precision). This is a minor concern but worth considering whether a dynamic precision or minimum significant digits approach would be more appropriate.
  • Suggestion: This is acceptable for now but consider whether the spec intends a specific precision contract.

6. [API-CONSISTENCY] as_export_dict() Not Updated

  • Location: src/cleveragents/domain/models/core/session.py — as_export_dict()
  • Issue: The export dict still uses linked_plan_ids (flat list) and estimated_cost as a raw float. While the export format may intentionally differ from the CLI display format (export is for data interchange, CLI is for human/machine display), this creates two different serialization contracts for the same model. The as_export_dict() docstring doesn't mention this distinction.
  • Suggestion: This may be intentional (export preserves raw data, CLI formats for display), but it should be documented explicitly in the as_export_dict() docstring to prevent future confusion.

📋 Summary

Category Status
Spec Compliance (as_cli_dict output) ✅ Correct
Commit Message Format ✅ Correct
Type Safety ✅ No suppressions
LinkedPlan Value Object ✅ Well-designed
init.py Export ✅ Correct
Dual linked_plan_ids/linked_plans ⚠️ Consistency risk
LinkedPlan.plan_id validation ⚠️ Missing ULID pattern
PR Milestone & Labels ❌ Missing
Fallback empty strings ⚠️ Minor — prefer "unknown"
Test coverage ⚠️ Cannot verify — unit tests noted as hanging

The core implementation is solid and correctly addresses the spec compliance issues. The main concerns are around the dual-representation consistency risk and missing PR metadata. Items #1 (dual representation) and #4 (missing milestone/labels) should be addressed before merge.

Automated by CleverAgents Bot
Reviewer: Code Quality | Agent: ca-pr-self-reviewer

## PR #3461 Review — `fix(session): correct field names and data types in Session.as_cli_dict() for spec compliance` **Review Focus**: specification-compliance, behavior-correctness, api-consistency **Linked Issue**: #3440 (UAT: `agents session show` JSON output uses wrong field names) --- ### ✅ What Looks Good 1. **Specification Compliance**: The rewritten `as_cli_dict()` correctly produces the spec-required structure with `session_summary` wrapper, renamed fields (`id`, `actor`, `messages`, `created`, `updated`), `automation` field, `text` key in `recent_messages`, `linked_plans` as objects, and `estimated_cost` as formatted string. This directly addresses all 9 violations listed in #3440. 2. **Architectural Decision**: Adding `LinkedPlan` as a value object in the domain model is the right approach — it keeps the domain model as the owner of its data rather than requiring service-layer lookups at display time. 3. **Commit Message**: ✅ Follows Conventional Changelog format exactly as specified in the issue metadata. 4. **ISSUES CLOSED Footer**: ✅ Present (`ISSUES CLOSED: #3440`). 5. **PR Description**: ✅ Thorough, well-structured, includes `Closes #3440`. 6. **No Forbidden Patterns**: ✅ No `# type: ignore`, imports at top of file, proper type annotations throughout. 7. **`LinkedPlan` Model**: Clean Pydantic BaseModel with proper `Field` descriptors, `str_strip_whitespace`, and `validate_assignment`. 8. **`__init__.py` Export**: `LinkedPlan` correctly added to both the import block and `__all__` list, maintaining alphabetical ordering. --- ### ⚠️ Issues Requiring Attention #### 1. **[API-CONSISTENCY] Dual Representation Creates Consistency Risk** — `linked_plan_ids` vs `linked_plans` - **Location**: `src/cleveragents/domain/models/core/session.py` — `Session` model fields - **Issue**: The `Session` model now has **both** `linked_plan_ids: list[str]` and `linked_plans: list[LinkedPlan]`. The existing `link_plan()` method (which is the primary API for linking plans) only appends to `linked_plan_ids` — it does not create a corresponding `LinkedPlan` entry. This means after calling `link_plan("some-ulid")`, the `as_cli_dict()` method will fall through to the fallback path and emit `{"plan_id": "some-ulid", "phase": "", "state": ""}` with empty strings. - **Risk**: Any code path that uses `link_plan()` (the existing API) will produce degraded output. The two lists can drift out of sync with no validation preventing it. - **Suggestion**: Consider either (a) adding a model validator that ensures consistency between the two lists, (b) updating `link_plan()` to accept optional `phase`/`state` parameters and populate both lists, or (c) documenting the intended migration path clearly. At minimum, the `link_plan()` docstring should note that it only populates `linked_plan_ids` and that `linked_plans` must be populated separately for full spec-compliant output. #### 2. **[BEHAVIOR] Fallback Uses Empty Strings Instead of Explicit "Unknown"** - **Location**: `src/cleveragents/domain/models/core/session.py` — `as_cli_dict()`, the `elif self.linked_plan_ids:` branch - **Issue**: When only flat IDs are available, the fallback emits `{"plan_id": pid, "phase": "", "state": ""}`. Empty strings are ambiguous — they could mean "not set", "unknown", or "intentionally blank". The spec example shows actual values like `"execute"` and `"complete"`. - **Suggestion**: Consider using `"unknown"` instead of `""` for the fallback phase/state values, which is more explicit and less likely to confuse downstream consumers. #### 3. **[SPEC-COMPLIANCE] Missing ULID Validation on `LinkedPlan.plan_id`** - **Location**: `src/cleveragents/domain/models/core/session.py` — `LinkedPlan` class - **Issue**: `LinkedPlan.plan_id` is declared as `str` without `pattern=ULID_PATTERN` validation, while `Session.session_id` and `SessionMessage.message_id` both enforce the ULID pattern. This is inconsistent — plan IDs should be ULIDs per the spec. - **Suggestion**: Add `pattern=ULID_PATTERN` to the `plan_id` field for consistency with the rest of the codebase. #### 4. **[PROCESS] PR Missing Milestone and Labels** - **Location**: PR metadata - **Issue**: Per CONTRIBUTING.md, every PR must be assigned to the same milestone as its linked issue and must have exactly one `Type/` label. Issue #3440 is in milestone **v3.7.0** and has label `Type/Bug`. This PR has neither a milestone nor any labels. - **Required**: Assign milestone `v3.7.0` and add label `Type/Bug`. #### 5. **[BEHAVIOR] `estimated_cost` Format Precision** - **Location**: `src/cleveragents/domain/models/core/session.py` — `as_cli_dict()`, `f"${cost:.4f}"` - **Issue**: The format always uses exactly 4 decimal places. The spec example shows `"$0.0184"` (4 decimals). This works for the example, but for larger costs like `$12.50`, it would produce `"$12.5000"`. For very small costs like `$0.000001`, it would produce `"$0.0000"` (losing precision). This is a minor concern but worth considering whether a dynamic precision or minimum significant digits approach would be more appropriate. - **Suggestion**: This is acceptable for now but consider whether the spec intends a specific precision contract. #### 6. **[API-CONSISTENCY] `as_export_dict()` Not Updated** - **Location**: `src/cleveragents/domain/models/core/session.py` — `as_export_dict()` - **Issue**: The export dict still uses `linked_plan_ids` (flat list) and `estimated_cost` as a raw float. While the export format may intentionally differ from the CLI display format (export is for data interchange, CLI is for human/machine display), this creates two different serialization contracts for the same model. The `as_export_dict()` docstring doesn't mention this distinction. - **Suggestion**: This may be intentional (export preserves raw data, CLI formats for display), but it should be documented explicitly in the `as_export_dict()` docstring to prevent future confusion. --- ### 📋 Summary | Category | Status | |----------|--------| | Spec Compliance (as_cli_dict output) | ✅ Correct | | Commit Message Format | ✅ Correct | | Type Safety | ✅ No suppressions | | LinkedPlan Value Object | ✅ Well-designed | | __init__.py Export | ✅ Correct | | Dual linked_plan_ids/linked_plans | ⚠️ Consistency risk | | LinkedPlan.plan_id validation | ⚠️ Missing ULID pattern | | PR Milestone & Labels | ❌ Missing | | Fallback empty strings | ⚠️ Minor — prefer "unknown" | | Test coverage | ⚠️ Cannot verify — unit tests noted as hanging | The core implementation is solid and correctly addresses the spec compliance issues. The main concerns are around the dual-representation consistency risk and missing PR metadata. Items #1 (dual representation) and #4 (missing milestone/labels) should be addressed before merge. --- **Automated by CleverAgents Bot** Reviewer: Code Quality | Agent: ca-pr-self-reviewer
freemo merged commit 4d32281351 into master 2026-04-05 18:19:20 +00:00
freemo deleted branch bugfix/session-show-as-cli-dict-field-names 2026-04-05 18:19:20 +00:00
Sign in to join this conversation.
Reviewers
No reviewers
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
1 participant
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!3461
No description provided.