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

fix(events): add close() method to ReactiveEventBus to complete RxPY subject #11190

Open
freemo wants to merge 2 commits from PR-fix-wf18 into master
pull from: PR-fix-wf18
merge into: cleveragents:master
Conversation 2 Commits 2 Files changed 2 +132 -13
freemo commented 2026-05-13 05:58:50 +00:00
Owner
Copy link

Fix for issue #10378: ReactiveEventBus._subject (RxPY Subject) is never completed — missing close() method causes RxPY subscriber resource leaks.

Changes:

  • Add _closed flag to track bus shutdown state
  • Prevent emit() after close() with clear RuntimeError
  • Make close() idempotent (safe to call multiple times)
  • Add context manager protocol (__enter__/__exit__) for resource cleanup

Fixes #10378

Fix for issue #10378: ReactiveEventBus._subject (RxPY Subject) is never completed — missing close() method causes RxPY subscriber resource leaks. Changes: - Add `_closed` flag to track bus shutdown state - Prevent `emit()` after `close()` with clear RuntimeError - Make `close()` idempotent (safe to call multiple times) - Add context manager protocol (`__enter__`/`__exit__`) for resource cleanup Fixes #10378
feat(agents): add mandatory PR compliance checklist to implementation-pool-supervisor
Some checks failed
CI / build (pull_request) Successful in 1m12s
Details
CI / lint (pull_request) Successful in 1m25s
Details
CI / helm (pull_request) Successful in 1m12s
Details
CI / quality (pull_request) Successful in 1m35s
Details
CI / typecheck (pull_request) Successful in 1m51s
Details
CI / security (pull_request) Successful in 1m54s
Details
CI / push-validation (pull_request) Successful in 21s
Details
CI / integration_tests (pull_request) Successful in 5m12s
Details
CI / unit_tests (pull_request) Successful in 5m43s
Details
CI / coverage (pull_request) Failing after 1m34s
Details
CI / docker (pull_request) Successful in 2m45s
Details
CI / status-check (pull_request) Failing after 4s
Details
3777eb749e 
Add CHANGELOG.md and CONTRIBUTORS.md entries for the Implementation Pool
Supervisor PR Compliance Checklist feature. This ensures all 8 checklist
items are properly documented before workers create PRs.

ISSUES CLOSED: #11015
fix(events): add close() method to ReactiveEventBus to complete RxPY subject
Some checks failed
CI / helm (pull_request) Successful in 48s
Details
CI / lint (pull_request) Failing after 1m22s
Details
CI / quality (pull_request) Successful in 1m27s
Details
CI / build (pull_request) Successful in 1m17s
Details
CI / push-validation (pull_request) Successful in 1m3s
Details
CI / typecheck (pull_request) Successful in 1m53s
Details
CI / security (pull_request) Successful in 1m56s
Details
CI / integration_tests (pull_request) Successful in 4m4s
Details
CI / unit_tests (pull_request) Successful in 5m15s
Details
CI / docker (pull_request) Has been skipped
Details
CI / coverage (pull_request) Has been skipped
Details
CI / status-check (pull_request) Failing after 3s
Details
0f967e04e2 
- Add _closed flag to track bus shutdown state
- Prevent emit() after close() with clear RuntimeError
- Make close() idempotent (safe to call multiple times)
- Add context manager protocol (__enter__/__exit__) for resource cleanup

Fixes issue #10378: missing close() method causes RxPY subscriber leaks
freemo added this to the v3.2.0 milestone 2026-05-13 06:03:48 +00:00
HAL9001 requested changes 2026-05-14 00:22:41 +00:00
HAL9001 left a comment
Copy link

Review Summary

This PR addresses issue #10378 and the underlying fix in ReactiveEventBus is correct and well-designed. The close() method, _closed flag, idempotency guard, RuntimeError on post-close emit(), and the context manager protocol (__enter__/__exit__) are all implemented correctly and match the acceptance criteria.

However, there are several blocking issues that must be resolved before this PR can be approved and merged:

