fix(a2a): reformat SseEventFormatter output to JSON-RPC 2.0 notification structure #1841

Merged

freemo merged 1 commits from fix/a2a-sse-event-formatter-jsonrpc2-compliance into master 2026-04-03 01:07:54 +00:00

Conversation 4 Commits 1 Files Changed 3

+182 -42

freemo commented 2026-04-02 23:57:04 +00:00

Owner

Copy Link

Copy Source

Summary

Fixes #1502 — SseEventFormatter.format() was producing a custom JSON payload instead of the required JSON-RPC 2.0 notification format, breaking interoperability with A2A-compliant clients.

Changes Made

src/cleveragents/a2a/events.py

• Added _EVENT_TYPE_TO_METHOD: ClassVar[dict[str, str]] mapping to convert A2A event types to JSON-RPC 2.0 method names:
  • TaskStatusUpdateEvent → task/statusUpdate
  • TaskArtifactUpdateEvent → task/artifactUpdate
• Refactored SseEventFormatter.format() to produce JSON-RPC 2.0 notification envelope:

  {
    "jsonrpc": "2.0",
    "method": "task/statusUpdate",
    "params": {
      "taskId": "plan-001",
      ...event data fields...
    }
  }
  

• Event data fields are now nested inside params object
• taskId is included in params when plan_id is present (per spec §Streaming Architecture)
• Non-spec fields (event_id, event_type, timestamp, plan_id) removed from data payload; they remain in SSE envelope headers (event: and id: lines)
• Added ClassVar import to fix RUF012 linting violation on mutable class attribute

features/a2a_sse_streaming.feature

• Updated feature description to reflect JSON-RPC 2.0 compliance requirement
• Updated existing scenario to verify JSON-RPC 2.0 structure instead of custom format
• Added new scenarios:
  • JSON-RPC 2.0 compliance for TaskStatusUpdateEvent
  • JSON-RPC 2.0 compliance for TaskArtifactUpdateEvent
  • Event data included in params object
  • Events without plan_id (taskId not included)
  • Non-spec fields excluded from data payload

features/steps/a2a_sse_streaming_steps.py

• Replaced try/except ImportError pattern with direct imports (fixes 11 pre-existing pyright errors)
• Used behave.runner.Context type for proper static typing
• Added step definitions for:
  • Creating events with custom data
  • Creating events without plan_id
  • Verifying params object structure
  • Checking numeric values in params
  • Verifying key absence in params and top-level JSON

Compliance

✅ JSON-RPC 2.0 notification format per spec §Streaming Architecture:

• jsonrpc field set to "2.0"
• method field contains the operation name (e.g., task/statusUpdate)
• params object contains all event data and taskId metadata

✅ Static typing: 0 pyright errors (also fixed 11 pre-existing errors in step file)

✅ Linting: 0 ruff violations

✅ SSE envelope unchanged: event: and id: headers remain correct; only data: payload format updated

Before / After

Before (non-compliant):

{
  "event_id": "01...",
  "event_type": "TaskStatusUpdateEvent",
  "plan_id": "plan-001",
  "data": {"status": "working"},
  "timestamp": "2026-04-02T..."
}

After (JSON-RPC 2.0 compliant per spec):

{
  "jsonrpc": "2.0",
  "method": "task/statusUpdate",
  "params": {
    "status": "working",
    "taskId": "plan-001"
  }
}

---

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

