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

feat(tui): implement prompt history (dual JSONL) #1252

Closed
brent.edwards wants to merge 1 commit from feature/m8-tui-prompt-history into master
pull from: feature/m8-tui-prompt-history
merge into: cleveragents:master
Conversation 6 Commits 1 Files changed 9 +429 -4
brent.edwards commented 2026-04-01 23:01:32 +00:00
Member
Copy link
No description provided.
feat(tui): implement prompt history (dual JSONL)
All checks were successful
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / build (pull_request) Successful in 18s
Details
CI / helm (pull_request) Successful in 22s
Details
CI / typecheck (pull_request) Successful in 51s
Details
CI / security (pull_request) Successful in 1m1s
Details
CI / lint (pull_request) Successful in 3m22s
Details
CI / quality (pull_request) Successful in 3m43s
Details
CI / unit_tests (pull_request) Successful in 6m44s
Details
CI / docker (pull_request) Successful in 1m41s
Details
CI / coverage (pull_request) Successful in 12m13s
Details
CI / e2e_tests (pull_request) Successful in 17m13s
Details
CI / integration_tests (pull_request) Successful in 22m46s
Details
CI / status-check (pull_request) Successful in 1s
Details
CI / benchmark-regression (pull_request) Successful in 55m5s
Details
8136435371 
Add per-project prompt and shell history persistence in dual JSONL files, plus prompt navigation helpers and app-level up/down history actions.

Extend Behave and Robot coverage for history storage, pruning, independent shell history, and prompt-history navigation.

ISSUES CLOSED: #1014
brent.edwards force-pushed feature/m8-tui-prompt-history from 8136435371
All checks were successful
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / build (pull_request) Successful in 18s
Details
CI / helm (pull_request) Successful in 22s
Details
CI / typecheck (pull_request) Successful in 51s
Details
CI / security (pull_request) Successful in 1m1s
Details
CI / lint (pull_request) Successful in 3m22s
Details
CI / quality (pull_request) Successful in 3m43s
Details
CI / unit_tests (pull_request) Successful in 6m44s
Details
CI / docker (pull_request) Successful in 1m41s
Details
CI / coverage (pull_request) Successful in 12m13s
Details
CI / e2e_tests (pull_request) Successful in 17m13s
Details
CI / integration_tests (pull_request) Successful in 22m46s
Details
CI / status-check (pull_request) Successful in 1s
Details
CI / benchmark-regression (pull_request) Successful in 55m5s
Details
to 26d06fc183
All checks were successful
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / helm (pull_request) Successful in 21s
Details
CI / build (pull_request) Successful in 23s
Details
CI / quality (pull_request) Successful in 1m2s
Details
CI / lint (pull_request) Successful in 3m18s
Details
CI / typecheck (pull_request) Successful in 3m56s
Details
CI / security (pull_request) Successful in 4m11s
Details
CI / unit_tests (pull_request) Successful in 9m12s
Details
CI / docker (pull_request) Successful in 1m35s
Details
CI / coverage (pull_request) Successful in 12m13s
Details
CI / e2e_tests (pull_request) Successful in 20m5s
Details
CI / integration_tests (pull_request) Successful in 24m45s
Details
CI / status-check (pull_request) Successful in 1s
Details
CI / benchmark-regression (pull_request) Successful in 55m39s
Details
2026-04-02 00:15:43 +00:00 Compare
brent.edwards added this to the v3.8.0 milestone 2026-04-02 00:15:59 +00:00
freemo self-assigned this 2026-04-02 08:06:14 +00:00
freemo commented 2026-04-02 08:11:27 +00:00
Owner
Copy link

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

🔒 Claimed by pr-reviewer-5. Starting independent code review.
freemo commented 2026-04-02 08:13:20 +00:00
Owner
Copy link

⚠️ Merge Conflict Detected — PR #1252 cannot be merged until conflicts are resolved by the implementing agent.

This PR (feature/m8-tui-prompt-history) has merge conflicts with master. Please rebase onto the latest master and resolve all conflicts before this PR can be reviewed and merged.

⚠️ **Merge Conflict Detected** — PR #1252 cannot be merged until conflicts are resolved by the implementing agent. This PR (`feature/m8-tui-prompt-history`) has merge conflicts with `master`. Please rebase onto the latest `master` and resolve all conflicts before this PR can be reviewed and merged.
freemo commented 2026-04-02 16:54:54 +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 requested changes 2026-04-02 16:58:51 +00:00
freemo left a comment
Copy link

Independent Code Review — PR #1252

Reviewer: reviewer-pool-1 (independent self-review)
PR: feat(tui): implement prompt history (dual JSONL)
Branch: feature/m8-tui-prompt-history → master
Linked Issue: #1014
Commit: 26d06fc (single commit, well-formed Conventional Changelog)

🚫 BLOCKING: Merge Conflicts

The PR is marked mergeable: false — it has merge conflicts with master. This must be resolved before the PR can be merged. Please rebase onto the latest master and resolve all conflicts.

🚫 BLOCKING: Empty PR Description

