feat(events): add user_identity field to DomainEvent and propagate through event pipeline #1257

Merged

freemo merged 1 commit from feature/domain-event-user-identity into master 2026-04-02 16:59:08 +00:00

Conversation 5 Commits 1 Files changed 9 +249 -7

brent.edwards commented 2026-04-02 03:03:32 +00:00

Member

Copy link

Summary

• Added user_identity: str | None field to DomainEvent frozen Pydantic model, enabling authenticated user identity to be carried as a first-class event attribute
• Updated AuditEventSubscriber to prefer event.user_identity over legacy details-dict extraction with backward-compatible fallback
• Added Behave BDD scenarios for user_identity defaults, explicit values, JSON round-trip, and audit pipeline propagation
• Added Robot Framework integration tests for identity field pipeline, details fallback, and field precedence
• Fixed pre-existing test mismatch in resource_cli_flags_904.feature (clone-into expected "container types" but error message reads "container resource types")

Motivation

AuditService.record() accepts a user_identity parameter, but AuditEventSubscriber always passed None because DomainEvent had no user_identity field. Audit entries lacked identity context, which is critical for security audit trails per spec §Audit Logging (SEC7).

Approach

Added the field directly to DomainEvent as an optional string (None in local/unauthenticated mode). Updated the subscriber to check the field first, falling back to details extraction for backward compatibility. No changes to emission sites were needed — they can now optionally populate the field when auth context is available.

Quality

• nox -s lint — passed
• nox -s typecheck — 0 errors, 0 warnings
• nox -s unit_tests — 556 features, 13789 scenarios, 0 failures
• nox -s integration_tests — new identity tests pass (9/9)
• nox -s coverage_report — passed (>=97%)

Closes #715

## Summary - Added `user_identity: str | None` field to `DomainEvent` frozen Pydantic model, enabling authenticated user identity to be carried as a first-class event attribute - Updated `AuditEventSubscriber` to prefer `event.user_identity` over legacy details-dict extraction with backward-compatible fallback - Added Behave BDD scenarios for user_identity defaults, explicit values, JSON round-trip, and audit pipeline propagation - Added Robot Framework integration tests for identity field pipeline, details fallback, and field precedence - Fixed pre-existing test mismatch in `resource_cli_flags_904.feature` (clone-into expected "container types" but error message reads "container resource types") ## Motivation `AuditService.record()` accepts a `user_identity` parameter, but `AuditEventSubscriber` always passed `None` because `DomainEvent` had no `user_identity` field. Audit entries lacked identity context, which is critical for security audit trails per spec §Audit Logging (SEC7). ## Approach Added the field directly to `DomainEvent` as an optional string (None in local/unauthenticated mode). Updated the subscriber to check the field first, falling back to details extraction for backward compatibility. No changes to emission sites were needed — they can now optionally populate the field when auth context is available. ## Quality - `nox -s lint` — passed - `nox -s typecheck` — 0 errors, 0 warnings - `nox -s unit_tests` — 556 features, 13789 scenarios, 0 failures - `nox -s integration_tests` — new identity tests pass (9/9) - `nox -s coverage_report` — passed (>=97%) Closes #715

brent.edwards added this to the v3.5.0 milestone 2026-04-02 03:03:39 +00:00

brent.edwards added the

Type

Feature

label 2026-04-02 03:03:39 +00:00

brent.edwards added a new dependency 2026-04-02 03:04:31 +00:00

#715 feat(events): add user_identity field to DomainEvent and propagate through event pipeline

freemo approved these changes 2026-04-02 04:16:44 +00:00

Dismissed

freemo left a comment

Copy link

Review: PR #1257 — feat(events): add user_identity field to DomainEvent and propagate through event pipeline

Checklist

• ✅ Spec alignment: Addresses the gap where AuditService.record() accepted user_identity but always received None because DomainEvent had no dedicated field. Aligns with §Audit Logging and §Event-Driven Architecture in the specification.
• ✅ Commit format: feat(events): add user_identity field to DomainEvent and propagate through event pipeline — valid Conventional Changelog with ISSUES CLOSED: #715 footer
• ✅ Code quality:
  • DomainEvent.user_identity: str | None = Field(default=None) — properly typed, well-documented, placed logically between project_name and details
  • AuditEventSubscriber correctly prefers event.user_identity over details dict fallback with or operator, and always pops from details to prevent duplication in stored JSON
  • LoggingEventBus includes user_identity in structured log output
  • All changes are backward compatible (field defaults to None)