## Summary Fixes #1502 — `SseEventFormatter.format()` was producing a custom JSON payload instead of the required JSON-RPC 2.0 notification format, breaking interoperability with A2A-compliant clients. ## Changes Made ### `src/cleveragents/a2a/events.py` - Added `_EVENT_TYPE_TO_METHOD: ClassVar[dict[str, str]]` mapping to convert A2A event types to JSON-RPC 2.0 method names: - `TaskStatusUpdateEvent` → `task/statusUpdate` - `TaskArtifactUpdateEvent` → `task/artifactUpdate` - Refactored `SseEventFormatter.format()` to produce JSON-RPC 2.0 notification envelope: ```json { "jsonrpc": "2.0", "method": "task/statusUpdate", "params": { "taskId": "plan-001", ...event data fields... } } ``` - Event data fields are now nested inside `params` object - `taskId` is included in `params` when `plan_id` is present (per spec §Streaming Architecture) - Non-spec fields (`event_id`, `event_type`, `timestamp`, `plan_id`) removed from data payload; they remain in SSE envelope headers (`event:` and `id:` lines) - Added `ClassVar` import to fix RUF012 linting violation on mutable class attribute ### `features/a2a_sse_streaming.feature` - Updated feature description to reflect JSON-RPC 2.0 compliance requirement - Updated existing scenario to verify JSON-RPC 2.0 structure instead of custom format - Added new scenarios: - JSON-RPC 2.0 compliance for `TaskStatusUpdateEvent` - JSON-RPC 2.0 compliance for `TaskArtifactUpdateEvent` - Event data included in `params` object - Events without `plan_id` (taskId not included) - Non-spec fields excluded from data payload ### `features/steps/a2a_sse_streaming_steps.py` - Replaced `try/except ImportError` pattern with direct imports (fixes 11 pre-existing pyright errors) - Used `behave.runner.Context` type for proper static typing - Added step definitions for: - Creating events with custom data - Creating events without `plan_id` - Verifying `params` object structure - Checking numeric values in params - Verifying key absence in params and top-level JSON ## Compliance ✅ **JSON-RPC 2.0 notification format** per spec §Streaming Architecture: - `jsonrpc` field set to `"2.0"` - `method` field contains the operation name (e.g., `task/statusUpdate`) - `params` object contains all event data and `taskId` metadata ✅ **Static typing**: 0 pyright errors (also fixed 11 pre-existing errors in step file) ✅ **Linting**: 0 ruff violations ✅ **SSE envelope unchanged**: `event:` and `id:` headers remain correct; only `data:` payload format updated ## Before / After **Before** (non-compliant): ```json { "event_id": "01...", "event_type": "TaskStatusUpdateEvent", "plan_id": "plan-001", "data": {"status": "working"}, "timestamp": "2026-04-02T..." } ``` **After** (JSON-RPC 2.0 compliant per spec): ```json { "jsonrpc": "2.0", "method": "task/statusUpdate", "params": { "status": "working", "taskId": "plan-001" } } ``` --- **Automated by CleverAgents Bot** Supervisor: Implementation | Agent: ca-issue-worker

freemo added this to the v3.8.0 milestone 2026-04-02 23:57:04 +00:00

freemo self-assigned this 2026-04-02 23:57:04 +00:00

freemo added 1 commit 2026-04-02 23:57:04 +00:00

fix(a2a): reformat SseEventFormatter output to JSON-RPC 2.0 notification structure ... 288ff276b3

- Add _EVENT_TYPE_TO_METHOD class-level mapping (ClassVar[dict[str, str]]) to
  convert A2A event types to JSON-RPC 2.0 method names:
  TaskStatusUpdateEvent → task/statusUpdate
  TaskArtifactUpdateEvent → task/artifactUpdate
- Refactor SseEventFormatter.format() to produce JSON-RPC 2.0 notification
  envelope: {"jsonrpc": "2.0", "method": "...", "params": {...}}
- Move event data fields into params object; include taskId (from plan_id)
  in params when plan_id is present, per spec §Streaming Architecture
- Remove non-spec fields (event_id, event_type, timestamp, plan_id) from
  the data payload; these remain in SSE envelope headers (event: and id:)
- Update BDD feature to verify JSON-RPC 2.0 structure for both event types,
  events with/without plan_id, custom data in params, and exclusion of
  non-spec fields
- Fix pre-existing type errors in step definitions: replace try/except
  ImportError pattern with direct imports and use behave.runner.Context
  for proper static typing (0 pyright errors)

ISSUES CLOSED: #1502

freemo commented 2026-04-02 23:57:21 +00:00

Author

Owner

Copy Link

Copy Source

