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

refactor(test): replace deprecated tempfile.mktemp() with tempfile.mkstemp() #736

Closed
CoreRasurae wants to merge 1 commit from refactor/m3-replace-mktemp into master
pull from: refactor/m3-replace-mktemp
merge into: cleveragents:master
Conversation 6 Commits 1 Files changed 18 +82 -32
CoreRasurae commented 2026-03-12 14:29:35 +00:00
Member
Copy link

Summary

Replaced all 28 uses of the deprecated tempfile.mktemp() function with the atomic tempfile.mkstemp() + os.close(fd) pattern across 16 test infrastructure and benchmark files. Added import os where it was not already present.

tempfile.mktemp() has been deprecated since Python 2.3 due to a TOCTOU (time-of-check-to-time-of-use) race condition: between name generation and file creation, another process could create a file at the predicted path. Under 16-worker parallel test execution (behave-parallel), there was also a non-zero risk of path collisions.

Closes #730

Motivation

Identified during the code review of PR #727 (Finding #7 in the APPROVED review, Security Review Finding #2, and Performance Review P3 by @hurui200320). These are pre-existing issues not introduced by that PR.

Changes

Files modified (28 call sites across 16 files + CHANGELOG):

File Call sites Change
features/environment.py 3 mktemp → mkstemp + os.close(fd)
robot/helper_resource_registry_migration.py 3 mktemp → mkstemp + os.close(fd), added import os
robot/helper_plan_phase_migration.py 1 mktemp → mkstemp + os.close(fd), added import os
robot/helper_plan_persistence_e2e.py 1 mktemp → mkstemp + os.close(fd), added import os
robot/helper_persistence_lifecycle.py 1 mktemp → mkstemp + os.close(fd), added import os
robot/helper_db_lifecycle_models.py 1 mktemp → mkstemp + os.close(fd), added import os
robot/helper_automation_profiles.py 1 mktemp → mkstemp + os.close(fd), added import os
features/steps/skill_discovery_steps.py 2 mktemp → mkstemp + os.close(fd), added import os
features/steps/resource_registry_tables_steps.py 2 mktemp → mkstemp + os.close(fd), added import os
features/steps/plan_persistence_steps.py 1 mktemp → mkstemp + os.close(fd), added import os
features/steps/persistence_robot_alignment_steps.py 1 mktemp → mkstemp + os.close(fd), added import os
features/steps/garbage_collection_cli_steps.py 3 mktemp → mkstemp + os.close(fd)
features/steps/decision_recording_steps.py 1 mktemp → mkstemp + os.close(fd)
features/steps/coverage_boost_steps.py 1 mktemp → mkstemp + os.close(fd)
features/steps/cli_streaming_steps.py 1 mktemp → mkstemp + os.close(fd)
features/steps/automation_profiles_guards_steps.py 1 mktemp → mkstemp + os.close(fd), added import os
benchmarks/persistence_robot_bench.py 4 mktemp → mkstemp + os.close(fd), added import os
CHANGELOG.md — Added entry under Unreleased

Replacement pattern

# Before (deprecated, TOCTOU-vulnerable)
tmp = tempfile.mktemp(suffix=".db", prefix="prefix_")

# After (atomic file creation)
fd, tmp = tempfile.mkstemp(suffix=".db", prefix="prefix_")
os.close(fd)

Test Results

Metric Before After Delta
Features passed 374 374 Same
Scenarios passed 10,640 10,640 Same
Steps passed 40,632 40,632 Same
Behave total time 3m 51s 4m 01s +10s (noise)
Wall time 3m 27s 3m 36s +9s (noise)
Failures 0 0 Same

The ~9s wall-time delta (+4.3%) is within normal run-to-run variance for a 3.5-minute parallel test suite and does not represent a real regression.

Acceptance Criteria Verification

  • Zero remaining uses of tempfile.mktemp() in the codebase
  • All replacements use tempfile.mkstemp() + os.close(fd) atomic approach
  • All tests pass under parallel (16-worker) execution
  • No Python deprecation warnings related to tempfile
  • CHANGELOG.md updated