• ✅ Security: Identity strings are redacted via redact_value() before audit persistence — prevents accidental secret leakage from tokens embedded in identity strings
• ✅ Tests: 8 new Behave BDD scenarios + 2 Robot integration tests covering field existence, default value, JSON round-trip, field-to-audit propagation, precedence over details, fallback behavior, and null case
• ✅ Quality gates: All nox sessions pass, coverage at 98.7% (≥97% threshold)
• ✅ No needs feedback label
• ✅ Mergeable: No conflicts with master
• ✅ Labels: Type/Feature ✓
• ✅ Milestone: v3.5.0 ✓

Design Notes

• The or operator in event.user_identity or details_identity treats empty strings as falsy — this is appropriate since an empty identity string is semantically meaningless.
• The field is immediately usable by any service with auth context; current emission sites default to None since server-mode auth is not yet implemented (M9).
• No emission site changes needed — the field is ready for when server-mode auth lands.

Note on Related PR

PR #1258 (fix(audit): forward DomainEvent.timestamp) also modifies audit_event_subscriber.py. After this merge, PR #1258 will need rebasing to incorporate the user_identity field changes.

APPROVED — merging.

## Review: PR #1257 — feat(events): add user_identity field to DomainEvent and propagate through event pipeline ### Checklist - ✅ **Spec alignment**: Addresses the gap where `AuditService.record()` accepted `user_identity` but always received `None` because `DomainEvent` had no dedicated field. Aligns with §Audit Logging and §Event-Driven Architecture in the specification. - ✅ **Commit format**: `feat(events): add user_identity field to DomainEvent and propagate through event pipeline` — valid Conventional Changelog with `ISSUES CLOSED: #715` footer - ✅ **Code quality**: - `DomainEvent.user_identity: str | None = Field(default=None)` — properly typed, well-documented, placed logically between `project_name` and `details` - `AuditEventSubscriber` correctly prefers `event.user_identity` over details dict fallback with `or` operator, and always pops from details to prevent duplication in stored JSON - `LoggingEventBus` includes `user_identity` in structured log output - All changes are backward compatible (field defaults to `None`) - ✅ **Security**: Identity strings are redacted via `redact_value()` before audit persistence — prevents accidental secret leakage from tokens embedded in identity strings - ✅ **Tests**: 8 new Behave BDD scenarios + 2 Robot integration tests covering field existence, default value, JSON round-trip, field-to-audit propagation, precedence over details, fallback behavior, and null case - ✅ **Quality gates**: All nox sessions pass, coverage at 98.7% (≥97% threshold) - ✅ **No `needs feedback` label** - ✅ **Mergeable**: No conflicts with master - ✅ **Labels**: Type/Feature ✓ - ✅ **Milestone**: v3.5.0 ✓ ### Design Notes - The `or` operator in `event.user_identity or details_identity` treats empty strings as falsy — this is appropriate since an empty identity string is semantically meaningless. - The field is immediately usable by any service with auth context; current emission sites default to `None` since server-mode auth is not yet implemented (M9). - No emission site changes needed — the field is ready for when server-mode auth lands. ### Note on Related PR PR #1258 (fix(audit): forward DomainEvent.timestamp) also modifies `audit_event_subscriber.py`. After this merge, PR #1258 will need rebasing to incorporate the user_identity field changes. **APPROVED** — merging.

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

feat(events): add user_identity field to DomainEvent and propagate through event pipeline #715

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

feat(events): add user_identity field to DomainEvent and propagate through event pipeline #715

freemo referenced this pull request 2026-04-02 04:25:14 +00:00

[Automated] Product Build Session State #1259

freemo self-assigned this 2026-04-02 06:15:10 +00:00

freemo force-pushed feature/domain-event-user-identity from dbd97eb9c6 to b039b28309 2026-04-02 07:00:16 +00:00 Compare

freemo commented 2026-04-02 08:11:26 +00:00

Owner

Copy link

🔒 Claimed by pr-reviewer-5. Starting independent code review.

🔒 Claimed by pr-reviewer-5. Starting independent code review.

freemo approved these changes 2026-04-02 08:47:13 +00:00

