Skip to content

12.4 Ticket Service - Scaffold and Schema

Sprint: Sprint 12 - Notifications and Ticketing
Feature ID: 12.4
Subtasks: 12.4.1, 12.4.2

Objective

Deliver "Ticket Service - Scaffold and Schema" within Sprint 12 - Notifications and Ticketing.

Dependencies

Aggregated from the subtasks below (prerequisite task IDs and enablers):

  • 3.4.1
  • Sprint 04
  • 12.4.1

Subtasks

12.4.1 Scaffold ticket-service from template

  • ID: 12.4.1
  • Title: Create ticket-service from the service template
  • Description: Instantiate microservices/ticket-service (port 9010, base package com.telco.ticket) from the template; depend on starter-api, starter-security, starter-mediator, starter-observability, starter-outbox, starter-inbox; own the ticket database; CQRS+Mediator.
  • Business Purpose: Standardized ticket-domain service skeleton.
  • Inputs: ADR-017.
  • Outputs: ticket-service skeleton building and registering.
  • Acceptance Criteria:
  • Service starts, registers, exposes Swagger UI.
  • Dependencies: 3.4.1, Sprint 04
  • Complexity: S

12.4.2 Ticket schema migration

  • ID: 12.4.2
  • Title: Create Flyway migration for tickets, comments, SLA
  • Description: V1__ticket.sql creating tickets (id, customer_id, category, priority, status, assigned_team, sla_due_at, created_at, resolved_at), ticket_comments (id, ticket_id, author_id, body, created_at), and an sla_policies table (category, priority, resolution_minutes, team), plus outbox/inbox tables.
  • Business Purpose: Persist tickets, comments, and SLA policies (FR-31, FR-32).
  • Inputs: analysis Section 10.9, FR-31, FR-32.
  • Outputs: Flyway migration.
  • Acceptance Criteria:
  • Migration applies; ticket status supports OPEN/ASSIGNED/RESOLVED; SLA policies map category/ priority to a team and resolution target.
  • Dependencies: 12.4.1
  • Complexity: M

Acceptance Criteria

Each subtask above carries its own objective, testable acceptance criteria. This feature is complete when every subtask's acceptance criteria are met.

Deliverables

  • ticket-service skeleton building and registering.
  • Flyway migration.

Definition of Done

  • All subtasks (12.4.1, 12.4.2) completed and their acceptance criteria verified.
  • All listed dependencies satisfied.
  • Build and tests green per the global conventions in ../README.md (Section 3).