feat: add category-driven ticket workflows

backend/apps/tickets/schemas.py

@@ -6,7 +6,12 @@ from ninja import Schema
 class TicketIn(Schema):
     title: str
     description: str
+    category_code: str | None = None
     priority: str = "medium"
+    problem_performance: str = ""
+    problem_object: str = ""
+    submitter_name: str = ""
+    submitter_org: str = ""
     impact_scope: str = ""
     environment: str = ""
     related_system: str = ""
@@ -16,7 +21,15 @@ class TicketIn(Schema):
 class TicketUpdateIn(Schema):
     title: str | None = None
     description: str | None = None
+    category_code: str | None = None
     priority: str | None = None
+    problem_performance: str | None = None
+    problem_object: str | None = None
+    submitter_name: str | None = None
+    submitter_org: str | None = None
+    resolution: str | None = None
+    is_resolved: bool | None = None
+    replied_to_customer: bool | None = None
     impact_scope: str | None = None
     environment: str | None = None
     related_system: str | None = None
@@ -26,6 +39,9 @@ class TicketUpdateIn(Schema):
 class TicketStatusIn(Schema):
     status: str
     remark: str = ""
+    resolution: str = ""
+    is_resolved: bool | None = None
+    replied_to_customer: bool | None = None
 
 
 class TicketUserOut(Schema):
@@ -34,13 +50,30 @@ class TicketUserOut(Schema):
     display_name: str
 
 
+class TicketCategoryOut(Schema):
+    id: int
+    code: str
+    name: str
+    description: str
+
+
 class TicketOut(Schema):
     id: int
     ticket_no: str
     title: str
     description: str
+    category: TicketCategoryOut | None = None
+    category_code: str | None = None
     status: str
     priority: str
+    problem_performance: str
+    problem_object: str
+    submitter_name: str
+    submitter_org: str
+    ai_solution: str
+    resolution: str
+    is_resolved: bool
+    replied_to_customer: bool
     impact_scope: str
     environment: str
     related_system: str