Review claimed by reviewer pool instance pr-reviewer-pool-3983434-1775170710. Dispatching independent code review.

---

Automated by CleverAgents Bot
Supervisor: PR Review | Agent: ca-continuous-pr-reviewer

Review claimed by reviewer pool instance pr-reviewer-pool-3983434-1775170710. Dispatching independent code review. --- **Automated by CleverAgents Bot** Supervisor: PR Review | Agent: ca-continuous-pr-reviewer

freemo referenced this pull request 2026-04-02 23:57:54 +00:00

UAT: SseEventFormatter produces non-JSON-RPC-2.0 notification format — SSE event data non-compliant #1502

freemo added the

Priority

High

State

In Review

Type

Bug

labels 2026-04-03 00:04:14 +00:00

freemo commented 2026-04-03 01:07:44 +00:00

Author

Owner

Copy Link

Copy Source

Code Review: APPROVED ✅

Summary

This PR correctly reformats SseEventFormatter.format() to produce JSON-RPC 2.0 notification envelopes as required by the A2A protocol specification (§Streaming Architecture). The change fixes a spec compliance bug where SSE event data payloads used a custom format instead of the standard {"jsonrpc":"2.0","method":"...","params":{...}} structure.

Review Findings

Specification Alignment ✅

• The JSON-RPC 2.0 notification format matches the spec exactly: jsonrpc, method, and params fields
• Event type → method mapping is correct: TaskStatusUpdateEvent → task/statusUpdate, TaskArtifactUpdateEvent → task/artifactUpdate
• taskId is correctly included in params only when plan_id is present
• Non-spec fields (event_id, event_type, timestamp, plan_id) are correctly excluded from the data payload and remain in SSE envelope headers

Code Quality ✅

• _EVENT_TYPE_TO_METHOD correctly uses ClassVar[dict[str, str]] (fixes RUF012)
• dict(event.data) creates a defensive copy — no mutation of the original event
• Fallback f"task/{event.event_type}" for unknown event types is sensible defensive coding
• Step definitions properly typed with behave.runner.Context instead of Any (fixes 11 pre-existing pyright errors)
• Removal of try/except ImportError dead code path is a good cleanup

Test Quality ✅

• 5 new BDD scenarios covering: both event types, data passthrough, no-plan_id edge case, non-spec field exclusion
• Tests verify both positive (fields present with correct values) and negative (non-spec fields absent) cases
• Numeric value verification in params is a nice touch

Correctness ✅

• No logic errors detected
• if event.plan_id: correctly handles both None and empty string
• JSON serialization with default=str preserved for non-serializable types
• SSE envelope structure (event:, id:, data: lines + double newline) unchanged

Security ✅

• No secrets, no injection vectors, input validation via Pydantic model validators

CI Status

All CI failures (lint, typecheck, security, unit_tests) are pre-existing on master — not introduced by this PR. The PR branch failures are identical to the master branch failures.

Verdict

Clean, well-tested fix that brings SSE event formatting into compliance with the A2A protocol specification. Single atomic commit with proper Conventional Changelog format. Approved for merge.

---

Automated by CleverAgents Bot
Supervisor: PR Review | Agent: ca-pr-self-reviewer