## Summary Replaced all 28 uses of the deprecated `tempfile.mktemp()` function with the atomic `tempfile.mkstemp()` + `os.close(fd)` pattern across 16 test infrastructure and benchmark files. Added `import os` where it was not already present. `tempfile.mktemp()` has been [deprecated since Python 2.3](https://docs.python.org/3/library/tempfile.html#tempfile.mktemp) due to a TOCTOU (time-of-check-to-time-of-use) race condition: between name generation and file creation, another process could create a file at the predicted path. Under 16-worker parallel test execution (`behave-parallel`), there was also a non-zero risk of path collisions. Closes #730 ## Motivation Identified during the code review of PR #727 (Finding #7 in the APPROVED review, Security Review Finding #2, and Performance Review P3 by @hurui200320). These are pre-existing issues not introduced by that PR. ## Changes ### Files modified (28 call sites across 16 files + CHANGELOG): | File | Call sites | Change | |------|-----------|--------| | `features/environment.py` | 3 | `mktemp` → `mkstemp` + `os.close(fd)` | | `robot/helper_resource_registry_migration.py` | 3 | `mktemp` → `mkstemp` + `os.close(fd)`, added `import os` | | `robot/helper_plan_phase_migration.py` | 1 | `mktemp` → `mkstemp` + `os.close(fd)`, added `import os` | | `robot/helper_plan_persistence_e2e.py` | 1 | `mktemp` → `mkstemp` + `os.close(fd)`, added `import os` | | `robot/helper_persistence_lifecycle.py` | 1 | `mktemp` → `mkstemp` + `os.close(fd)`, added `import os` | | `robot/helper_db_lifecycle_models.py` | 1 | `mktemp` → `mkstemp` + `os.close(fd)`, added `import os` | | `robot/helper_automation_profiles.py` | 1 | `mktemp` → `mkstemp` + `os.close(fd)`, added `import os` | | `features/steps/skill_discovery_steps.py` | 2 | `mktemp` → `mkstemp` + `os.close(fd)`, added `import os` | | `features/steps/resource_registry_tables_steps.py` | 2 | `mktemp` → `mkstemp` + `os.close(fd)`, added `import os` | | `features/steps/plan_persistence_steps.py` | 1 | `mktemp` → `mkstemp` + `os.close(fd)`, added `import os` | | `features/steps/persistence_robot_alignment_steps.py` | 1 | `mktemp` → `mkstemp` + `os.close(fd)`, added `import os` | | `features/steps/garbage_collection_cli_steps.py` | 3 | `mktemp` → `mkstemp` + `os.close(fd)` | | `features/steps/decision_recording_steps.py` | 1 | `mktemp` → `mkstemp` + `os.close(fd)` | | `features/steps/coverage_boost_steps.py` | 1 | `mktemp` → `mkstemp` + `os.close(fd)` | | `features/steps/cli_streaming_steps.py` | 1 | `mktemp` → `mkstemp` + `os.close(fd)` | | `features/steps/automation_profiles_guards_steps.py` | 1 | `mktemp` → `mkstemp` + `os.close(fd)`, added `import os` | | `benchmarks/persistence_robot_bench.py` | 4 | `mktemp` → `mkstemp` + `os.close(fd)`, added `import os` | | `CHANGELOG.md` | — | Added entry under Unreleased | ### Replacement pattern ```python # Before (deprecated, TOCTOU-vulnerable) tmp = tempfile.mktemp(suffix=".db", prefix="prefix_") # After (atomic file creation) fd, tmp = tempfile.mkstemp(suffix=".db", prefix="prefix_") os.close(fd) ``` ## Test Results | Metric | Before | After | Delta | |--------|--------|-------|-------| | Features passed | 374 | 374 | Same | | Scenarios passed | 10,640 | 10,640 | Same | | Steps passed | 40,632 | 40,632 | Same | | Behave total time | 3m 51s | 4m 01s | +10s (noise) | | Wall time | 3m 27s | 3m 36s | +9s (noise) | | Failures | 0 | 0 | Same | The ~9s wall-time delta (+4.3%) is within normal run-to-run variance for a 3.5-minute parallel test suite and does not represent a real regression. ## Acceptance Criteria Verification - [x] Zero remaining uses of `tempfile.mktemp()` in the codebase - [x] All replacements use `tempfile.mkstemp()` + `os.close(fd)` atomic approach - [x] All tests pass under parallel (16-worker) execution - [x] No Python deprecation warnings related to tempfile - [x] CHANGELOG.md updated
refactor(test): replace deprecated tempfile.mktemp() with tempfile.mkstemp()
All checks were successful
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / lint (pull_request) Successful in 14s
Details
CI / quality (pull_request) Successful in 17s
Details
CI / build (pull_request) Successful in 25s
Details
CI / typecheck (pull_request) Successful in 38s
Details
CI / security (pull_request) Successful in 43s
Details
CI / unit_tests (pull_request) Successful in 3m7s
Details
CI / docker (pull_request) Successful in 41s
Details
CI / integration_tests (pull_request) Successful in 5m3s
Details
CI / coverage (pull_request) Successful in 5m26s
Details
CI / benchmark-regression (pull_request) Successful in 38m33s
Details
532f128a49 
Replaced all 28 uses of the deprecated tempfile.mktemp() function with the
atomic tempfile.mkstemp() + os.close(fd) pattern across 16 test infrastructure
and benchmark files.  Added import os where it was not already present.