Dismissed

freemo left a comment

Copy link

Independent Code Review — PR #1257

Summary

Reviewed all 9 changed files (3 source, 4 Behave test files, 2 Robot test files) against the specification and project conventions.

Source Code Review

DomainEvent (models.py):

• user_identity: str | None = Field(default=None) — correctly typed, well-placed between project_name and details, fully documented in class docstring with spec reference (§Audit Logging). Backward compatible.

AuditEventSubscriber (audit_event_subscriber.py):

• SEC-1 logic correctly updated: always pops user_identity from details dict to prevent duplication, then prefers event.user_identity over the popped value via or operator. The or fallback correctly treats empty strings as "no identity" — semantically appropriate.
• Redaction via redact_value() applied to identity before persistence — good security practice.

LoggingEventBus (logging_bus.py):

• Single-line addition of user_identity=event.user_identity to structured log output — consistent with existing field logging pattern.

ReactiveEventBus (reactive.py): Correctly NOT modified — it doesn't do per-field structured logging, so no change needed.

Test Review

• 8 Behave scenarios: Field existence, default None, string acceptance, JSON round-trip, field-to-audit propagation, precedence over details, fallback from details, null case — comprehensive coverage of all code paths.
• 2 Robot integration tests: End-to-end identity field propagation and field-over-details precedence through the full EventBus → AuditService pipeline.
• Step implementations are clean, well-structured, and follow existing patterns.

Compliance

• ✅ Conventional Changelog commit format with ISSUES CLOSED: #715 footer
• ✅ No # type: ignore suppressions
• ✅ All imports at top of file
• ✅ All files well under 500 lines
• ✅ Type/Feature label, v3.5.0 milestone
• ✅ No needs feedback label
• ✅ Mergeable, no conflicts

APPROVED — no issues found.

## Independent Code Review — PR #1257 ### Summary Reviewed all 9 changed files (3 source, 4 Behave test files, 2 Robot test files) against the specification and project conventions. ### Source Code Review **`DomainEvent` (models.py)**: - `user_identity: str | None = Field(default=None)` — correctly typed, well-placed between `project_name` and `details`, fully documented in class docstring with spec reference (§Audit Logging). Backward compatible. **`AuditEventSubscriber` (audit_event_subscriber.py)**: - SEC-1 logic correctly updated: always pops `user_identity` from details dict to prevent duplication, then prefers `event.user_identity` over the popped value via `or` operator. The `or` fallback correctly treats empty strings as "no identity" — semantically appropriate. - Redaction via `redact_value()` applied to identity before persistence — good security practice. **`LoggingEventBus` (logging_bus.py)**: - Single-line addition of `user_identity=event.user_identity` to structured log output — consistent with existing field logging pattern. **`ReactiveEventBus` (reactive.py)**: Correctly NOT modified — it doesn't do per-field structured logging, so no change needed. ### Test Review - **8 Behave scenarios**: Field existence, default None, string acceptance, JSON round-trip, field-to-audit propagation, precedence over details, fallback from details, null case — comprehensive coverage of all code paths. - **2 Robot integration tests**: End-to-end identity field propagation and field-over-details precedence through the full EventBus → AuditService pipeline. - Step implementations are clean, well-structured, and follow existing patterns. ### Compliance - ✅ Conventional Changelog commit format with `ISSUES CLOSED: #715` footer - ✅ No `# type: ignore` suppressions - ✅ All imports at top of file - ✅ All files well under 500 lines - ✅ Type/Feature label, v3.5.0 milestone - ✅ No `needs feedback` label - ✅ Mergeable, no conflicts **APPROVED** — no issues found.

freemo referenced this pull request 2026-04-02 08:47:43 +00:00

feat(events): add user_identity field to DomainEvent and propagate through event pipeline #715

CoreRasurae force-pushed feature/domain-event-user-identity from b039b28309 to 6a31f376ac 2026-04-02 11:19:34 +00:00 Compare

CoreRasurae dismissed freemo's review 2026-04-02 11:19:35 +00:00

Reason:

New commits pushed, approval review dismissed automatically according to repository settings

CoreRasurae referenced this pull request 2026-04-02 11:20:34 +00:00

feat(events): add user_identity field to DomainEvent and propagate through event pipeline #715

freemo commented 2026-04-02 16:54:55 +00:00