Blocking Issues

  1. CI lint gate is FAILING — CI / lint failed (1m22s, failing). Per company policy, all required CI gates must be green before merge. The lint failure also causes CI / coverage to be skipped, so coverage compliance cannot be confirmed.

  2. Non-atomic commit history — The PR contains two commits related to this fix:

    • 3459f821 — the main fix, which accidentally removes exc_info=True from the event_handler_failed logging block
    • 4099872a — a follow-up commit immediately restoring exc_info=True
      Per CONTRIBUTING.md, each commit must be atomic and independently correct. A commit that introduces a regression, immediately followed by a fixup commit, is not acceptable in merged history. These must be squashed (via interactive rebase) into a single, clean commit before merge.

  3. Branch name does not follow conventions — The PR head branch is PR-fix-wf18. CONTRIBUTING.md requires bug fix branches to follow bugfix/mN-<descriptive-name> format (e.g. bugfix/m2-reactive-event-bus-close). Additionally, the branch does not match the Branch: field in the issue #10378 Metadata section (fix/reactive-event-bus-close-method), which is also non-conforming.

  4. PR is stale with merge conflicts — The PR is marked as stale with conflicts against master and cannot be merged. The branch must be rebased onto the current master before this PR can land.

  5. Coverage check is skipped — Due to the lint failure, CI / coverage was skipped. Coverage compliance (≥97%) cannot be confirmed until lint passes and coverage runs to completion.

Likely Root Cause of Lint Failure

In features/steps/event_bus_steps.py, the new step @given("a ReactiveEventBus used as a context manager") assigns ctx.cm_bus but the variable is never subsequently read in any step. This is likely triggering a ruff "assigned but never used" or similar warning/error. Fix: either remove the ctx.cm_bus assignment entirely (the with ctx.bus as bus: block is sufficient to exercise __enter__), or use it in the @then step.

Code Quality

Aside from the blocking issues above, the code quality is good:

  • reactive.py implementation is correct, clean, well-documented, and type-annotated
  • BDD scenarios in event_bus.feature and tdd_reactive_event_bus_close.feature cover all acceptance criteria
  • tdd_reactive_event_bus_close_steps.py is thorough and uses proper Behave idioms
  • The @tdd_issue_10377 tag is correctly applied per the TDD bug fix workflow
  • __exit__ is correctly typed with TracebackType from types
  • All public methods have docstrings

Required Actions Before Re-Review

  1. Fix the lint issue (likely ctx.cm_bus unused variable in event_bus_steps.py)
  2. Squash the two events-related commits into one clean atomic commit
  3. Rebase the branch onto current master (resolve all conflicts)
  4. Ensure nox passes locally (all sessions green, coverage ≥97%)
  5. Rename the branch to follow bugfix/m2-reactive-event-bus-close convention

Automated by CleverAgents Bot
Supervisor: PR Review | Agent: pr-review-worker

## Review Summary This PR addresses issue #10378 and the underlying fix in `ReactiveEventBus` is **correct and well-designed**. The `close()` method, `_closed` flag, idempotency guard, `RuntimeError` on post-close `emit()`, and the context manager protocol (`__enter__`/`__exit__`) are all implemented correctly and match the acceptance criteria. However, there are several **blocking issues** that must be resolved before this PR can be approved and merged: ### Blocking Issues 1. **CI lint gate is FAILING** — `CI / lint` failed (1m22s, failing). Per company policy, all required CI gates must be green before merge. The lint failure also causes `CI / coverage` to be skipped, so coverage compliance cannot be confirmed. 2. **Non-atomic commit history** — The PR contains two commits related to this fix: - `3459f821` — the main fix, which accidentally removes `exc_info=True` from the `event_handler_failed` logging block - `4099872a` — a follow-up commit immediately restoring `exc_info=True` Per CONTRIBUTING.md, each commit must be atomic and independently correct. A commit that introduces a regression, immediately followed by a fixup commit, is not acceptable in merged history. These must be squashed (via interactive rebase) into a single, clean commit before merge. 3. **Branch name does not follow conventions** — The PR head branch is `PR-fix-wf18`. CONTRIBUTING.md requires bug fix branches to follow `bugfix/mN-<descriptive-name>` format (e.g. `bugfix/m2-reactive-event-bus-close`). Additionally, the branch does not match the `Branch:` field in the issue #10378 Metadata section (`fix/reactive-event-bus-close-method`), which is also non-conforming. 4. **PR is stale with merge conflicts** — The PR is marked as stale with conflicts against master and cannot be merged. The branch must be rebased onto the current master before this PR can land. 5. **Coverage check is skipped** — Due to the lint failure, `CI / coverage` was skipped. Coverage compliance (≥97%) cannot be confirmed until lint passes and coverage runs to completion. ### Likely Root Cause of Lint Failure In `features/steps/event_bus_steps.py`, the new step `@given("a ReactiveEventBus used as a context manager")` assigns `ctx.cm_bus` but the variable is never subsequently read in any step. This is likely triggering a ruff "assigned but never used" or similar warning/error. Fix: either remove the `ctx.cm_bus` assignment entirely (the `with ctx.bus as bus:` block is sufficient to exercise `__enter__`), or use it in the `@then` step. ### Code Quality Aside from the blocking issues above, the code quality is good: - `reactive.py` implementation is correct, clean, well-documented, and type-annotated - BDD scenarios in `event_bus.feature` and `tdd_reactive_event_bus_close.feature` cover all acceptance criteria - `tdd_reactive_event_bus_close_steps.py` is thorough and uses proper Behave idioms - The `@tdd_issue_10377` tag is correctly applied per the TDD bug fix workflow - `__exit__` is correctly typed with `TracebackType` from `types` - All public methods have docstrings ### Required Actions Before Re-Review 1. Fix the lint issue (likely `ctx.cm_bus` unused variable in `event_bus_steps.py`) 2. Squash the two events-related commits into one clean atomic commit 3. Rebase the branch onto current master (resolve all conflicts) 4. Ensure `nox` passes locally (all sessions green, coverage ≥97%) 5. Rename the branch to follow `bugfix/m2-reactive-event-bus-close` convention --- Automated by CleverAgents Bot Supervisor: PR Review | Agent: pr-review-worker
features/steps/event_bus_steps.py
HAL9001 commented 2026-05-14 00:22:40 +00:00
Owner
Copy link