tempfile.mktemp() has been deprecated since Python 2.3 due to a TOCTOU race
condition: between name generation and file creation, another process could
create a file at the predicted path.  Under 16-worker parallel test execution,
there was also a non-zero risk of path collisions.

Files modified:
- features/environment.py (3 call sites)
- robot/helper_resource_registry_migration.py (3 call sites)
- robot/helper_plan_phase_migration.py (1 call site)
- robot/helper_plan_persistence_e2e.py (1 call site)
- robot/helper_persistence_lifecycle.py (1 call site)
- robot/helper_db_lifecycle_models.py (1 call site)
- robot/helper_automation_profiles.py (1 call site)
- features/steps/skill_discovery_steps.py (2 call sites)
- features/steps/resource_registry_tables_steps.py (2 call sites)
- features/steps/plan_persistence_steps.py (1 call site)
- features/steps/persistence_robot_alignment_steps.py (1 call site)
- features/steps/garbage_collection_cli_steps.py (3 call sites)
- features/steps/decision_recording_steps.py (1 call site)
- features/steps/coverage_boost_steps.py (1 call site)
- features/steps/cli_streaming_steps.py (1 call site)
- features/steps/automation_profiles_guards_steps.py (1 call site)
- benchmarks/persistence_robot_bench.py (4 call sites)

All 10,640 BDD scenarios pass.  No performance regression observed (within
normal run-to-run variance).  Zero remaining uses of tempfile.mktemp() in
the codebase.

ISSUES CLOSED: #730
freemo added this to the v3.2.0 milestone 2026-03-12 20:22:21 +00:00
freemo approved these changes 2026-03-12 20:36:52 +00:00
freemo left a comment
Copy link

Review — PR #736: refactor(test): replace deprecated tempfile.mktemp() with tempfile.mkstemp()

Diff Summary

  • Files changed: 18 (16 test/benchmark files + CHANGELOG.md + 1 duplicate import addition)
  • Lines: +82 / −32

Commit Message Compliance

  • Issue #730 metadata: refactor(test): replace deprecated tempfile.mktemp() with tempfile.mkstemp()
  • PR commit first line: refactor(test): replace deprecated tempfile.mktemp() with tempfile.mkstemp()
  • Match: ✅ Exact match