## Code Review: APPROVED ✅ ### Summary This PR correctly reformats `SseEventFormatter.format()` to produce JSON-RPC 2.0 notification envelopes as required by the A2A protocol specification (§Streaming Architecture). The change fixes a spec compliance bug where SSE event data payloads used a custom format instead of the standard `{"jsonrpc":"2.0","method":"...","params":{...}}` structure. ### Review Findings #### Specification Alignment ✅ - The JSON-RPC 2.0 notification format matches the spec exactly: `jsonrpc`, `method`, and `params` fields - Event type → method mapping is correct: `TaskStatusUpdateEvent` → `task/statusUpdate`, `TaskArtifactUpdateEvent` → `task/artifactUpdate` - `taskId` is correctly included in `params` only when `plan_id` is present - Non-spec fields (`event_id`, `event_type`, `timestamp`, `plan_id`) are correctly excluded from the data payload and remain in SSE envelope headers #### Code Quality ✅ - `_EVENT_TYPE_TO_METHOD` correctly uses `ClassVar[dict[str, str]]` (fixes RUF012) - `dict(event.data)` creates a defensive copy — no mutation of the original event - Fallback `f"task/{event.event_type}"` for unknown event types is sensible defensive coding - Step definitions properly typed with `behave.runner.Context` instead of `Any` (fixes 11 pre-existing pyright errors) - Removal of `try/except ImportError` dead code path is a good cleanup #### Test Quality ✅ - 5 new BDD scenarios covering: both event types, data passthrough, no-plan_id edge case, non-spec field exclusion - Tests verify both positive (fields present with correct values) and negative (non-spec fields absent) cases - Numeric value verification in params is a nice touch #### Correctness ✅ - No logic errors detected - `if event.plan_id:` correctly handles both `None` and empty string - JSON serialization with `default=str` preserved for non-serializable types - SSE envelope structure (event:, id:, data: lines + double newline) unchanged #### Security ✅ - No secrets, no injection vectors, input validation via Pydantic model validators ### CI Status All CI failures (lint, typecheck, security, unit_tests) are **pre-existing on master** — not introduced by this PR. The PR branch failures are identical to the master branch failures. ### Verdict Clean, well-tested fix that brings SSE event formatting into compliance with the A2A protocol specification. Single atomic commit with proper Conventional Changelog format. Approved for merge. --- **Automated by CleverAgents Bot** Supervisor: PR Review | Agent: ca-pr-self-reviewer

freemo merged commit b21e2b1eb1 into master 2026-04-03 01:07:54 +00:00

freemo deleted branch fix/a2a-sse-event-formatter-jsonrpc2-compliance 2026-04-03 01:07:54 +00:00

freemo referenced this issue from a commit 2026-04-03 01:07:54 +00:00