BLOCKING — Likely lint failure root cause

ctx.cm_bus is assigned on this line (and updated inside the with block on the next line) but is never read in any subsequent @then step. ruff will flag this as an unused variable assignment, which is likely why CI / lint is failing.

How to fix: Remove the ctx.cm_bus assignment entirely. The with ctx.bus as bus: block is sufficient to exercise __enter__ — you do not need to capture the returned value since the @then("the bus should be closed after the context exits") step only checks ctx.bus._closed, not ctx.cm_bus.

@given("a ReactiveEventBus used as a context manager")
def step_given_bus_context_manager(ctx: Context) -> None:
    ctx.bus = ReactiveEventBus()
    with ctx.bus:  # __enter__ is exercised; no need to capture return value
        pass

Automated by CleverAgents Bot
Supervisor: PR Review | Agent: pr-review-worker

**BLOCKING — Likely lint failure root cause** `ctx.cm_bus` is assigned on this line (and updated inside the `with` block on the next line) but is never read in any subsequent `@then` step. ruff will flag this as an unused variable assignment, which is likely why `CI / lint` is failing. **How to fix:** Remove the `ctx.cm_bus` assignment entirely. The `with ctx.bus as bus:` block is sufficient to exercise `__enter__` — you do not need to capture the returned value since the `@then("the bus should be closed after the context exits")` step only checks `ctx.bus._closed`, not `ctx.cm_bus`. ```python @given("a ReactiveEventBus used as a context manager") def step_given_bus_context_manager(ctx: Context) -> None: ctx.bus = ReactiveEventBus() with ctx.bus: # __enter__ is exercised; no need to capture return value pass ``` --- Automated by CleverAgents Bot Supervisor: PR Review | Agent: pr-review-worker
src/cleveragents/infrastructure/events/reactive.py
HAL9001 commented 2026-05-14 00:22:41 +00:00
Owner
Copy link

BLOCKING — Accidental removal of exc_info=True in this commit

This commit (3459f821) removes exc_info=True from the event_handler_failed logger call. A follow-up commit (4099872a) immediately restores it, citing that "The exc_info=True parameter was accidentally removed from the event_handler_failed logging block during a previous formatting cleanup."

Per CONTRIBUTING.md, commits must be atomic — each commit must be independently correct and not introduce a regression that is then immediately fixed by the very next commit. This two-commit sequence must be squashed into a single clean commit via interactive rebase (git rebase -i HEAD~2) before the PR can be approved.

The final state of the file is correct — exc_info=True is present at HEAD. This is not a code quality issue in the resulting code, only a commit hygiene issue.

Automated by CleverAgents Bot
Supervisor: PR Review | Agent: pr-review-worker

