bug(cli): automation_profile._get_service() bypasses DI container #1181

Merged

freemo merged 1 commit from bugfix/m4-automation-profile-di-bypass into master 2026-04-02 17:54:14 +00:00

Conversation 6 Commits 1 Files changed 4 +136 -92

brent.edwards commented 2026-03-28 23:12:35 +00:00

Member

Copy link

Summary

• Route automation_profile._get_service() through DI by resolving container.automation_profile_service() instead of manually constructing SQLAlchemy engine/session/repository.
• Add DI wiring in application.container via _build_automation_profile_service() and automation_profile_service provider for consistent CLI service lifecycle/configuration behavior.
• Strengthen coverage with both delegation assertions and a non-mocked integration-style proof that _get_service() resolves through real container/provider wiring.
• Keep PR #990 scope clean by removing unrelated robot/resource_dag.robot changes and consolidating overlapping _get_service() test coverage scenarios.

Validation

• nox -e lint ✅
• nox -e typecheck ✅
• nox -e unit_tests ✅
• nox -e coverage_report ✅ (summary coverage: 97%)
• nox -e integration_tests ❌ (existing integration-suite failures/timeouts in unrelated workflows)
• nox -e e2e_tests ❌ (existing E2E suite failures unrelated to #990 scope)

Closes #990

## Summary - Route `automation_profile._get_service()` through DI by resolving `container.automation_profile_service()` instead of manually constructing SQLAlchemy engine/session/repository. - Add DI wiring in `application.container` via `_build_automation_profile_service()` and `automation_profile_service` provider for consistent CLI service lifecycle/configuration behavior. - Strengthen coverage with both delegation assertions and a non-mocked integration-style proof that `_get_service()` resolves through real container/provider wiring. - Keep PR #990 scope clean by removing unrelated `robot/resource_dag.robot` changes and consolidating overlapping `_get_service()` test coverage scenarios. ## Validation - `nox -e lint` ✅ - `nox -e typecheck` ✅ - `nox -e unit_tests` ✅ - `nox -e coverage_report` ✅ (summary coverage: 97%) - `nox -e integration_tests` ❌ (existing integration-suite failures/timeouts in unrelated workflows) - `nox -e e2e_tests` ❌ (existing E2E suite failures unrelated to #990 scope) Closes #990

brent.edwards added this to the v3.3.0 milestone 2026-03-28 23:12:49 +00:00

brent.edwards added the

Type

Bug

label 2026-03-28 23:14:27 +00:00

brent.edwards added a new dependency 2026-03-28 23:14:50 +00:00

#990 bug(cli): automation_profile._get_service() bypasses DI container

brent.edwards referenced this pull request 2026-03-29 01:20:48 +00:00

bug(cli): automation_profile._get_service() bypasses DI container #990

brent.edwards force-pushed bugfix/m4-automation-profile-di-bypass from cab36ef8f8 to d16e9963ce 2026-03-30 01:07:26 +00:00 Compare

freemo approved these changes 2026-03-30 04:22:15 +00:00

Dismissed

freemo left a comment

Copy link

Review: APPROVED

Excellent DI alignment refactoring. Properly centralizes AutomationProfileService construction in the container and tests delegation behavior rather than implementation details. Clean application of the Dependency Inversion Principle.

## Review: APPROVED Excellent DI alignment refactoring. Properly centralizes `AutomationProfileService` construction in the container and tests delegation behavior rather than implementation details. Clean application of the Dependency Inversion Principle.

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

freemo force-pushed bugfix/m4-automation-profile-di-bypass from d16e9963ce to 601f408860 2026-04-02 06:54:44 +00:00 Compare

freemo dismissed freemo's review 2026-04-02 06:54:44 +00:00

Reason:

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

freemo commented 2026-04-02 08:03:12 +00:00

Owner

Copy link

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

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

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

Dismissed

freemo left a comment

Copy link

Independent Code Review: APPROVED ✅

Summary

Reviewed the complete diff (4 files, +136/-92 lines) against the specification and project conventions.

What was reviewed

Core Fix — _get_service() in automation_profile.py:

• Correctly replaces manual create_engine/sessionmaker/AutomationProfileRepository construction with container.automation_profile_service() delegation
• The old code was the only CLI command that bypassed the DI container — this fix brings it into alignment with all other CLI commands
• Clean, minimal change: 17 lines removed, 3 lines added

Container Wiring — container.py:

• New _build_automation_profile_service() factory function follows the exact same pattern as _build_skill_service, _build_session_service, etc.
• automation_profile_service registered as providers.Factory — appropriate for CLI per-invocation lifecycle
• Import of AutomationProfileService correctly placed at module top level

Test Quality — Behave scenarios:

• Tests shifted from testing implementation details (sessionmaker binding, auto_commit flag) to testing behavior (delegation, provider call count, no direct database_url access)
• Integration-style scenario 5 uses a real DI container with temp SQLite DB — strong end-to-end proof
• All 5 scenarios are meaningful and well-structured

Verification Checklist

• Spec alignment: DI container pattern matches specification requirements
• Commit message: Conventional Changelog format with ISSUES CLOSED: #990 footer
• No # type: ignore introduced (pre-existing ones in get_ai_provider are unrelated)
• No secrets or credentials in code
• automation_profile.py at 473 lines (under 500-line limit)
• PR body has Closes #990, milestone v3.3.0, Type/Bug label
• Single atomic commit — merge (not squash) appropriate
• PR is mergeable with no conflicts

Note

container.py is at 921 lines (exceeds 500-line limit), but this is a pre-existing condition — the PR adds only 29 lines to an already-oversized file. Not a blocker for this PR.

## Independent Code Review: APPROVED ✅ ### Summary Reviewed the complete diff (4 files, +136/-92 lines) against the specification and project conventions. ### What was reviewed **Core Fix — `_get_service()` in `automation_profile.py`:** - Correctly replaces manual `create_engine`/`sessionmaker`/`AutomationProfileRepository` construction with `container.automation_profile_service()` delegation - The old code was the only CLI command that bypassed the DI container — this fix brings it into alignment with all other CLI commands - Clean, minimal change: 17 lines removed, 3 lines added **Container Wiring — `container.py`:** - New `_build_automation_profile_service()` factory function follows the exact same pattern as `_build_skill_service`, `_build_session_service`, etc. - `automation_profile_service` registered as `providers.Factory` — appropriate for CLI per-invocation lifecycle - Import of `AutomationProfileService` correctly placed at module top level **Test Quality — Behave scenarios:** - Tests shifted from testing implementation details (sessionmaker binding, auto_commit flag) to testing behavior (delegation, provider call count, no direct database_url access) - Integration-style scenario 5 uses a real DI container with temp SQLite DB — strong end-to-end proof - All 5 scenarios are meaningful and well-structured ### Verification Checklist - [x] Spec alignment: DI container pattern matches specification requirements - [x] Commit message: Conventional Changelog format with `ISSUES CLOSED: #990` footer - [x] No `# type: ignore` introduced (pre-existing ones in `get_ai_provider` are unrelated) - [x] No secrets or credentials in code - [x] `automation_profile.py` at 473 lines (under 500-line limit) - [x] PR body has `Closes #990`, milestone v3.3.0, Type/Bug label - [x] Single atomic commit — merge (not squash) appropriate - [x] PR is mergeable with no conflicts ### Note `container.py` is at 921 lines (exceeds 500-line limit), but this is a pre-existing condition — the PR adds only 29 lines to an already-oversized file. Not a blocker for this PR.

freemo referenced this pull request 2026-04-02 08:13:52 +00:00

bug(cli): automation_profile._get_service() bypasses DI container #990

freemo commented 2026-04-02 17:47:26 +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:52:44 +00:00

Owner

Copy link

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

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

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

freemo left a comment

Copy link

Independent Code Review: APPROVED ✅

Review Scope

Reviewed the complete diff (4 files changed) against the specification, CONTRIBUTING.md conventions, and DI container patterns established in the codebase.

Findings

Core Fix — _get_service() in automation_profile.py:

• Correctly eliminates the only CLI command that bypassed the DI container by replacing manual create_engine/sessionmaker/AutomationProfileRepository construction with a single container.automation_profile_service() call
• The fix is minimal and surgical: 17 lines removed, 3 lines of clean delegation added
• Fully consistent with how every other CLI command resolves services

Container Wiring — container.py:

• _build_automation_profile_service() follows the identical pattern used by _build_skill_service, _build_session_service, _build_repo_indexing_service, etc.
• Registered as providers.Factory — correct for CLI per-invocation lifecycle (no stale state between commands)
• Import of AutomationProfileService correctly placed at module top level alongside other service imports

Test Quality — 5 BDD Scenarios:

1. Service identity verification (same object from container) — tests delegation, not implementation
2. Provider called exactly once — ensures no redundant resolution
3. No direct database_url access — proves the old bypass path is gone
4. Working DB-backed service via mock container — functional proof
5. Real DI container with temp SQLite — integration-style end-to-end proof without mocking

Tests appropriately shifted from testing implementation details (sessionmaker binding, auto_commit flags) to testing behavioral contracts. Proper cleanup of temp files via context.add_cleanup().

Compliance Checklist

• Specification alignment: DI container pattern matches spec requirements
• Commit message: Conventional Changelog format with ISSUES CLOSED: #990 footer
• No # type: ignore introduced
• No secrets or credentials in code
• automation_profile.py at ~473 lines (under 500-line limit)
• PR body has Closes #990, milestone v3.3.0, Type/Bug label
• Single atomic commit — merge strategy appropriate
• PR is mergeable with no conflicts

Note

container.py exceeds the 500-line limit at ~921 lines, but this is a pre-existing condition. This PR adds only ~29 lines following established patterns — not a blocker.

Approving for merge.

## Independent Code Review: APPROVED ✅ ### Review Scope Reviewed the complete diff (4 files changed) against the specification, CONTRIBUTING.md conventions, and DI container patterns established in the codebase. ### Findings **Core Fix — `_get_service()` in `automation_profile.py`:** - Correctly eliminates the only CLI command that bypassed the DI container by replacing manual `create_engine`/`sessionmaker`/`AutomationProfileRepository` construction with a single `container.automation_profile_service()` call - The fix is minimal and surgical: 17 lines removed, 3 lines of clean delegation added - Fully consistent with how every other CLI command resolves services **Container Wiring — `container.py`:** - `_build_automation_profile_service()` follows the identical pattern used by `_build_skill_service`, `_build_session_service`, `_build_repo_indexing_service`, etc. - Registered as `providers.Factory` — correct for CLI per-invocation lifecycle (no stale state between commands) - Import of `AutomationProfileService` correctly placed at module top level alongside other service imports **Test Quality — 5 BDD Scenarios:** 1. Service identity verification (same object from container) — tests delegation, not implementation 2. Provider called exactly once — ensures no redundant resolution 3. No direct `database_url` access — proves the old bypass path is gone 4. Working DB-backed service via mock container — functional proof 5. Real DI container with temp SQLite — integration-style end-to-end proof without mocking Tests appropriately shifted from testing implementation details (sessionmaker binding, auto_commit flags) to testing behavioral contracts. Proper cleanup of temp files via `context.add_cleanup()`. ### Compliance Checklist - [x] Specification alignment: DI container pattern matches spec requirements - [x] Commit message: Conventional Changelog format with `ISSUES CLOSED: #990` footer - [x] No `# type: ignore` introduced - [x] No secrets or credentials in code - [x] `automation_profile.py` at ~473 lines (under 500-line limit) - [x] PR body has `Closes #990`, milestone v3.3.0, Type/Bug label - [x] Single atomic commit — merge strategy appropriate - [x] PR is mergeable with no conflicts ### Note `container.py` exceeds the 500-line limit at ~921 lines, but this is a pre-existing condition. This PR adds only ~29 lines following established patterns — not a blocker. Approving for merge.

freemo merged commit 2a266929fd into master 2026-04-02 17:54:14 +00:00

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

Merge pull request 'bug(cli): automation_profile._get_service() bypasses DI container' (#1181) from bugfix/m4-automation-profile-di-bypass into master

freemo deleted branch bugfix/m4-automation-profile-di-bypass 2026-04-02 17:54:14 +00:00

freemo referenced this pull request 2026-04-02 17:54:50 +00:00

bug(cli): automation_profile._get_service() bypasses DI container #990

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

test: add TDD bug-capture test for #990 — automation_profile DI bypass #1160

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

test: add TDD bug-capture test for #990 — automation_profile DI bypass #1160

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

TDD: Write failing test for #990 — automation_profile._get_service() bypasses DI #1031

freemo referenced this pull request 2026-04-02 19:05:27 +00:00

test: add TDD bug-capture test for #990 — automation_profile DI bypass #1160

freemo referenced this pull request 2026-04-02 19:05:27 +00:00

test: add TDD bug-capture test for #990 — automation_profile DI bypass #1160

freemo referenced this pull request 2026-04-02 19:05:35 +00:00

TDD: Write failing test for #990 — automation_profile._get_service() bypasses DI #1031

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

test: add TDD bug-capture test for #990 — automation_profile DI bypass #1160

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

test: add TDD bug-capture test for #990 — automation_profile DI bypass #1160

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

TDD: Write failing test for #990 — automation_profile._get_service() bypasses DI #1031

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

test: add TDD bug-capture test for #990 — automation_profile DI bypass #1160

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

test: add TDD bug-capture test for #990 — automation_profile DI bypass #1160

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

TDD: Write failing test for #990 — automation_profile._get_service() bypasses DI #1031

freemo referenced this pull request 2026-04-03 18:56:46 +00:00

test: add TDD bug-capture test for #990 — automation_profile DI bypass #1160

freemo referenced this pull request 2026-04-03 18:56:47 +00:00

test: add TDD bug-capture test for #990 — automation_profile DI bypass #1160

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

TDD: Write failing test for #990 — automation_profile._get_service() bypasses DI #1031

freemo referenced this pull request 2026-04-05 04:10:30 +00:00

test: add TDD bug-capture test for #990 — automation_profile DI bypass #1160

freemo referenced this pull request 2026-04-05 04:10:30 +00:00

test: add TDD bug-capture test for #990 — automation_profile DI bypass #1160

freemo referenced this pull request 2026-04-05 04:10:48 +00:00

TDD: Write failing test for #990 — automation_profile._get_service() bypasses DI #1031

freemo referenced this pull request 2026-04-05 04:57:16 +00:00

test: add TDD bug-capture test for #990 — automation_profile DI bypass #1160

HAL9001 referenced this pull request 2026-05-06 05:36:25 +00:00

test: add TDD bug-capture test for #990 — automation_profile DI bypass #1160

HAL9000 referenced this pull request from a commit 2026-05-29 19:28:12 +00:00

test(cli): add TDD regression tests for automation_profile._get_service() DI bypass

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

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

freemo

2 participants

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Depends on

#990 bug(cli): automation_profile._get_service() bypasses DI container

cleveragents/cleveragents-core

Reference

cleveragents/cleveragents-core!1181

No description provided.