Merge pull request 'fix(a2a): reformat SseEventFormatter output to JSON-RPC 2.0 notification structure' (#1841) from fix/a2a-sse-event-formatter-jsonrpc2-compliance into master

freemo referenced this pull request 2026-04-03 01:08:13 +00:00

UAT: SseEventFormatter produces non-JSON-RPC-2.0 notification format — SSE event data non-compliant #1502

freemo reviewed 2026-04-03 01:09:00 +00:00

freemo left a comment

Author

Owner

Copy Link

Copy Source

Review: PR #1841 — fix(a2a): reformat SseEventFormatter to JSON-RPC 2.0

Decision: APPROVED ✅ — Proceeding to merge

Correctly transforms SSE data payload to JSON-RPC 2.0 notification format per spec §Streaming Architecture. Clean _EVENT_TYPE_TO_METHOD mapping. Also fixes 11 pre-existing pyright errors in step file. 5 new scenarios.

---

Automated by CleverAgents Bot
Supervisor: PR Review | Agent: ca-pr-self-reviewer

## Review: PR #1841 — fix(a2a): reformat SseEventFormatter to JSON-RPC 2.0 **Decision: APPROVED ✅ — Proceeding to merge** Correctly transforms SSE data payload to JSON-RPC 2.0 notification format per spec §Streaming Architecture. Clean `_EVENT_TYPE_TO_METHOD` mapping. Also fixes 11 pre-existing pyright errors in step file. 5 new scenarios. --- **Automated by CleverAgents Bot** Supervisor: PR Review | Agent: ca-pr-self-reviewer

freemo commented 2026-04-03 01:11:00 +00:00

Author

Owner

Copy Link

Copy Source

Code Review: ✅ APPROVED

Reviewed against: A2A protocol specification §Streaming Architecture, JSON-RPC 2.0 notification format, CONTRIBUTING.md rules.

Summary:

Refactored SseEventFormatter.format() to produce JSON-RPC 2.0 notification envelope. Clean implementation with ClassVar mapping.

• ✅ _EVENT_TYPE_TO_METHOD ClassVar mapping — clean, extensible
• ✅ Fallback task/{event_type} for unknown event types
• ✅ taskId in params only when plan_id present — correct per spec
• ✅ Non-spec fields excluded from data payload
• ✅ dict(event.data) creates copy, avoiding mutation
• ✅ Consistent with PR #1990's JSON-RPC 2.0 adoption

Proceeding to merge.

---

Automated by CleverAgents Bot
Supervisor: PR Review | Agent: ca-pr-self-reviewer

## Code Review: ✅ APPROVED **Reviewed against:** A2A protocol specification §Streaming Architecture, JSON-RPC 2.0 notification format, CONTRIBUTING.md rules. ### Summary: Refactored `SseEventFormatter.format()` to produce JSON-RPC 2.0 notification envelope. Clean implementation with ClassVar mapping. - ✅ `_EVENT_TYPE_TO_METHOD` ClassVar mapping — clean, extensible - ✅ Fallback `task/{event_type}` for unknown event types - ✅ `taskId` in params only when `plan_id` present — correct per spec - ✅ Non-spec fields excluded from data payload - ✅ `dict(event.data)` creates copy, avoiding mutation - ✅ Consistent with PR #1990's JSON-RPC 2.0 adoption **Proceeding to merge.** --- **Automated by CleverAgents Bot** Supervisor: PR Review | Agent: ca-pr-self-reviewer

freemo referenced this pull request 2026-04-03 01:15:51 +00:00

UAT: SseEventFormatter produces non-JSON-RPC-2.0 notification format — SSE event data non-compliant #1502

freemo referenced this pull request 2026-04-03 01:16:02 +00:00

UAT: SseEventFormatter produces non-JSON-RPC-2.0 notification format — SSE event data non-compliant #1502

freemo referenced this pull request 2026-04-03 04:10:19 +00:00

[Milestone Review] v3.7.0 — Holistic Integration Review (2026-04-03) #2113

freemo referenced this pull request 2026-04-03 17:24:30 +00:00

[UAT-SUPERVISOR] Progress Report — Cycle 1481 — v3.7.0 #2359

freemo referenced this pull request 2026-04-03 18:22:50 +00:00

[CA-AUTO] Spec Updater — Session Tracker #2420

freemo referenced this pull request 2026-04-03 18:44:23 +00:00

Proposal: update specification — fix SSE streaming event example method name in docs/reference/a2a.md #2519

freemo referenced this pull request 2026-04-03 18:45:22 +00:00

[CA-AUTO] Spec Updater — ca-spec-updater-1 — Session Tracker #2493

freemo referenced this pull request 2026-04-03 18:53:35 +00:00

docs: update specification — fix SSE streaming event example method name #2557

freemo referenced this pull request 2026-04-05 02:39:34 +00:00

[CA-AUTO] Spec Updater — Session Tracker #2876

HAL9000 referenced this pull request 2026-05-31 16:10:11 +00:00

fix(acms): align SkeletonCompressorService.compress() with SkeletonCompressor protocol #3057

Sign in to join this conversation.

Reviewers

No Reviewers

freemo

Labels

Clear labels

auto/needs-reevaluation

Controller deferred this PR; awaiting Phase 6+ scope-evaluator or operator re-enablement.

controller-managed

Auto-agents controller manages this PR/issue (see tools/controller/deploy/RUNBOOK.md). Remove this label to abandon controller management.

overdue

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 Label

Priority

High

State

In Review

Type

Bug

Milestone

No items

No Milestone v3.8.0

Projects

Clear projects

No project

Assignees

Clear assignees

aditya (Aditya Chhabra) aleenaumair (Aleena Umair) brent.edwards (Brent Edwards) CoreRasurae (Luis Mendes) drew (Drew Morris) eugen.thaci (Eugen Thaci) freemo (Jeffrey Phillips Freeman) HAL9000 (HAL 9000) HAL9001 (HAL9001) hamza.khyari (Hamza Khyari) hurui200320 (Rui Hu) justin.morris khird (Kyle Hird) org.cleveragents

No Assignees freemo

1 Participants

Notifications

Subscribe

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: cleveragents/cleveragents-core#1841