**BLOCKING — Accidental removal of `exc_info=True` in this commit** This commit (`3459f821`) removes `exc_info=True` from the `event_handler_failed` logger call. A follow-up commit (`4099872a`) immediately restores it, citing that "The exc_info=True parameter was accidentally removed from the event_handler_failed logging block during a previous formatting cleanup." Per CONTRIBUTING.md, commits must be **atomic** — each commit must be independently correct and not introduce a regression that is then immediately fixed by the very next commit. This two-commit sequence must be squashed into a single clean commit via interactive rebase (`git rebase -i HEAD~2`) before the PR can be approved. The final state of the file is correct — `exc_info=True` is present at HEAD. This is not a code quality issue in the resulting code, only a commit hygiene issue. --- Automated by CleverAgents Bot Supervisor: PR Review | Agent: pr-review-worker
HAL9001 commented 2026-05-14 00:22:55 +00:00
Owner
Copy link

Peer review completed. Formal review submitted with REQUEST_CHANGES status (review ID 8749).

This PR addresses a real and important bug — the ReactiveEventBus fix itself is correct. However, there are 5 blocking issues that must be resolved before approval:

  1. CI / lint is failing — likely caused by an unused ctx.cm_bus variable in event_bus_steps.py
  2. Coverage check is skipped (blocked by lint failure) — cannot confirm ≥97%
  3. Non-atomic commits — exc_info=True was accidentally removed in commit 3459f821 and restored in 4099872a; these must be squashed
  4. Branch name PR-fix-wf18 does not follow bugfix/mN-<name> convention
  5. Stale with merge conflicts — branch must be rebased onto current master

See the inline review comments for specific fix guidance.

Automated by CleverAgents Bot
Supervisor: PR Review | Agent: pr-review-worker

Peer review completed. Formal review submitted with **REQUEST_CHANGES** status (review ID 8749). This PR addresses a real and important bug — the `ReactiveEventBus` fix itself is correct. However, there are 5 blocking issues that must be resolved before approval: 1. **CI / lint is failing** — likely caused by an unused `ctx.cm_bus` variable in `event_bus_steps.py` 2. **Coverage check is skipped** (blocked by lint failure) — cannot confirm ≥97% 3. **Non-atomic commits** — `exc_info=True` was accidentally removed in commit `3459f821` and restored in `4099872a`; these must be squashed 4. **Branch name** `PR-fix-wf18` does not follow `bugfix/mN-<name>` convention 5. **Stale with merge conflicts** — branch must be rebased onto current master See the inline review comments for specific fix guidance. --- Automated by CleverAgents Bot Supervisor: PR Review | Agent: pr-review-worker
Some checks failed
CI / helm (pull_request) Successful in 48s
Details
CI / lint (pull_request) Failing after 1m22s
Required
Details
CI / quality (pull_request) Successful in 1m27s
Required
Details
CI / build (pull_request) Successful in 1m17s
Required
Details
CI / push-validation (pull_request) Successful in 1m3s
Details
CI / typecheck (pull_request) Successful in 1m53s
Required
Details
CI / security (pull_request) Successful in 1m56s
Required
Details
CI / integration_tests (pull_request) Successful in 4m4s
Required
Details
CI / unit_tests (pull_request) Successful in 5m15s
Required
Details
CI / docker (pull_request) Has been skipped
Required
Details
CI / coverage (pull_request) Has been skipped
Required
Details
CI / status-check (pull_request) Failing after 3s
Details
This pull request has changes conflicting with the target branch.
  • src/cleveragents/infrastructure/events/reactive.py
View command line instructions

Manual merge helper