Closes Keyword

  • PR body contains Closes #730 ✅

Label Compliance

Required Label Status
Type label ✅ Type/Task
Priority label ❌ Missing on PR (issue has Priority/Medium)
MoSCoW label ❌ Missing on both PR and issue #730

Code Quality

  • Every replacement follows the identical, correct pattern: fd, tmp = tempfile.mkstemp(...) → os.close(fd). This eliminates the TOCTOU race condition from the deprecated mktemp().
  • import os is added exactly where it was previously absent — no unnecessary import additions.
  • CHANGELOG.md is updated with a clear, well-written entry.
  • All 10,640 BDD scenarios reported passing under both sequential and 16-worker parallel execution.
  • The one area I'd note for future reference: features/steps/resource_registry_tables_steps.py has a duplicate import os and import tempfile inside the function step_run_init_database_twice (line ~958) — these are local re-imports, harmless but slightly inconsistent with other call sites that use module-level imports. Not a blocker.

Verdict: APPROVED

Clean, mechanical, consistent refactoring with no behavioral changes. Well-documented PR body with test metrics. Minor note: please add Priority/Medium label to the PR, and consider adding a MoSCoW label to both issue #730 and this PR.

## Review — PR #736: refactor(test): replace deprecated tempfile.mktemp() with tempfile.mkstemp() ### Diff Summary - **Files changed:** 18 (16 test/benchmark files + CHANGELOG.md + 1 duplicate import addition) - **Lines:** +82 / −32 ### Commit Message Compliance - **Issue #730 metadata:** `refactor(test): replace deprecated tempfile.mktemp() with tempfile.mkstemp()` - **PR commit first line:** `refactor(test): replace deprecated tempfile.mktemp() with tempfile.mkstemp()` - **Match:** ✅ Exact match ### Closes Keyword - PR body contains `Closes #730` ✅ ### Label Compliance | Required Label | Status | |---|---| | Type label | ✅ `Type/Task` | | Priority label | ❌ Missing on PR (issue has `Priority/Medium`) | | MoSCoW label | ❌ Missing on both PR and issue #730 | ### Code Quality - Every replacement follows the identical, correct pattern: `fd, tmp = tempfile.mkstemp(...)` → `os.close(fd)`. This eliminates the TOCTOU race condition from the deprecated `mktemp()`. - `import os` is added exactly where it was previously absent — no unnecessary import additions. - CHANGELOG.md is updated with a clear, well-written entry. - All 10,640 BDD scenarios reported passing under both sequential and 16-worker parallel execution. - The one area I'd note for future reference: `features/steps/resource_registry_tables_steps.py` has a duplicate `import os` and `import tempfile` inside the function `step_run_init_database_twice` (line ~958) — these are local re-imports, harmless but slightly inconsistent with other call sites that use module-level imports. Not a blocker. ### Verdict: APPROVED Clean, mechanical, consistent refactoring with no behavioral changes. Well-documented PR body with test metrics. Minor note: please add `Priority/Medium` label to the PR, and consider adding a MoSCoW label to both issue #730 and this PR.
freemo commented 2026-03-13 22:06:10 +00:00
Owner
Copy link

Rebase Required

@CoreRasurae — This PR has merge conflicts with master. Please rebase onto the latest master and force-push. See also: #656, #804, #806, #807 (all need rebase).

## Rebase Required @CoreRasurae — This PR has merge conflicts with `master`. Please rebase onto the latest `master` and force-push. See also: #656, #804, #806, #807 (all need rebase).
freemo commented 2026-03-14 04:24:36 +00:00
Owner
Copy link

PM Status Update — Day 34

This is a low-risk, well-documented refactor (replaces deprecated tempfile.mktemp() across 28 call sites in 16 files). All tests pass, zero regressions. Should be a quick merge after rebase.

@CoreRasurae — Rebase onto master and force-push. This is the safest of your 5 conflicted PRs and should be rebased first for a quick win.

