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): add session export/import command support #1244

Closed
brent.edwards wants to merge 1 commit from feature/m8-tui-session-export-import into master
pull from: feature/m8-tui-session-export-import
merge into: cleveragents:master
Conversation 10 Commits 1 Files changed 6 +406 -9
brent.edwards commented 2026-04-01 19:05:26 +00:00
Member
Copy link
No description provided.
feat(tui): add session export/import command support
Some checks failed
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / build (pull_request) Successful in 19s
Details
CI / helm (pull_request) Successful in 24s
Details
CI / lint (pull_request) Successful in 39s
Details
CI / quality (pull_request) Successful in 3m43s
Details
CI / typecheck (pull_request) Successful in 3m56s
Details
CI / security (pull_request) Successful in 4m7s
Details
CI / unit_tests (pull_request) Successful in 9m11s
Details
CI / docker (pull_request) Successful in 1m20s
Details
CI / e2e_tests (pull_request) Failing after 11m56s
Details
CI / coverage (pull_request) Successful in 12m50s
Details
CI / integration_tests (pull_request) Successful in 25m57s
Details
CI / status-check (pull_request) Failing after 1s
Details
CI / benchmark-regression (pull_request) Successful in 55m1s
Details
fc1c5b65e4 
Support /session:export with JSON/Markdown output and /session:import from JSON in the TUI command router, including colon command aliases and safe relative path handling.

Expand Behave and Robot smoke coverage for the new session command flows and update changelog entries.

ISSUES CLOSED: #1004
brent.edwards scheduled this pull request to auto merge when all checks succeed 2026-04-01 19:05:49 +00:00
freemo commented 2026-04-02 08:03:30 +00:00
Owner
Copy link

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

🔒 Claimed by pr-reviewer-5. Starting independent code review.
freemo self-assigned this 2026-04-02 08:06:15 +00:00
freemo commented 2026-04-02 08:09:10 +00:00
Owner
Copy link

⚠️ Backlog Groomer Notice — Potential Duplicate PR