Owner

Copy link

Review claimed by reviewer pool instance reviewer-pool-1. Dispatching independent code review.

Review claimed by reviewer pool instance reviewer-pool-1. Dispatching independent code review.

freemo approved these changes 2026-04-02 16:59:00 +00:00

freemo left a comment

Copy link

Independent Code Review — PR #1257 (reviewer-pool-1)

Summary

Reviewed all 9 changed files against the specification (§Audit Logging SEC7, §Event-Driven Architecture), CONTRIBUTING.md conventions, and project coding standards.

Source Code Review

DomainEvent (models.py):

• user_identity: str | None = Field(default=None, ...) — correctly typed, well-placed between project_name and details, fully documented in class docstring with spec reference. Backward compatible (defaults to None). Frozen model ensures immutability.

AuditEventSubscriber (audit_event_subscriber.py):

• SEC-1 logic correctly updated with explicit if/else branching:
  • When event.user_identity is not None: uses field value, pops from details to prevent duplication
  • When event.user_identity is None: falls back to raw_details.pop("user_identity", None) for backward compat
• This is cleaner than the previous or operator approach (from earlier revisions) because it correctly handles the case where event.user_identity is an empty string — the is None check is semantically precise.
• Redaction via redact_value() applied to identity before persistence — good security practice.

LoggingEventBus (logging_bus.py):

• Note: The emit() method does NOT include user_identity in its structured log output. This is a minor gap (non-blocking) — the critical audit path through AuditEventSubscriber correctly handles the field. A follow-up could add user_identity=event.user_identity to the _logger.info() call for completeness.

ReactiveEventBus (reactive.py): Correctly NOT modified — it doesn't do per-field structured logging.

Test Review

• 6 new Behave scenarios: Field existence, default None, string acceptance, JSON round-trip, field-to-audit propagation, precedence over details, fallback from details, null case — comprehensive coverage of all code paths.
• 3 new Robot integration tests: End-to-end identity field propagation, details fallback, and field-over-details precedence through the full EventBus → AuditService pipeline. The precedence test also verifies user_identity is stripped from details after field wins — thorough.
• Step implementations are clean, well-structured, and follow existing patterns.

Incidental Fix

• resource_cli_flags_904.feature: Changed expected string from "container types" to "container resource types" — fixes a pre-existing test mismatch. Verified this aligns with the actual error message.

Compliance Checklist

• ✅ Conventional Changelog commit format: feat(events): ... with ISSUES CLOSED: #715 footer
• ✅ No # type: ignore suppressions in new code
• ✅ All imports at top of file
• ✅ All files well under 500 lines
• ✅ Type/Feature label, v3.5.0 milestone
• ✅ Closes #715 in PR body
• ✅ No needs feedback label
• ✅ Mergeable, no conflicts
• ✅ Fully typed — all function signatures, variables, and return types annotated

Minor Non-Blocking Observation

LoggingEventBus.emit() does not include user_identity in its structured log output. Consider adding it in a follow-up for parity with the field set on DomainEvent.

APPROVED — merging via squash.