Use this merge commit message when completing the merge manually.

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin PR-fix-wf18:PR-fix-wf18
git switch PR-fix-wf18
Sign in to join this conversation.
Reviewers
No reviewers
HAL9001
Labels
Clear labels   
auto/needs-reevaluation
Controller deferred this PR; awaiting Phase 6+ scope-evaluator or operator re-enablement.

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

  
auto/blocked-by-deps
PR blocked by an open issue dependency. Operator must close the dep (or remove the dependency link) before the merge driver can act. Auto-cleared by merge_drive when no open deps remain.

  
auto/ci-timeout
Most recent merge cycle hit CI timeout. Driver excludes this PR while last merge_cycle row is < 30 min old; label persists thereafter as visible history.

  
auto/claimed-implementer
Currently being processed by an implementer worker.

  
auto/claimed-merge
Currently being processed by the merge driver.

  
auto/claimed-reviewer
Currently being processed by a reviewer worker.

  
auto/driver-down
Merge driver heartbeat stale; pipeline halted. Closed automatically on next clean tick.

  
auto/invariant-violation
Detected master commit violating the strict merge invariant. Tracked as an issue (not a PR label); kept here for label completeness.

  
auto/last-attempt-tier-0
In-cycle escalation: most recent attempt ran at the Tier 0 slot (`tier-0`). Slot's model defined in .opencode/models/tiers.yaml.

  
auto/last-attempt-tier-1
In-cycle escalation: most recent attempt ran at the Tier 1 slot (`tier-1`). Slot's model defined in .opencode/models/tiers.yaml.

  
auto/last-attempt-tier-2
In-cycle escalation: most recent attempt ran at the Tier 2 slot (`tier-2`). Slot's model defined in .opencode/models/tiers.yaml. Gated behind IMPLEMENTER_ESCALATION_TIER2_ENABLED.

  
auto/last-attempt-tier-min
In-cycle escalation: most recent attempt ran at the Tier -1 slot (`tier-min`). Slot's model defined in .opencode/models/tiers.yaml. Suffix is ``-min`` (not ``--1``) so the Forgejo UI reads naturally.

  
Automation Tracking
Tracking issues used by the AI Automation system for agents to communicate and report.

  
auto/needs-conflict-resolution
Rebase conflict needs LLM conflict-resolver.

  
auto/needs-implementer
Failing CI needs implementer attention.

  
auto/postmortem
Documenting a driver incident or rollback.

  
auto/ready-to-merge
Reviewer has APPROVED this PR and no later REQUEST_CHANGES is outstanding. The merge driver requires this label to even consider a PR for merging. Set by the reviewer worker on APPROVE; cleared on REQUEST_CHANGES.

  
auto/restart-throttled
Train repeatedly lost master-tempo races. Driver excludes via merge_cycle until cooldown elapses; label persists as visible history.

  
auto/revert
Revert PR backing out an invariant violation. Fast-tracked through the merge driver.

  
auto/sentinel
Sentinel PR duplicated from upstream into a personal fork by tools/duplicate_prs_to_fork.py for pipeline testing. Lives only in the fork; the canonical pipeline never sees it.

  
auto/stale-inactivity
No implementer activity for N days. Flagged for human review. Auto-cleared on next push to head branch.

  
auto/unstable
Repeatedly fails on current master (>= 3 ci-fail-on-rebased-sha releases in 12 h). Excluded from driver until human triage.

  
Blocked
A ticket in a blocked state and unable to complete until some other task is completed first.

  
Bounty
$100
 A bounty of $100 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$1000
 A bounty of $1000 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$10000
 A bounty of $10000 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$20
 A bounty of $20 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$2000
 A bounty of $2000 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$250
 A bounty of $250 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$50
 A bounty of $50 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$500
 A bounty of $500 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$5000
 A bounty of $5000 for any open-source contributor who provides a MR that solves this issue

  
Bounty
$750
 A bounty of $750 for any open-source contributor who provides a MR that solves this issue

  
MoSCoW
Could have
 Could have feature in order to satisfy the epic/legendary.

  
MoSCoW
Must have
 Must have feature in order to satisfy the epic/legendary.

  
MoSCoW
Should have
 Should have feature in order to satisfy the epic/legendary.

  
Needs Feedback
There are questions in the ticket that can not be completed until the project owner provides clarity.

  
Points
1
 1 man-hours worth of work for an expert with no learning curve.

  
Points
13
 13 man-hours worth of work for an expert with no learning curve.

  
Points
2
 2 man-hours worth of work for an expert with no learning curve.

  
Points
21
 21 man-hours worth of work for an expert with no learning curve.

  
Points
3
 3 man-hours worth of work for an expert with no learning curve.

  
Points
34
 34 man-hours worth of work for an expert with no learning curve.

  
Points
5
 5 man-hours worth of work for an expert with no learning curve.

  
Points
55
 55 man-hours worth of work for an expert with no learning curve.

  
Points
8
 8 man-hours worth of work for an expert with no learning curve.

  
Points
88
 88 man-hours worth of work for an expert with no learning curve.

  
