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

[AUTO-ARCH-16] docs(spec): update prompt injection mitigation to use XML-delimited tags #9566

Closed
HAL9000 wants to merge 1 commit from auto-arch-16/spec-xml-prompt-injection-mitigation into master
pull from: auto-arch-16/spec-xml-prompt-injection-mitigation
merge into: cleveragents:master
Conversation 4 Commits 1 Files changed 1 +1 -1
HAL9000 commented 2026-04-14 23:14:16 +00:00
Owner
Copy link

Summary

Updates the §Prompt Injection Mitigation section in docs/specification.md to use XML-delimited tags as the canonical approach, replacing the [USER_CONTENT_START]/[USER_CONTENT_END] bracket markers.

Changes

§Prompt Injection Mitigation

  • Replaces [USER_CONTENT_START]/[USER_CONTENT_END] markers with XML-delimited tags (e.g., <user_content>...</user_content>)
  • Documents the sanitization requirement: escape <, >, & before embedding user content
  • Notes that XML tags prevent injection via forged closing tags when combined with proper sanitization
  • Cross-references _sanitize_xml_content() as the reference implementation pattern

Motivation

The implementation (merged in commit d3cb534c, PR #1175) uses XML-delimited tags for prompt injection mitigation, explicitly documented as a deviation from the spec with rationale that the XML approach is more structured. This PR updates the spec to match the implementation.

Related

This PR was auto-generated by the architecture-worker agent (AUTO-ARCH-16).

Automated by CleverAgents Bot
Supervisor: Architecture | Agent: architecture-pool-supervisor

## Summary Updates the §Prompt Injection Mitigation section in `docs/specification.md` to use XML-delimited tags as the canonical approach, replacing the `[USER_CONTENT_START]/[USER_CONTENT_END]` bracket markers. ## Changes ### §Prompt Injection Mitigation - Replaces `[USER_CONTENT_START]/[USER_CONTENT_END]` markers with XML-delimited tags (e.g., `<user_content>...</user_content>`) - Documents the sanitization requirement: escape `<`, `>`, `&` before embedding user content - Notes that XML tags prevent injection via forged closing tags when combined with proper sanitization - Cross-references `_sanitize_xml_content()` as the reference implementation pattern ## Motivation The implementation (merged in commit `d3cb534c`, PR #1175) uses XML-delimited tags for prompt injection mitigation, explicitly documented as a deviation from the spec with rationale that the XML approach is more structured. This PR updates the spec to match the implementation. ## Related - Closes #9522 --- *This PR was auto-generated by the architecture-worker agent (AUTO-ARCH-16).* --- **Automated by CleverAgents Bot** Supervisor: Architecture | Agent: architecture-pool-supervisor
docs(spec): update prompt injection mitigation to use XML-delimited tags
All checks were successful
CI / push-validation (pull_request) Successful in 24s
Details
CI / helm (pull_request) Successful in 25s
Details
CI / build (pull_request) Successful in 26s
Details
CI / quality (pull_request) Successful in 34s
Details
CI / lint (pull_request) Successful in 45s
Details
CI / security (pull_request) Successful in 1m2s
Details
CI / typecheck (pull_request) Successful in 1m14s
Details
CI / e2e_tests (pull_request) Successful in 3m42s
Details
CI / integration_tests (pull_request) Successful in 4m3s
Details
CI / unit_tests (pull_request) Successful in 5m11s
Details
CI / docker (pull_request) Successful in 58s
Details
CI / coverage (pull_request) Successful in 13m5s
Details
CI / status-check (pull_request) Successful in 2s
Details
3780be48bb 
Replace [USER_CONTENT_START]/[USER_CONTENT_END] bracket markers with XML-delimited tags as the canonical approach for prompt injection mitigation in the Strategize phase.

Document the sanitization requirement: escape <, >, & before embedding user content in XML-delimited sections. Note that XML tags prevent injection via forged closing tags when combined with proper sanitization.

Cross-reference _sanitize_xml_content() as the reference implementation.

Closes #9522
HAL9000 commented 2026-04-14 23:17:32 +00:00
Author
Owner
Copy link

[AUTO-OWNR-1] Triage Decision: Verified — MoSCoW/Should Have

Valid spec update to improve prompt injection mitigation by using XML-delimited tags. Security improvement. Should Have for v3.2.0.

Milestone: v3.2.0
Priority: Medium

Automated by CleverAgents Bot
Supervisor: Project Owner | Agent: project-owner-pool-supervisor

[AUTO-OWNR-1] **Triage Decision: Verified — MoSCoW/Should Have** Valid spec update to improve prompt injection mitigation by using XML-delimited tags. Security improvement. Should Have for v3.2.0. **Milestone:** v3.2.0 **Priority:** Medium --- **Automated by CleverAgents Bot** Supervisor: Project Owner | Agent: project-owner-pool-supervisor
HAL9001 requested changes 2026-04-15 07:21:43 +00:00
HAL9001 left a comment
Copy link

Code Review: REQUEST CHANGES

Summary

This PR updates docs/specification.md to replace [USER_CONTENT_START]/[USER_CONTENT_END] bracket markers with XML-delimited tags for prompt injection mitigation. The content change itself is correct and well-written. However, several process/compliance requirements from CONTRIBUTING.md are not met.

✅ What Looks Good

  1. CI passes — All CI checks passed (run #18313).
  2. Content correctness — The spec change accurately reflects the implementation (commit d3cb534c, PR #1175). The new text correctly documents:
    • XML-delimited tags as the canonical approach
    • The sanitization requirement (escaping <, >, &)
    • Cross-reference to _sanitize_xml_content() as the reference implementation
    • Prevention of injection via forged closing tags
  3. Commit message format — docs(spec): ... follows Conventional Changelog type(scope) format.
  4. PR description — Detailed and well-structured with motivation and related issue.
  5. Closes keyword — Closes #9522 is present in the PR body.

❌ Issues Requiring Changes

1. Missing Milestone Assignment

The PR has no milestone assigned. The linked issue #9522 is assigned to v3.2.0, and the triage comment explicitly states "Should Have for v3.2.0". The PR must be assigned to the v3.2.0 milestone.

2. Missing Type/ Label

The PR only has the Needs Feedback label. Per CONTRIBUTING.md, every PR must have exactly one Type/ label. For a pure documentation change, Type/Documentation should be applied.

3. Missing Changelog Update

CONTRIBUTING.md requires a changelog update for PRs. No changelog file was modified in this PR (only docs/specification.md was changed).

4. Missing CONTRIBUTORS.md Entry

CONTRIBUTING.md requires a CONTRIBUTORS.md entry for each PR. This file was not updated.

5. Commit Message: Missing ISSUES CLOSED: Format

The commit body uses Closes #9522 but CONTRIBUTING.md specifies the format should be ISSUES CLOSED: #N in the commit body. Please update the commit message to include:

ISSUES CLOSED: #9522

6. Incomplete Acceptance Criteria — Other Occurrences Not Checked

Issue #9522 acceptance criteria includes: "Any other spec sections referencing [USER_CONTENT_START]/[USER_CONTENT_END] are updated for consistency." The diff only shows 1 line changed. Please verify there are no other occurrences of [USER_CONTENT_START] or [USER_CONTENT_END] remaining in docs/specification.md and confirm this in the PR description.

Required Actions

  • Assign milestone v3.2.0 to this PR
  • Add Type/Documentation label
  • Add changelog entry
  • Add CONTRIBUTORS.md entry
  • Update commit message to use ISSUES CLOSED: #9522 format
  • Verify and confirm no other occurrences of [USER_CONTENT_START]/[USER_CONTENT_END] remain in the spec

Automated by CleverAgents Bot
Supervisor: PR Review Pool | Agent: pr-reviewer
Worker: [AUTO-REV-9566]

## Code Review: REQUEST CHANGES ### Summary This PR updates `docs/specification.md` to replace `[USER_CONTENT_START]/[USER_CONTENT_END]` bracket markers with XML-delimited tags for prompt injection mitigation. The content change itself is correct and well-written. However, several process/compliance requirements from CONTRIBUTING.md are not met. --- ### ✅ What Looks Good 1. **CI passes** — All CI checks passed (run #18313). 2. **Content correctness** — The spec change accurately reflects the implementation (commit `d3cb534c`, PR #1175). The new text correctly documents: - XML-delimited tags as the canonical approach - The sanitization requirement (escaping `<`, `>`, `&`) - Cross-reference to `_sanitize_xml_content()` as the reference implementation - Prevention of injection via forged closing tags 3. **Commit message format** — `docs(spec): ...` follows Conventional Changelog type(scope) format. 4. **PR description** — Detailed and well-structured with motivation and related issue. 5. **Closes keyword** — `Closes #9522` is present in the PR body. --- ### ❌ Issues Requiring Changes #### 1. Missing Milestone Assignment The PR has **no milestone assigned**. The linked issue #9522 is assigned to `v3.2.0`, and the triage comment explicitly states "Should Have for v3.2.0". The PR must be assigned to the `v3.2.0` milestone. #### 2. Missing Type/ Label The PR only has the `Needs Feedback` label. Per CONTRIBUTING.md, every PR must have **exactly one `Type/` label**. For a pure documentation change, `Type/Documentation` should be applied. #### 3. Missing Changelog Update CONTRIBUTING.md requires a changelog update for PRs. No changelog file was modified in this PR (only `docs/specification.md` was changed). #### 4. Missing CONTRIBUTORS.md Entry CONTRIBUTING.md requires a `CONTRIBUTORS.md` entry for each PR. This file was not updated. #### 5. Commit Message: Missing `ISSUES CLOSED:` Format The commit body uses `Closes #9522` but CONTRIBUTING.md specifies the format should be `ISSUES CLOSED: #N` in the commit body. Please update the commit message to include: ``` ISSUES CLOSED: #9522 ``` #### 6. Incomplete Acceptance Criteria — Other Occurrences Not Checked Issue #9522 acceptance criteria includes: *"Any other spec sections referencing `[USER_CONTENT_START]/[USER_CONTENT_END]` are updated for consistency."* The diff only shows 1 line changed. Please verify there are no other occurrences of `[USER_CONTENT_START]` or `[USER_CONTENT_END]` remaining in `docs/specification.md` and confirm this in the PR description. --- ### Required Actions - [ ] Assign milestone `v3.2.0` to this PR - [ ] Add `Type/Documentation` label - [ ] Add changelog entry - [ ] Add CONTRIBUTORS.md entry - [ ] Update commit message to use `ISSUES CLOSED: #9522` format - [ ] Verify and confirm no other occurrences of `[USER_CONTENT_START]/[USER_CONTENT_END]` remain in the spec --- **Automated by CleverAgents Bot** Supervisor: PR Review Pool | Agent: pr-reviewer Worker: [AUTO-REV-9566]
HAL9001 commented 2026-04-15 07:22:24 +00:00
Owner
Copy link

Code Review Decision: REQUEST CHANGES

This PR correctly updates the spec content but is missing several CONTRIBUTING.md compliance requirements:

  1. Missing milestone — PR must be assigned to v3.2.0 (matching the linked issue #9522)
  2. Missing Type/ label — Needs Type/Documentation label (currently only has Needs Feedback)
  3. Missing changelog update — No changelog file was modified
  4. Missing CONTRIBUTORS.md entry — Not updated
  5. Commit message format — Should use ISSUES CLOSED: #9522 instead of Closes #9522
  6. Incomplete acceptance criteria — Need to verify no other occurrences of [USER_CONTENT_START]/[USER_CONTENT_END] remain in the spec

CI ✅ passes. The spec content change itself is correct and well-written.

See the formal review for full details.

Automated by CleverAgents Bot
Supervisor: PR Review Pool | Agent: pr-reviewer
Worker: [AUTO-REV-9566]

**Code Review Decision: REQUEST CHANGES** This PR correctly updates the spec content but is missing several CONTRIBUTING.md compliance requirements: 1. **Missing milestone** — PR must be assigned to `v3.2.0` (matching the linked issue #9522) 2. **Missing Type/ label** — Needs `Type/Documentation` label (currently only has `Needs Feedback`) 3. **Missing changelog update** — No changelog file was modified 4. **Missing CONTRIBUTORS.md entry** — Not updated 5. **Commit message format** — Should use `ISSUES CLOSED: #9522` instead of `Closes #9522` 6. **Incomplete acceptance criteria** — Need to verify no other occurrences of `[USER_CONTENT_START]/[USER_CONTENT_END]` remain in the spec CI ✅ passes. The spec content change itself is correct and well-written. See the formal review for full details. --- **Automated by CleverAgents Bot** Supervisor: PR Review Pool | Agent: pr-reviewer Worker: [AUTO-REV-9566]
HAL9000 added this to the v3.2.0 milestone 2026-04-15 15:29:38 +00:00
HAL9000 commented 2026-04-15 15:31:13 +00:00
Author
Owner
Copy link

[GROOMED] Quality analysis complete.

Checks Performed

  • Labels: Required Type/Documentation, State/In Review, Priority/Medium, and MoSCoW/Should have are still missing. Multiple forgejo-label-manager attempts failed because the environment lacks the approved label-write tool, so manual application is still needed.
  • Milestone: Assigned to v3.2.0 to match the linked issue.
  • Reviews: HAL9001 review (ID 5786) remains in REQUEST_CHANGES status.
  • Linked issues: Issue #9522 remains open and referenced via the PR description (Closes #9522).

Fixes Applied

  • Added milestone v3.2.0.

Remaining Issues (Require PR Author Action)

  • Apply the required labels (Type/Documentation, State/In Review, Priority/Medium, MoSCoW/Should have) alongside the existing Needs Feedback label.
  • Add the missing changelog update referenced in the review.
  • Add the CONTRIBUTORS.md entry requested in the review.
  • Update the commit message format to include "ISSUES CLOSED: #9522".
  • Respond to HAL9001's acceptance-criteria questions and provide any outstanding verification or testing evidence.

Automated by CleverAgents Bot
Supervisor: Grooming | Agent: grooming-pool-supervisor

[GROOMED] Quality analysis complete. ## Checks Performed - Labels: Required Type/Documentation, State/In Review, Priority/Medium, and MoSCoW/Should have are still missing. Multiple forgejo-label-manager attempts failed because the environment lacks the approved label-write tool, so manual application is still needed. - Milestone: Assigned to **v3.2.0** to match the linked issue. - Reviews: HAL9001 review (ID 5786) remains in REQUEST_CHANGES status. - Linked issues: Issue #9522 remains open and referenced via the PR description (Closes #9522). ## Fixes Applied - Added milestone v3.2.0. ## Remaining Issues (Require PR Author Action) - Apply the required labels (Type/Documentation, State/In Review, Priority/Medium, MoSCoW/Should have) alongside the existing Needs Feedback label. - Add the missing changelog update referenced in the review. - Add the CONTRIBUTORS.md entry requested in the review. - Update the commit message format to include "ISSUES CLOSED: #9522". - Respond to HAL9001's acceptance-criteria questions and provide any outstanding verification or testing evidence. --- **Automated by CleverAgents Bot** Supervisor: Grooming | Agent: grooming-pool-supervisor
freemo closed this pull request 2026-04-15 15:46:42 +00:00
All checks were successful
CI / push-validation (pull_request) Successful in 24s
Details
CI / helm (pull_request) Successful in 25s
Details
CI / build (pull_request) Successful in 26s
Required
Details
CI / quality (pull_request) Successful in 34s
Required
Details
CI / lint (pull_request) Successful in 45s
Required
Details
CI / security (pull_request) Successful in 1m2s
Required
Details
CI / typecheck (pull_request) Successful in 1m14s
Required
Details
CI / e2e_tests (pull_request) Successful in 3m42s
Details
CI / integration_tests (pull_request) Successful in 4m3s
Required
Details
CI / unit_tests (pull_request) Successful in 5m11s
Required
Details
CI / docker (pull_request) Successful in 58s
Required
Details
CI / coverage (pull_request) Successful in 13m5s
Required
Details
CI / status-check (pull_request) Successful in 2s
Details

Pull request closed

Please reopen this pull request to perform a merge.
Sign in to join this conversation.
Reviewers
No reviewers
HAL9001
Labels
Clear labels   
auto/needs-reevaluation
Controller deferred this PR; awaiting Phase 6+ scope-evaluator or operator re-enablement.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

  
auto/needs-implementer
Failing CI needs implementer attention.

  
auto/postmortem
Documenting a driver incident or rollback.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

  
Priority
Critical
 The priority is critical

  
Priority
High
 The priority is high

  
Priority
Low
 The priority is low

  
Priority
Medium
 The priority is medium

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

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

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

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

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

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

  
State
In Progress
 A ticket that is actively being developed.

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

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

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

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

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

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

  
Type
Bug
 Something that doesnt work as intended.

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

  
Type
Documentation
 An error or improvement needed in the documentation.

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

  
Type
Feature
 Some new functionality not present.

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

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

  
Type
Support
 Someone needs help using the project.

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

  
Type
Testing
 Work exclusively focusing on fixing or expanding testing.

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

No due date set.

Dependencies

No dependencies set.

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