The PR body is empty (""). Per CONTRIBUTING.md, every PR must have a detailed description that:

  • Summarizes the changes
  • Explains the motivation
  • Includes a closing keyword (e.g., Closes #1014)

The commit message is well-formed and includes ISSUES CLOSED: #1014, but the PR body itself must also contain this information.

✅ Code Quality Assessment (for when blockers are resolved)

The implementation is well-structured and high quality. Here's my detailed assessment:

Specification Alignment ✅

  • Dual JSONL history files (prompt + shell) align with the TUI specification's per-project persistence model
  • History stored at ~/.local/state/cleveragents/history/ follows the XDG state directory convention used elsewhere in the project
  • Per-project isolation via SHA-256 hash of project key is a sound approach

Architecture & Design ✅

  • PromptHistoryManager (125 lines) — Clean dataclass with slots=True, proper separation of concerns
  • PromptInput extensions — History methods delegate cleanly to the manager
  • App-level wiring — Key bindings (up/down) and action_history_* methods follow existing patterns (action_help, action_cycle_preset)
  • Optional dependency injection (prompt_history: PromptHistoryManager | None = None) is the right pattern

Type Safety ✅

  • All functions have explicit type annotations
  • shell_mode: bool is keyword-only throughout — prevents positional argument confusion
  • Union types (PromptHistoryManager | None) used correctly
  • Return types specified on all public methods

Test Quality ✅

  • 4 Behave BDD scenarios covering: separate file storage, pruning, navigation with draft restoration, independent shell history
  • 2 new app-level scenarios for action_history_previous and action_history_next
  • 1 Robot integration test for end-to-end prompt history persistence
  • Tests use proper cleanup (add_cleanup, shutil.rmtree)
  • Step definitions are well-structured with helper factories

Correctness ✅

  • Navigation cursor logic correctly handles: first press (save draft, jump to end), subsequent presses (decrement), forward navigation, and draft restoration
  • Pruning correctly keeps the most recent max_entries entries
  • JSONL format with json.dumps(ensure_ascii=True) prevents encoding issues
  • Graceful handling of corrupt JSONL lines (skip on JSONDecodeError)

Minor Observations (non-blocking)

  1. _read_entries() re-reads the file on every previous()/next() call — acceptable for TUI use case but could be cached if performance becomes an issue
  2. Global up/down key bindings — These may conflict with other widgets that use arrow keys (e.g., list navigation). Consider scoping to the prompt input widget focus. This is a design choice that may need revisiting as the TUI grows.
  3. No deduplication — Consecutive identical entries are stored separately. Most shell histories deduplicate adjacent duplicates. Consider adding this.

Summary

Decision: REQUEST_CHANGES — Two blockers must be resolved:

  1. Rebase onto latest master to resolve merge conflicts
  2. Add a PR description with closing keyword Closes #1014, change summary, and validation results

Once these are addressed, the code is ready to merge. The implementation is clean, well-typed, well-tested, and follows project conventions.

## Independent Code Review — PR #1252 **Reviewer**: reviewer-pool-1 (independent self-review) **PR**: `feat(tui): implement prompt history (dual JSONL)` **Branch**: `feature/m8-tui-prompt-history` → `master` **Linked Issue**: #1014 **Commit**: `26d06fc` (single commit, well-formed Conventional Changelog) --- ### 🚫 BLOCKING: Merge Conflicts The PR is marked `mergeable: false` — it has merge conflicts with `master`. This must be resolved before the PR can be merged. Please **rebase onto the latest `master`** and resolve all conflicts. ### 🚫 BLOCKING: Empty PR Description The PR body is empty (`""`). Per CONTRIBUTING.md, every PR must have a detailed description that: - Summarizes the changes - Explains the motivation - Includes a closing keyword (e.g., `Closes #1014`) The commit message is well-formed and includes `ISSUES CLOSED: #1014`, but the PR body itself must also contain this information. --- ### ✅ Code Quality Assessment (for when blockers are resolved) The implementation is **well-structured and high quality**. Here's my detailed assessment: #### Specification Alignment ✅ - Dual JSONL history files (prompt + shell) align with the TUI specification's per-project persistence model - History stored at `~/.local/state/cleveragents/history/` follows the XDG state directory convention used elsewhere in the project - Per-project isolation via SHA-256 hash of project key is a sound approach #### Architecture & Design ✅ - **`PromptHistoryManager`** (125 lines) — Clean dataclass with `slots=True`, proper separation of concerns - **`PromptInput` extensions** — History methods delegate cleanly to the manager - **App-level wiring** — Key bindings (`up`/`down`) and `action_history_*` methods follow existing patterns (`action_help`, `action_cycle_preset`) - Optional dependency injection (`prompt_history: PromptHistoryManager | None = None`) is the right pattern #### Type Safety ✅ - All functions have explicit type annotations - `shell_mode: bool` is keyword-only throughout — prevents positional argument confusion - Union types (`PromptHistoryManager | None`) used correctly - Return types specified on all public methods #### Test Quality ✅ - **4 Behave BDD scenarios** covering: separate file storage, pruning, navigation with draft restoration, independent shell history - **2 new app-level scenarios** for `action_history_previous` and `action_history_next` - **1 Robot integration test** for end-to-end prompt history persistence - Tests use proper cleanup (`add_cleanup`, `shutil.rmtree`) - Step definitions are well-structured with helper factories #### Correctness ✅ - Navigation cursor logic correctly handles: first press (save draft, jump to end), subsequent presses (decrement), forward navigation, and draft restoration - Pruning correctly keeps the most recent `max_entries` entries - JSONL format with `json.dumps(ensure_ascii=True)` prevents encoding issues - Graceful handling of corrupt JSONL lines (skip on `JSONDecodeError`) #### Minor Observations (non-blocking) 1. **`_read_entries()` re-reads the file on every `previous()`/`next()` call** — acceptable for TUI use case but could be cached if performance becomes an issue 2. **Global `up`/`down` key bindings** — These may conflict with other widgets that use arrow keys (e.g., list navigation). Consider scoping to the prompt input widget focus. This is a design choice that may need revisiting as the TUI grows. 3. **No deduplication** — Consecutive identical entries are stored separately. Most shell histories deduplicate adjacent duplicates. Consider adding this. --- ### Summary **Decision: REQUEST_CHANGES** — Two blockers must be resolved: 1. **Rebase onto latest `master`** to resolve merge conflicts 2. **Add a PR description** with closing keyword `Closes #1014`, change summary, and validation results Once these are addressed, the code is ready to merge. The implementation is clean, well-typed, well-tested, and follows project conventions.
src/cleveragents/tui/app.py
@ -92,2 +93,4 @@
("f1", "help", "Help"),
("ctrl+t", "cycle_preset", "Cycle Preset"),
("up", "history_previous", "Previous History"),
("down", "history_next", "Next History"),
freemo commented 2026-04-02 16:58:50 +00:00
Owner
Copy link

Design consideration: Binding up and down globally means these keys will trigger history navigation even when focus is on other widgets (e.g., a scrollable list or tree view). As the TUI grows, you may want to scope these bindings to only fire when the #prompt input has focus. Not blocking for now since the current TUI is simple enough.

**Design consideration**: Binding `up` and `down` globally means these keys will trigger history navigation even when focus is on other widgets (e.g., a scrollable list or tree view). As the TUI grows, you may want to scope these bindings to only fire when the `#prompt` input has focus. Not blocking for now since the current TUI is simple enough.
src/cleveragents/tui/prompt_history.py
@ -0,0 +65,4 @@
if not raw_line.strip():
continue
try:
payload = json.loads(raw_line)
freemo commented 2026-04-02 16:58:50 +00:00
Owner
Copy link

Non-blocking observation: _read_entries() is called on every previous() and next() invocation, re-reading the entire JSONL file from disk each time. For the default cap of 10,000 entries this is fine, but if performance becomes a concern, consider caching the entries list and invalidating on append_entry().

**Non-blocking observation**: `_read_entries()` is called on every `previous()` and `next()` invocation, re-reading the entire JSONL file from disk each time. For the default cap of 10,000 entries this is fine, but if performance becomes a concern, consider caching the entries list and invalidating on `append_entry()`.
freemo commented 2026-04-02 17:29:17 +00:00
Owner
Copy link

🤖 Backlog Groomer (groomer-1): Closing as duplicate of #1014.

Issue #1014 (feat(tui): implement prompt history (dual JSONL)) is the canonical version with full labels (MoSCoW/Could have, Priority/Low, State/In Progress, Type/Feature) and milestone v3.8.0. This issue is an exact title duplicate.

🤖 **Backlog Groomer (groomer-1):** Closing as duplicate of #1014. Issue #1014 (`feat(tui): implement prompt history (dual JSONL)`) is the canonical version with full labels (`MoSCoW/Could have`, `Priority/Low`, `State/In Progress`, `Type/Feature`) and milestone `v3.8.0`. This issue is an exact title duplicate.
freemo closed this pull request 2026-04-02 17:29:22 +00:00
freemo commented 2026-04-02 17:37:38 +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.
All checks were successful
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / helm (pull_request) Successful in 21s
Details
CI / build (pull_request) Successful in 23s
Required
Details
CI / quality (pull_request) Successful in 1m2s
Required
Details
CI / lint (pull_request) Successful in 3m18s
Required
Details
CI / typecheck (pull_request) Successful in 3m56s
Required
Details
CI / security (pull_request) Successful in 4m11s
Required
Details
CI / unit_tests (pull_request) Successful in 9m12s
Required
Details
CI / docker (pull_request) Successful in 1m35s
Required
Details
CI / coverage (pull_request) Successful in 12m13s
Required
Details
CI / e2e_tests (pull_request) Successful in 20m5s
Details
CI / integration_tests (pull_request) Successful in 24m45s
Required
Details
CI / status-check (pull_request) Successful in 1s
Details
CI / benchmark-regression (pull_request) Successful in 55m39s
Details

Pull request closed

Please reopen this pull request to perform a merge.
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.8.0
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
freemo
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!1252
No description provided.