Priority
Backlog
 This ticket has backlogged priority and is not to be worked on yet

  
Priority
CI Blocker
 Critical priority issue that blocks CI/CD pipeline and prevents PR merges

  
Priority
Critical
 The priority is critical

  
Priority
High
 The priority is high

  
Priority
Low
 The priority is low

  
Priority
Medium
 The priority is medium

  
Signed-off: Owner
When an epic or legendary is in review it must be signed off by owner, tech lead, and scrum master before being marked as completed.

  
Signed-off: Scrum Master
When an epic or legendary is in review it must be signed off by owner, tech lead, and scrum master before being marked as completed.

  
Signed-off: Tech Lead
When an epic or legendary is in review it must be signed off by owner, tech lead, and scrum master before being marked as completed.

  
Spike
A ticket for learning a tool or technology that is needed to be able to do future planning and design.

  
State
Completed
 The ticket has been fully implemented, completed, and merged with the source code. This label should only be applied once a ticket is closed.

  
State
Duplicate
 A ticket that represents the same content as an existing ticket.

  
State
In Progress
 A ticket that is actively being developed.

  
State
In Review
 A ticket that has had some code completed to implement but is waiting to pass peer review and is not yet merged in.

  
State
Paused
 This ticket's work started but wasn't finished. It's on hold (likely in a feature branch) and will be resumed later, either due to a blocker or a delay.

  
State
Unverified
 All new tickets start in this state. A developer may set it to show the ticket is unverified. This means we haven't agreed to work on it. It will either move to a verified state or be closed as wontdo.

  
State
Verified
 The issue has been verified by a developer as legitimate. It will be worked on and verified tickets are now considered part of the backlog.

  
State
Wont Do
 This ticket has been decided it wont be done. This may mean the bug has been determined to not be real (cant verify) or the feature is one we have decided we dont want to adopt.

  
Type
Automation
 Any edits or discussion about the AI automated coding system.

  
Type
Bug
 Something that doesnt work as intended.

  
Type
Discussion
 Anytime a ticket represents a discussion about a subject and doesnt fall into one of the other categories.

  
Type
Documentation
 An error or improvement needed in the documentation.

  
Type
Epic
 Any first tier epic. That is, an epic which contains only issues as children and will not have sub-epics.

  
Type
Feature
 Some new functionality not present.

  
Type
Legendary
 A type of Epic which will contain other Epics.

  
Type
Refactor
 A code change that restructures existing code without changing its external behavior.

  
Type
Support
 Someone needs help using the project.

  
Type
Task
 A generic task that doesnt fit into the other type categories.

  
Type
Testing
 Work exclusively focusing on fixing or expanding testing.

No labels
auto/needs-reevaluation
controller-managed
auto/blocked-by-deps
auto/ci-timeout
auto/claimed-implementer
auto/claimed-merge
auto/claimed-reviewer
auto/driver-down
auto/invariant-violation
auto/last-attempt-tier-0
auto/last-attempt-tier-1
auto/last-attempt-tier-2
auto/last-attempt-tier-min
Automation Tracking
auto/needs-conflict-resolution
auto/needs-implementer
auto/postmortem
auto/ready-to-merge
auto/restart-throttled
auto/revert
auto/sentinel
auto/stale-inactivity
auto/unstable
Blocked
Bounty
$100
Bounty
$1000
Bounty
$10000
Bounty
$20
Bounty
$2000
Bounty
$250
Bounty
$50
Bounty
$500
Bounty
$5000
Bounty
$750
MoSCoW
Could have
MoSCoW
Must have
MoSCoW
Should have
Needs Feedback
Points
1
Points
13
Points
2
Points
21
Points
3
Points
34
Points
5
Points
55
Points
8
Points
88
Priority
Backlog
Priority
CI Blocker
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Signed-off: Owner
Signed-off: Scrum Master
Signed-off: Tech Lead
Spike
State
Completed
State
Duplicate
State
In Progress
State
In Review
State
Paused
State
Unverified
State
Verified
State
Wont Do
Type
Automation
Type
Bug
Type
Discussion
Type
Documentation
Type
Epic
Type
Feature
Type
Legendary
Type
Refactor
Type
Support
Type
Task
Type
Testing
Milestone
Clear milestone
No items
No milestone
v3.2.0
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
cleveragents/cleveragents-core!11190
No description provided.