Hermes 284313f908
Some checks are pending
Bidi Control Character Guard / bidi-control-guard (push) Waiting to run
Circular Dependency Check / Check for new circular dependencies (push) Waiting to run
Citus Migration Smoke / Combined migrations on single-node Citus (push) Waiting to run
E2E Fresh Install Tests / fresh-install-e2e (push) Waiting to run
ext-v2 guardrails / Run ext-v2 guard and ESLint (push) Waiting to run
Integration Tests / Check for relevant changes (push) Waiting to run
Integration Tests / ${{ (github.event_name == 'schedule' || github.event.inputs.suite == 'full') && 'Full integration suite' || 'Tier-1 integration subset' }} (push) Blocked by required conditions
Mobile checks / Mobile lint + typecheck (push) Waiting to run
Mobile checks / Mobile unit tests (push) Waiting to run
Mobile checks / Mobile dependency audit (report) (push) Waiting to run
Mobile checks / Mobile reproducibility checks (push) Waiting to run
Secrets guard (env backups) / Ensure no tracked env backup files (push) Waiting to run
Temporal Readiness / fast-readiness (push) Waiting to run
Temporal Readiness / docker-parity (push) Waiting to run
TypeScript Type Check / Nx affected typecheck (push) Waiting to run
Unit Tests / Skipped-test budget (push) Waiting to run
Unit Tests / Nx affected unit tests (push) Waiting to run
Unit Tests / Server unit coverage (informational) (push) Waiting to run
Validate Tenant Management Schema / Check for relevant changes (push) Waiting to run
Validate Tenant Management Schema / Validate Tenant Management Schema (push) Blocked by required conditions
EE Workflows Build Guard / ee-workflows-build-guard (push) Waiting to run
Initial import of AlgaPSA codebase from PSA server
Excluded: .git, node_modules, secrets/, compose.env, assemblyscript tgz

Source: /opt/alga-psa on psa.joliet.tech
2026-06-22 16:12:17 -05:00

105 lines
4.0 KiB
JSON

[
{
"id": "F001",
"description": "Persist per-board inbound reopen policy fields for enablement, cutoff duration, optional reopen status, and AI acknowledgement suppression.",
"implemented": true,
"prdRefs": ["Requirements", "Data / API / Integrations"]
},
{
"id": "F002",
"description": "Expose board settings UI and server actions for editing inbound reopen policy using board-owned ticket statuses.",
"implemented": true,
"prdRefs": ["UX / UI Notes", "Requirements"]
},
{
"id": "F003",
"description": "Load matched ticket board policy during inbound reply handling before comment creation.",
"implemented": true,
"prdRefs": ["Requirements"]
},
{
"id": "F004",
"description": "When reopen-on-reply is disabled for a board, attach threaded replies to closed tickets without reopening.",
"implemented": true,
"prdRefs": ["Requirements"]
},
{
"id": "F005",
"description": "Apply the per-board cutoff window so replies older than the configured threshold bypass closed-ticket attachment and enter the new-ticket path.",
"implemented": true,
"prdRefs": ["Goals", "Requirements"]
},
{
"id": "F006",
"description": "Always reopen matched closed tickets for internal-user replies that fall within the cutoff window.",
"implemented": true,
"prdRefs": ["Goals", "Requirements"]
},
{
"id": "F007",
"description": "Reopen matched closed tickets for client/contact replies within the cutoff window when AI suppression is disabled or not applicable.",
"implemented": true,
"prdRefs": ["Goals", "Requirements"]
},
{
"id": "F008",
"description": "Resolve reopen target status from board `reopen_status_id` and fall back to the board default open status when unset.",
"implemented": true,
"prdRefs": ["Goals", "Requirements"]
},
{
"id": "F009",
"description": "Apply reopen transitions using existing ticket status semantics so `status_id`, `is_closed`, `closed_at`, and `closed_by` stay aligned.",
"implemented": true,
"prdRefs": ["Requirements"]
},
{
"id": "F010",
"description": "Preserve existing inbound dedupe and token-only self-notification skipping before reopen decisions execute.",
"implemented": true,
"prdRefs": ["Requirements"]
},
{
"id": "F011",
"description": "Introduce a shared acknowledgement-decision interface with a default non-AI implementation that never suppresses reopen.",
"implemented": true,
"prdRefs": ["Requirements", "Security / Permissions"]
},
{
"id": "F012",
"description": "Provide an EE acknowledgement-decision implementation behind manual edition-aware resolution so AI logic stays isolated in `@ee/...` code.",
"implemented": true,
"prdRefs": ["Requirements", "Security / Permissions"]
},
{
"id": "F013",
"description": "Require both board AI suppression enablement and tenant `AI Assistant` entitlement before any acknowledgement LLM call.",
"implemented": true,
"prdRefs": ["Requirements", "Security / Permissions"]
},
{
"id": "F014",
"description": "Use the standard LLM path with a minimal prompt and tiny formatted output such as `ACK` or `NOT_ACK` for short acknowledgement-like client replies.",
"implemented": true,
"prdRefs": ["Requirements", "Data / API / Integrations"]
},
{
"id": "F015",
"description": "Treat `ACK` client replies as comment-only updates that keep the ticket closed.",
"implemented": true,
"prdRefs": ["Requirements"]
},
{
"id": "F016",
"description": "Treat invalid AI output, missing EE code, missing entitlement, or AI runtime errors as reopen-normal fallback behavior.",
"implemented": true,
"prdRefs": ["Non-functional Requirements", "Acceptance Criteria (Definition of Done)"]
},
{
"id": "F017",
"description": "Record decision metadata sufficient to explain reopen, cutoff, and AI suppression outcomes during debugging.",
"implemented": true,
"prdRefs": ["Non-functional Requirements", "Observability"]
}
]