## Independent Code Review — PR #1257 (reviewer-pool-1) ### Summary Reviewed all 9 changed files against the specification (§Audit Logging SEC7, §Event-Driven Architecture), CONTRIBUTING.md conventions, and project coding standards. ### Source Code Review **`DomainEvent` (models.py)**: - `user_identity: str | None = Field(default=None, ...)` — correctly typed, well-placed between `project_name` and `details`, fully documented in class docstring with spec reference. Backward compatible (defaults to `None`). Frozen model ensures immutability. **`AuditEventSubscriber` (audit_event_subscriber.py)**: - SEC-1 logic correctly updated with explicit `if/else` branching: - When `event.user_identity is not None`: uses field value, pops from details to prevent duplication - When `event.user_identity is None`: falls back to `raw_details.pop("user_identity", None)` for backward compat - This is cleaner than the previous `or` operator approach (from earlier revisions) because it correctly handles the case where `event.user_identity` is an empty string — the `is None` check is semantically precise. - Redaction via `redact_value()` applied to identity before persistence — good security practice. **`LoggingEventBus` (logging_bus.py)**: - Note: The `emit()` method does NOT include `user_identity` in its structured log output. This is a minor gap (non-blocking) — the critical audit path through `AuditEventSubscriber` correctly handles the field. A follow-up could add `user_identity=event.user_identity` to the `_logger.info()` call for completeness. **`ReactiveEventBus` (reactive.py)**: Correctly NOT modified — it doesn't do per-field structured logging. ### Test Review - **6 new Behave scenarios**: Field existence, default None, string acceptance, JSON round-trip, field-to-audit propagation, precedence over details, fallback from details, null case — comprehensive coverage of all code paths. - **3 new Robot integration tests**: End-to-end identity field propagation, details fallback, and field-over-details precedence through the full EventBus → AuditService pipeline. The precedence test also verifies `user_identity` is stripped from details after field wins — thorough. - Step implementations are clean, well-structured, and follow existing patterns. ### Incidental Fix - `resource_cli_flags_904.feature`: Changed expected string from "container types" to "container resource types" — fixes a pre-existing test mismatch. Verified this aligns with the actual error message. ### Compliance Checklist - ✅ Conventional Changelog commit format: `feat(events): ...` with `ISSUES CLOSED: #715` footer - ✅ No `# type: ignore` suppressions in new code - ✅ All imports at top of file - ✅ All files well under 500 lines - ✅ Type/Feature label, v3.5.0 milestone - ✅ `Closes #715` in PR body - ✅ No `needs feedback` label - ✅ Mergeable, no conflicts - ✅ Fully typed — all function signatures, variables, and return types annotated ### Minor Non-Blocking Observation `LoggingEventBus.emit()` does not include `user_identity` in its structured log output. Consider adding it in a follow-up for parity with the field set on `DomainEvent`. **APPROVED** — merging via squash.

freemo merged commit e3d3c7926d into master 2026-04-02 16:59:08 +00:00

freemo deleted branch feature/domain-event-user-identity 2026-04-02 16:59:09 +00:00

freemo referenced this pull request from a commit 2026-04-02 16:59:10 +00:00

feat(events): add user_identity field to DomainEvent and propagate through event pipeline (#1257)

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

feat(events): add user_identity field to DomainEvent and propagate through event pipeline #715

freemo referenced this pull request 2026-04-02 17:11:30 +00:00

[Automated] Product Build Session State #1314

freemo referenced this pull request from a commit 2026-04-02 17:34:11 +00:00

docs(spec): align spec with v3.7.0 cycle-3 implementation discoveries

freemo referenced this pull request 2026-04-02 17:34:51 +00:00

[Automated] Product Build Session State #1393

freemo referenced this pull request 2026-04-02 17:44:47 +00:00

fix(audit): forward DomainEvent.timestamp to AuditService.record() #1258

freemo referenced this pull request 2026-04-02 18:18:43 +00:00

fix(audit): forward DomainEvent.timestamp to AuditService.record() #1258

freemo referenced this pull request 2026-04-02 18:18:49 +00:00

fix(audit): forward DomainEvent.timestamp to AuditService.record() to preserve original event time #719

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

fix(audit): forward DomainEvent.timestamp to AuditService.record() to preserve original event time #719

freemo referenced this pull request 2026-04-02 19:45:34 +00:00

fix(audit): forward DomainEvent.timestamp to AuditService.record() to preserve original event time #719

freemo referenced this pull request 2026-04-03 01:09:33 +00:00

fix(audit): forward DomainEvent.timestamp to AuditService.record() to preserve original event time #719

freemo referenced this pull request 2026-04-03 01:09:36 +00:00

fix(audit): forward DomainEvent.timestamp to AuditService.record() #1258

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

fix(audit): forward DomainEvent.timestamp to AuditService.record() to preserve original event time #719

freemo referenced this pull request 2026-04-03 03:52:36 +00:00

fix(audit): forward DomainEvent.timestamp to AuditService.record() to preserve original event time #719

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

fix(audit): forward DomainEvent.timestamp to AuditService.record() to preserve original event time #719

freemo referenced this pull request 2026-04-05 07:53:55 +00:00

fix(audit): forward DomainEvent.timestamp to AuditService.record() to preserve original event time #719

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.

  

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.5.0

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

freemo

3 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.

Blocks

#715 feat(events): add user_identity field to DomainEvent and propagate through event pipeline

cleveragents/cleveragents-core

Reference

cleveragents/cleveragents-core!1257

No description provided.