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
Excluded: .git, node_modules, secrets/, compose.env, assemblyscript tgz Source: /opt/alga-psa on psa.joliet.tech
37 lines
2.0 KiB
Markdown
37 lines
2.0 KiB
Markdown
# Scratchpad — Ticket Bundling
|
|
|
|
## Links / Context
|
|
|
|
- Mockup: merge/bundle modal + ticket list bundling toggle (provided in prompt)
|
|
- Architecture overview: `docs/architecture/overview.md`
|
|
- Ticket UI: `server/src/components/tickets/TicketingDashboardContainer.tsx`, `server/src/components/tickets/ticket/TicketDetails.tsx`
|
|
- Ticket model: `server/src/lib/models/ticket.tsx`
|
|
- Notification system: `server/src/lib/notifications/email.ts`
|
|
|
|
## Working Notes
|
|
|
|
- Existing UI mock uses “Merge Tickets” language and includes a checkbox to “Link Child Tickets to Master & Sync Updates” — plan treats this as a mode selector with sensible defaults and tenant policy overrides.
|
|
- Proposed schema for MVP keeps bundling simple via `tickets.master_ticket_id` + `ticket_bundle_settings` keyed by master ticket to store bundle-level behavior.
|
|
|
|
## Decisions (Draft)
|
|
|
|
- Prefer “bundle” semantics over destructive merges: child tickets remain addressable and retain source/requester context.
|
|
- UI terminology: **Bundle**.
|
|
- Default mode: **sync_updates**.
|
|
- Child workflow fields (status/assignment/priority): **locked by default**.
|
|
- Default customer notification scope for master public updates: **all child requesters**.
|
|
- Bundle membership: allow cross-client bundling within a tenant (e.g., outage bundles); UI should warn/indicate “multiple clients”.
|
|
- Inbound child replies surface on master as **view-only** (aggregated), not duplicated onto the master ticket.
|
|
- Sync updates do **not** include internal notes (internal notes stay on master).
|
|
- On bundle creation, children keep their current status; workflow fields are locked by default.
|
|
- De-duplicate internal notifications: notify on master event, not on each mirrored child event.
|
|
|
|
## Open Questions (Needs Answers)
|
|
|
|
- Should “reopen on reply” reopen only the master or also the child ticket(s)?
|
|
- For cross-client bundles, should “Email all affected requesters” require an extra confirmation step by default?
|
|
|
|
## Commands
|
|
|
|
- Validate plan JSON: `python scripts/validate_plan.py ee/docs/plans/2026-01-04-ticket-bundling`
|