This PR (#1244 "feat(tui): add session export/import command support") and PR #1269 ("feat(tui): implement session export/import (JSON + Markdown)") both reference Closes #1004 (feat(tui): implement session export/import).

PR #1269 appears to be a more comprehensive implementation (JSON + Markdown formats with BDD tests). Please review whether this PR is superseded by #1269 and consider closing one of them to avoid merge conflicts and duplicate work.

This comment was posted automatically by the backlog groomer.

⚠️ **Backlog Groomer Notice — Potential Duplicate PR** This PR (#1244 "feat(tui): add session export/import command support") and PR #1269 ("feat(tui): implement session export/import (JSON + Markdown)") both reference `Closes #1004` (feat(tui): implement session export/import). PR #1269 appears to be a more comprehensive implementation (JSON + Markdown formats with BDD tests). Please review whether this PR is superseded by #1269 and consider closing one of them to avoid merge conflicts and duplicate work. *This comment was posted automatically by the backlog groomer.*
freemo commented 2026-04-02 08:09:21 +00:00
Owner
Copy link

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

This PR (feature/m8-tui-session-export-import) 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 #1244 cannot be merged until conflicts are resolved by the implementing agent. This PR (`feature/m8-tui-session-export-import`) has merge conflicts with `master`. Please rebase onto the latest `master` and resolve all conflicts before this PR can be reviewed and merged.
freemo added this to the v3.7.0 milestone 2026-04-02 08:09:45 +00:00
freemo commented 2026-04-02 16:48:04 +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:52:58 +00:00
Dismissed
freemo left a comment
Copy link

Independent Code Review — PR #1244

Summary

This PR adds session export/import command support to the TUI command router, implementing /session:export (JSON and Markdown formats) and /session:import (from JSON). The code quality is good overall — well-structured, properly typed, with meaningful test coverage. However, there are blocking process issues that prevent merge.

🚫 Blocking Issues (Must Fix)

1. Merge Conflicts (mergeable: false)

The branch has diverged from master and has conflicts in:

  • CHANGELOG.md — Both this branch and master added entries at the top of the "Unreleased" section.
  • robot/tui_smoke.robot — Both this branch and master appended new test cases at the end of the file.

These are textual conflicts that should be straightforward to resolve. Please rebase onto the latest master and resolve conflicts.

2. Empty PR Body

The PR description is completely empty. Per CONTRIBUTING.md, the PR description must:

  • Provide a detailed summary of the changes
  • Include a closing keyword (e.g., Closes #1004)
  • Link the issue as a Forgejo dependency (PR blocks issue)

The commit message is well-written and contains ISSUES CLOSED: #1004, but the PR body itself must also contain this information.

⚠️ Minor Issues (Should Fix)

3. Missing SessionExportError handling in _session_export

The SessionService.export_session() contract declares it can raise both SessionNotFoundError and SessionExportError. Currently only SessionNotFoundError is caught:

try:
    export_data = self.session_service.export_session(session_id)
except SessionNotFoundError:
    return f"Session not found: {session_id}"

If SessionExportError is raised, it will propagate as an unhandled exception in the TUI. Since the command router is the top-level handler for user commands, catching SessionExportError and returning a user-friendly message would be appropriate:

except SessionExportError as exc:
    return f"Session export failed: {exc}"

✅ What Looks Good

  • Commit message follows Conventional Changelog format correctly
  • Single atomic commit — clean history
  • Colon command routing (_split_command) is well-implemented and handles edge cases
  • Path security — _resolve_relative_path() properly rejects absolute paths and directory traversal
  • Argument parsing — _parse_export_args and _parse_import_args handle --format, --input, positional args, and unknown options correctly
  • Markdown rendering — _render_session_markdown() produces clean, structured output
  • Error handling — Comprehensive coverage of file I/O errors, JSON parse errors, and service errors
  • Test coverage — 5 new Behave scenarios covering JSON export, Markdown export, JSON import, invalid JSON import, and colon alias; plus Robot smoke test
  • Type annotations — All new methods are properly typed
  • File length — commands.py stays well under the 500-line limit (~230 lines)
  • SessionService interface — Correctly uses the abstract contract from the domain model
  • session_service: SessionService | None = None — Reasonable optional design for graceful degradation

Duplicate PR Note

PR #1269 (the other PR for issue #1004) was closed without merge, so this PR is the active implementation. The backlog groomer's concern is resolved.

Verdict: REQUEST_CHANGES — Please rebase onto latest master to resolve conflicts, fill in the PR body with a description and Closes #1004, and consider adding SessionExportError handling. The code itself is solid and ready to merge once these items are addressed.

## Independent Code Review — PR #1244 ### Summary This PR adds session export/import command support to the TUI command router, implementing `/session:export` (JSON and Markdown formats) and `/session:import` (from JSON). The code quality is **good overall** — well-structured, properly typed, with meaningful test coverage. However, there are **blocking process issues** that prevent merge. --- ### 🚫 Blocking Issues (Must Fix) #### 1. Merge Conflicts (`mergeable: false`) The branch has diverged from `master` and has conflicts in: - **`CHANGELOG.md`** — Both this branch and master added entries at the top of the "Unreleased" section. - **`robot/tui_smoke.robot`** — Both this branch and master appended new test cases at the end of the file. These are textual conflicts that should be straightforward to resolve. **Please rebase onto the latest `master` and resolve conflicts.** #### 2. Empty PR Body The PR description is completely empty. Per CONTRIBUTING.md, the PR description must: - Provide a detailed summary of the changes - Include a closing keyword (e.g., `Closes #1004`) - Link the issue as a Forgejo dependency (PR blocks issue) The commit message is well-written and contains `ISSUES CLOSED: #1004`, but the PR body itself must also contain this information. --- ### ⚠️ Minor Issues (Should Fix) #### 3. Missing `SessionExportError` handling in `_session_export` The `SessionService.export_session()` contract declares it can raise both `SessionNotFoundError` and `SessionExportError`. Currently only `SessionNotFoundError` is caught: ```python try: export_data = self.session_service.export_session(session_id) except SessionNotFoundError: return f"Session not found: {session_id}" ``` If `SessionExportError` is raised, it will propagate as an unhandled exception in the TUI. Since the command router is the top-level handler for user commands, catching `SessionExportError` and returning a user-friendly message would be appropriate: ```python except SessionExportError as exc: return f"Session export failed: {exc}" ``` --- ### ✅ What Looks Good - **Commit message** follows Conventional Changelog format correctly - **Single atomic commit** — clean history - **Colon command routing** (`_split_command`) is well-implemented and handles edge cases - **Path security** — `_resolve_relative_path()` properly rejects absolute paths and directory traversal - **Argument parsing** — `_parse_export_args` and `_parse_import_args` handle `--format`, `--input`, positional args, and unknown options correctly - **Markdown rendering** — `_render_session_markdown()` produces clean, structured output - **Error handling** — Comprehensive coverage of file I/O errors, JSON parse errors, and service errors - **Test coverage** — 5 new Behave scenarios covering JSON export, Markdown export, JSON import, invalid JSON import, and colon alias; plus Robot smoke test - **Type annotations** — All new methods are properly typed - **File length** — commands.py stays well under the 500-line limit (~230 lines) - **SessionService interface** — Correctly uses the abstract contract from the domain model - **`session_service: SessionService | None = None`** — Reasonable optional design for graceful degradation ### Duplicate PR Note PR #1269 (the other PR for issue #1004) was closed without merge, so this PR is the active implementation. The backlog groomer's concern is resolved. --- **Verdict: REQUEST_CHANGES** — Please rebase onto latest `master` to resolve conflicts, fill in the PR body with a description and `Closes #1004`, and consider adding `SessionExportError` handling. The code itself is solid and ready to merge once these items are addressed.
src/cleveragents/tui/commands.py
@ -50,0 +170,4 @@
input_path = Path(arg.split("=", maxsplit=1)[1])
elif arg.startswith("--"):
raise ValueError(f"Unknown option: {arg}")
else:
freemo commented 2026-04-02 16:52:58 +00:00
Owner
Copy link

The SessionService.export_session() contract can raise SessionExportError in addition to SessionNotFoundError. Consider catching it here to provide a user-friendly error message instead of letting it propagate as an unhandled exception in the TUI:

except SessionNotFoundError:
    return f"Session not found: {session_id}"
except SessionExportError as exc:
    return f"Session export failed: {exc}"
The `SessionService.export_session()` contract can raise `SessionExportError` in addition to `SessionNotFoundError`. Consider catching it here to provide a user-friendly error message instead of letting it propagate as an unhandled exception in the TUI: ```python except SessionNotFoundError: return f"Session not found: {session_id}" except SessionExportError as exc: return f"Session export failed: {exc}" ```
freemo commented 2026-04-02 17:34:20 +00:00
Owner
Copy link

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

Review claimed by reviewer pool instance reviewer-pool-2. Dispatching independent code review.
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.
freemo requested changes 2026-04-02 17:39:25 +00:00
Dismissed
freemo left a comment
Copy link

Independent Code Review — PR #1244 (Second Review)

Verdict: REQUEST_CHANGES — PR is superseded; should be closed

🚫 Critical: This PR is superseded by PR #1392 (already merged)

PR #1392 (feat(tui): implement session export/import (JSON + Markdown)) was merged into master at 2026-04-02T17:30:37Z and closed issue #1004. That PR implemented a more comprehensive version of the same feature, including:

  • Session.as_export_markdown() domain method
  • CLI --format flag extension
  • TUI command router export/import handlers
  • 16 Behave scenarios

This PR (#1244) is now obsolete. Merging it would introduce duplicate and conflicting code. The merge conflicts (mergeable: false) are a direct consequence of PR #1392 already modifying the same files.

Recommendation: Close this PR without merge.

Process Issues (would have been blocking even without supersession)

  1. Empty PR body — The PR description is completely empty. Per CONTRIBUTING.md, PRs must have a detailed description explaining the "what" and "why", and must include a closing keyword (Closes #1004). The commit message contains ISSUES CLOSED: #1004 but the PR body itself must also contain this.

  2. Merge conflicts — mergeable: false. Conflicts exist in CHANGELOG.md and robot/tui_smoke.robot due to PR #1392 already being merged.

Code Quality Assessment (for the record)

Despite the process issues, the code itself was well-written:

✅ Strengths:

  • Clean, well-structured implementation with proper type annotations
  • _split_command() colon-alias routing is elegant and handles edge cases
  • _resolve_relative_path() provides good security against path traversal
  • _parse_export_args() and _parse_import_args() handle flags, positional args, and unknown options correctly
  • _render_session_markdown() produces clean, structured output
  • Comprehensive error handling for file I/O, JSON parsing, and service errors
  • 5 meaningful Behave scenarios + Robot smoke test
  • Single atomic commit with proper Conventional Changelog format
  • File stays well under 500-line limit

⚠️ Minor issue (would have needed fixing):

  • _session_export() catches SessionNotFoundError but not SessionExportError, while _session_import() catches SessionImportError. This is inconsistent — the export handler should also catch SessionExportError for a user-friendly error message.

Action required: Close this PR. Issue #1004 is already resolved by PR #1392.

## Independent Code Review — PR #1244 (Second Review) ### Verdict: REQUEST_CHANGES — PR is superseded; should be closed --- ### 🚫 Critical: This PR is superseded by PR #1392 (already merged) **PR #1392** (`feat(tui): implement session export/import (JSON + Markdown)`) was merged into `master` at 2026-04-02T17:30:37Z and closed issue #1004. That PR implemented a more comprehensive version of the same feature, including: - `Session.as_export_markdown()` domain method - CLI `--format` flag extension - TUI command router export/import handlers - 16 Behave scenarios **This PR (#1244) is now obsolete.** Merging it would introduce duplicate and conflicting code. The merge conflicts (`mergeable: false`) are a direct consequence of PR #1392 already modifying the same files. **Recommendation: Close this PR without merge.** --- ### Process Issues (would have been blocking even without supersession) 1. **Empty PR body** — The PR description is completely empty. Per CONTRIBUTING.md, PRs must have a detailed description explaining the "what" and "why", and must include a closing keyword (`Closes #1004`). The commit message contains `ISSUES CLOSED: #1004` but the PR body itself must also contain this. 2. **Merge conflicts** — `mergeable: false`. Conflicts exist in `CHANGELOG.md` and `robot/tui_smoke.robot` due to PR #1392 already being merged. --- ### Code Quality Assessment (for the record) Despite the process issues, the code itself was well-written: ✅ **Strengths:** - Clean, well-structured implementation with proper type annotations - `_split_command()` colon-alias routing is elegant and handles edge cases - `_resolve_relative_path()` provides good security against path traversal - `_parse_export_args()` and `_parse_import_args()` handle flags, positional args, and unknown options correctly - `_render_session_markdown()` produces clean, structured output - Comprehensive error handling for file I/O, JSON parsing, and service errors - 5 meaningful Behave scenarios + Robot smoke test - Single atomic commit with proper Conventional Changelog format - File stays well under 500-line limit ⚠️ **Minor issue (would have needed fixing):** - `_session_export()` catches `SessionNotFoundError` but not `SessionExportError`, while `_session_import()` catches `SessionImportError`. This is inconsistent — the export handler should also catch `SessionExportError` for a user-friendly error message. --- **Action required: Close this PR. Issue #1004 is already resolved by PR #1392.**
freemo commented 2026-04-02 17:39:35 +00:00
Owner
Copy link

Closing this PR as superseded. PR #1392 (feat(tui): implement session export/import (JSON + Markdown)) was already merged into master and closed issue #1004. This PR would introduce duplicate and conflicting code. The code quality was good, but this implementation is no longer needed.

**Closing this PR as superseded.** PR #1392 (`feat(tui): implement session export/import (JSON + Markdown)`) was already merged into `master` and closed issue #1004. This PR would introduce duplicate and conflicting code. The code quality was good, but this implementation is no longer needed.
freemo closed this pull request 2026-04-02 17:39:51 +00:00
freemo requested changes 2026-04-02 17:42:01 +00:00
freemo left a comment
Copy link

Independent Code Review — PR #1244 (Superseded)

Verdict: CLOSE WITHOUT MERGE

This PR is superseded by PR #1392, which was already merged into master at 2026-04-02T17:30:37Z. PR #1392 implements the same feature (session export/import with JSON + Markdown support for issue #1004) and has already been reviewed, approved, and merged.

Timeline of events:

  1. PR #1244 (this PR) — original implementation by brent.edwards, opened 2026-04-01
  2. PR #1269 — second implementation attempt, closed without merge
  3. PR #1392 — third implementation, merged 2026-04-02T17:30:37Z, resolving issue #1004

Why this PR cannot be merged:

  1. Superseded — Issue #1004 is already resolved by PR #1392. Merging this would introduce duplicate/conflicting code.
  2. Merge conflicts — mergeable: false due to conflicts in CHANGELOG.md and robot/tui_smoke.robot (caused by PR #1392's merge).
  3. Empty PR body — Missing required description, Closes #1004 keyword, and dependency links per CONTRIBUTING.md.

Recommendation:

This PR should be closed without merge. No further action is needed on issue #1004.

## Independent Code Review — PR #1244 (Superseded) ### Verdict: CLOSE WITHOUT MERGE **This PR is superseded by PR #1392**, which was already merged into `master` at 2026-04-02T17:30:37Z. PR #1392 implements the same feature (session export/import with JSON + Markdown support for issue #1004) and has already been reviewed, approved, and merged. ### Timeline of events: 1. **PR #1244** (this PR) — original implementation by `brent.edwards`, opened 2026-04-01 2. **PR #1269** — second implementation attempt, closed without merge 3. **PR #1392** — third implementation, **merged** 2026-04-02T17:30:37Z, resolving issue #1004 ### Why this PR cannot be merged: 1. **Superseded** — Issue #1004 is already resolved by PR #1392. Merging this would introduce duplicate/conflicting code. 2. **Merge conflicts** — `mergeable: false` due to conflicts in `CHANGELOG.md` and `robot/tui_smoke.robot` (caused by PR #1392's merge). 3. **Empty PR body** — Missing required description, `Closes #1004` keyword, and dependency links per CONTRIBUTING.md. ### Recommendation: This PR should be **closed without merge**. No further action is needed on issue #1004.
Some checks failed
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / build (pull_request) Successful in 19s
Required
Details
CI / helm (pull_request) Successful in 24s
Details
CI / lint (pull_request) Successful in 39s
Required
Details
CI / quality (pull_request) Successful in 3m43s
Required
Details
CI / typecheck (pull_request) Successful in 3m56s
Required
Details
CI / security (pull_request) Successful in 4m7s
Required
Details
CI / unit_tests (pull_request) Successful in 9m11s
Required
Details
CI / docker (pull_request) Successful in 1m20s
Required
Details
CI / e2e_tests (pull_request) Failing after 11m56s
Details
CI / coverage (pull_request) Successful in 12m50s
Required
Details
CI / integration_tests (pull_request) Successful in 25m57s
Required
Details
CI / status-check (pull_request) Failing after 1s
Details
CI / benchmark-regression (pull_request) Successful in 55m1s
Details

Pull request closed

This pull request cannot be reopened because the branch was deleted.
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.7.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!1244
No description provided.