Reviewer needed: @hurui200320 — please do a quick approval review after Luis rebases. This is straightforward.

Priority: Medium (M3, low risk, quick merge)

**PM Status Update — Day 34** This is a low-risk, well-documented refactor (replaces deprecated `tempfile.mktemp()` across 28 call sites in 16 files). All tests pass, zero regressions. Should be a quick merge after rebase. **@CoreRasurae** — Rebase onto master and force-push. This is the safest of your 5 conflicted PRs and should be rebased first for a quick win. **Reviewer needed:** @hurui200320 — please do a quick approval review after Luis rebases. This is straightforward. **Priority:** Medium (M3, low risk, quick merge)
freemo commented 2026-03-16 03:29:01 +00:00
Owner
Copy link

PM Status — Day 36

Rebase still needed. This is the safest of the conflicted PRs — low-risk refactor replacing deprecated tempfile.mktemp() across 28 call sites.

@CoreRasurae — Rebase this PR onto master. It should be a quick merge after rebase. This can be done alongside your other rebase tasks (#804, #806).

@hurui200320 — Quick approval review after rebase.

PM status comment — Day 36

## PM Status — Day 36 **Rebase still needed.** This is the safest of the conflicted PRs — low-risk refactor replacing deprecated `tempfile.mktemp()` across 28 call sites. @CoreRasurae — Rebase this PR onto master. It should be a quick merge after rebase. This can be done alongside your other rebase tasks (#804, #806). @hurui200320 — Quick approval review after rebase. --- *PM status comment — Day 36*
freemo reviewed 2026-03-16 16:14:58 +00:00
freemo left a comment
Copy link

PM Day 36 Triage: MERGE CONFLICT. @CoreRasurae please rebase onto master at your earliest convenience. This is a low-priority cleanup PR targeting v3.2.0 (M3). Reviewer: @brent.edwards — please review once rebased.

PM Day 36 Triage: MERGE CONFLICT. @CoreRasurae please rebase onto master at your earliest convenience. This is a low-priority cleanup PR targeting v3.2.0 (M3). Reviewer: @brent.edwards — please review once rebased.
freemo self-assigned this 2026-04-02 06:15:26 +00:00
freemo commented 2026-04-02 17:36:27 +00:00
Owner
Copy link

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

Issue #730 (refactor(test): replace deprecated tempfile.mktemp() with tempfile.mkstemp()) is the canonical version with full labels (MoSCoW/Should have, Priority/Medium, State/In Review, Type/Task) and milestone v3.2.0. This issue is an exact title duplicate.

🤖 **Backlog Groomer (groomer-1):** Closing as duplicate of #730. Issue #730 (`refactor(test): replace deprecated tempfile.mktemp() with tempfile.mkstemp()`) is the canonical version with full labels (`MoSCoW/Should have`, `Priority/Medium`, `State/In Review`, `Type/Task`) and milestone `v3.2.0`. This issue is an exact title duplicate.
freemo closed this pull request 2026-04-02 17:36:46 +00:00
All checks were successful
CI / benchmark-publish (pull_request) Has been skipped
Details
CI / lint (pull_request) Successful in 14s
Required
Details
CI / quality (pull_request) Successful in 17s
Required
Details
CI / build (pull_request) Successful in 25s
Required
Details
CI / typecheck (pull_request) Successful in 38s
Required
Details
CI / security (pull_request) Successful in 43s
Required
Details
CI / unit_tests (pull_request) Successful in 3m7s
Required
Details
CI / docker (pull_request) Successful in 41s
Required
Details
CI / integration_tests (pull_request) Successful in 5m3s
Required
Details
CI / coverage (pull_request) Successful in 5m26s
Required
Details
CI / benchmark-regression (pull_request) Successful in 38m33s
Details

Pull request closed

Please reopen this pull request to perform a merge.
Sign in to join this conversation.
Reviewers
No reviewers
freemo
brent.edwards
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
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!736
No description provided.