fix(tickets): resolve 500/422 errors by correcting response schema, timezone handling, and route ordering

docs/agent/thoughts/frontend.md

@@ -1,433 +1,731 @@
-# Frontend Team - Navigation & App Context Requirements
+# Ticketing System - Frontend Integration Guide
 
-**Date:** 2025-11-21  
-**Topic:** Project Selection & Context-Aware App Navigation  
-**Status:** Pending Backend Implementation
+Quick reference for PM, Sales Manager, and Dispatcher ticket management.
 
 ---
 
-## Problem Statement
+## User Roles & Permissions
 
-We've implemented a project selection system for project-based roles (Project Manager, Sales Manager, Dispatcher, Field Agent). These users now have two distinct contexts:
+| Role | View Tickets | Create Tickets | Assign Tickets | View Expenses | Approve Expenses |
+|------|--------------|----------------|----------------|---------------|------------------|
+| **Platform Admin** | All | ✓ | ✓ | All | ✓ |
+| **Project Manager** | Their projects | ✓ | ✓ | Their projects | ✓ |
+| **Dispatcher** | Contractor's projects | ✓ | ✓ | Contractor's projects | ✓ |
+| **Sales Manager** | Their client's projects | View only | ✗ | View only | ✗ |
 
-1. **Outside Project Context**: `/dashboard` - Project selection view
-2. **Inside Project Context**: `/project/:projectId` - Project-specific dashboard
+---
 
-Currently, the navigation system shows all available apps regardless of context. This creates a poor UX because:
-- Users see project-specific apps (Tickets, Inventory, Map, etc.) when they're on the project selection screen
-- These apps are not functional without a project context
-- It's confusing and cluttered
+## Ticket Basics
 
-## Proposed Solution
+### Ticket Types
+- **installation** - New customer service setup (from sales orders)
+- **support** - Fix existing customer issues (from incidents)
+- **infrastructure** - Project rollout work (from tasks)
 
-We need the **backend to provide context-aware app lists** based on user role and current context.
+### Ticket Status Flow
+```
+open → assigned → in_progress → pending_review → completed
+                                              ↘ cancelled
+```
 
----
+### Ticket Sources
+- **sales_order** - Customer wants new service
+- **incident** - Customer has problem with existing service
+- **task** - Infrastructure work needed
 
-## Backend API Requirements
+### Priority Levels
+`urgent` > `high` > `normal` > `low`
 
-### Current API Response Structure
-```json
-GET /api/v1/users/me/preferences
+---
 
-{
-  "available_apps": [
-    { "code": "dashboard", "name": "Dashboard", "route": "/dashboard" },
-    { "code": "tickets", "name": "Tickets", "route": "/tickets" },
-    { "code": "settings", "name": "Settings", "route": "/settings" },
-    // ... all apps
-  ],
-  "current_favorites": ["dashboard", "tickets", "inventory"],
-  "default_favorites": ["dashboard", "tickets", "map"]
-}
+## Core Endpoints
+
+### 1. List Tickets
+```http
+GET /api/v1/tickets?skip=0&limit=50
 ```
 
-### Proposed API Response Structure
+**Query Params:**
+- `project_id` (UUID) - Filter by project
+- `status` (enum) - open, assigned, in_progress, pending_review, completed, cancelled
+- `ticket_type` (enum) - installation, support, infrastructure
+- `priority` (enum) - urgent, high, normal, low
+- `project_region_id` (UUID) - Filter by region
+- `source` (enum) - sales_order, incident, task
+- `from_date` (date) - Created after (YYYY-MM-DD)
+- `to_date` (date) - Created before (YYYY-MM-DD)
+- `is_overdue` (bool) - true/false
+
+**Response:**
 ```json
-GET /api/v1/users/me/preferences
-
 {
-  "available_apps": [
-    { "code": "dashboard", "name": "Dashboard", "route": "/dashboard" },
-    { "code": "tickets", "name": "Tickets", "route": "/tickets" },
-    { "code": "inventory", "name": "Inventory", "route": "/inventory" },
-    { "code": "settings", "name": "Settings", "route": "/settings" },
-    { "code": "help", "name": "Help", "route": "/help" },
-    // ... all apps user has access to
-  ],
-  
-  "meta_apps": [
-    "dashboard",
-    "settings", 
-    "help",
-    "notifications",
-    "search"
-  ],
-  
-  "current_favorites": ["dashboard", "tickets", "inventory"],
-  "default_favorites": ["dashboard", "tickets", "map"]
+  "total": 150,
+  "skip": 0,
+  "limit": 50,
+  "tickets": [
+    {
+      "id": "uuid",
+      "project_id": "uuid",
+      "source": "sales_order",
+      "source_id": "uuid",
+      "ticket_name": "John Doe - Fiber Installation",
+      "ticket_type": "installation",
+      "service_type": "ftth",
+      "work_description": "Install fiber for customer",
+      "status": "open",
+      "priority": "normal",
+      "scheduled_date": "2024-03-20",
+      "scheduled_time_slot": "morning",
+      "due_date": "2024-03-20T17:00:00Z",
+      "sla_violated": false,
+      "is_overdue": false,
+      "project_region_id": "uuid",
+      "notes": "Customer prefers morning",
+      "created_at": "2024-03-15T10:00:00Z",
+      "updated_at": "2024-03-15T10:00:00Z",
+      "is_open": true,
+      "can_be_assigned": true
+    }
+  ]
 }
 ```
 
 ---
 
-## App Categorization by Role
-
-### For Project-Based Roles (PM, Sales Manager, Dispatcher, Field Agent)
-
-**Meta Apps** (Available outside project context):
-- `dashboard` - For returning to project selection
-- `settings` - User preferences
-- `help` - Help & support
-- `notifications` - User notifications
-- `search` - Global search (if applicable)
-
-**Project Apps** (Only available inside project context):
-- `tickets` - Work orders/tickets
-- `inventory` - Inventory management
-- `map` - Map view
-- `finance` - Financial data
-- `expenses` - Expense tracking
-- `payroll` - Payroll (if applicable)
-- `team` - Team management
-- `projects` - Project list (might be meta for some roles)
-- `reports` - Reporting
-- `customers` - Customer management
-- `documents` - Document management
-
-### For Admin Roles (Platform Admin, Client Admin, Contractor Admin)
-
-**All apps are always available** - No context switching needed.
-
-Their apps might include:
-- `dashboard` - Admin dashboard
-- `organizations` - Organization management (Platform Admin)
-- `users` - User management
-- `activity` - Activity logs
-- `billing` - Billing (Platform Admin)
-- `invitations` - User invitations
-- `team` - Team management (Org Admins)
-- `projects` - Project management (Org Admins)
-- `settings` - Settings
-- `help` - Help
+### 2. Get Single Ticket
+```http
+GET /api/v1/tickets/{ticket_id}
+```
+
+**Response:** Same as ticket object above with full details.
 
 ---
 
-## Backend Implementation Requirements
+### 3. Create Ticket from Sales Order
+```http
+POST /api/v1/tickets/from-sales-order
+```
 
-### 1. Add `meta_apps` Field to User Preferences Response
+**Request:**
+```json
+{
+  "sales_order_id": "uuid",
+  "priority": "normal",
+  "scheduled_date": "2024-03-20",
+  "scheduled_time_slot": "morning",
+  "work_description": "Install fiber for customer",
+  "notes": "Customer prefers morning visit"
+}
+```
 
-The backend should return a `meta_apps` array that lists app codes that are available **outside** of a project context.
+**Response:** Ticket object
 
-**Logic:**
-- For **project-based roles**: Return a curated list of meta apps
-- For **admin roles**: Return empty array `[]` or all apps (since they don't have context switching)
+**Rules:**
+- Sales order must be `pending` status
+- One sales order = one active ticket (prevents duplicates)
+- If cancelled ticket exists, it gets reactivated instead
 
-### 2. Role-Based Meta Apps Configuration
+---
 
-Create a configuration mapping for each role:
+### 4. Create Ticket from Task
+```http
+POST /api/v1/tickets/from-task
+```
 
-```python
-# Example backend configuration
-META_APPS_BY_ROLE = {
-    'project_manager': ['dashboard', 'settings', 'help', 'notifications', 'search'],
-    'sales_manager': ['dashboard', 'settings', 'help', 'notifications', 'search'],
-    'dispatcher': ['dashboard', 'settings', 'help', 'notifications', 'search'],
-    'field_agent': ['dashboard', 'settings', 'help', 'notifications', 'search'],
-    
-    # Admin roles - no context switching, so empty or all apps
-    'platform_admin': [],
-    'client_admin': [],
-    'contractor_admin': [],
+**Request:**
+```json
+{
+  "task_id": "uuid",
+  "priority": "normal",
+  "scheduled_date": "2024-03-20",
+  "scheduled_time_slot": "morning",
+  "notes": "Infrastructure work"
 }
 ```
 
-### 3. Update Preferences Endpoint
+**Response:** Ticket object
 
-**Endpoint:** `GET /api/v1/users/me/preferences`
+---
+
+### 5. Create Ticket from Incident
+```http
+POST /api/v1/tickets/from-incident
+```
 
-**Response Schema:**
-```typescript
+**Request:**
+```json
 {
-  available_apps: Array<{
-    code: string;
-    name: string;
-    route: string;
-  }>;
-  
-  meta_apps: string[];  // NEW FIELD - Array of app codes available outside project context
-  
-  current_favorites: string[];
-  default_favorites: string[];
+  "incident_id": "uuid",
+  "priority": "urgent",
+  "scheduled_date": "2024-03-20",
+  "scheduled_time_slot": "morning",
+  "notes": "Customer reports no internet"
 }
 ```
 
-### 4. Validation Rules
+**Response:** Ticket object
 
-- `meta_apps` should only contain codes that exist in `available_apps`
-- For admin roles, `meta_apps` can be empty or contain all app codes
-- For project-based roles, `meta_apps` should be a subset of `available_apps`
+**Important:** Support tickets don't create new subscriptions (service already exists).
 
 ---
 
-## Frontend Implementation Plan
+### 6. Bulk Create from Sales Orders
+```http
+POST /api/v1/tickets/bulk-from-sales-orders
+```
+
+**Request:**
+```json
+{
+  "sales_order_ids": ["uuid1", "uuid2", "uuid3"],
+  "priority": "normal",
+  "notes": "Batch promotion - March installations"
+}
+```
+
+**Response:**
+```json
+{
+  "total": 3,
+  "successful": 2,
+  "failed": 1,
+  "errors": ["Sales order uuid3: Already has ticket"],
+  "created_ticket_ids": ["ticket-uuid1", "ticket-uuid2"]
+}
+```
 
-Once the backend provides `meta_apps`, we'll implement the following:
+---
 
-### 1. Detect Project Context
+### 7. Update Ticket
+```http
+PUT /api/v1/tickets/{ticket_id}
+```
 
-```typescript
-// In a new hook or context
-const location = useLocation();
-const isInProjectContext = location.pathname.startsWith('/project/');
+**Request:**
+```json
+{
+  "priority": "urgent",
+  "work_description": "Updated description",
+  "notes": "Additional notes"
+}
 ```
 
-### 2. Filter Apps in StickyHeader
+**Rules:** Can only update `open` or `assigned` tickets.
 
-```typescript
-const visibleFavoriteApps = useMemo(() => {
-  const { meta_apps } = availableApps;
-  const isProjectBasedRole = !['platform_admin', 'client_admin', 'contractor_admin'].includes(user.role);
-  
-  // If outside project context and user is project-based role
-  if (!isInProjectContext && isProjectBasedRole) {
-    // Show only meta apps from favorites
-    return accessibleFavoriteApps.filter(app => meta_apps.includes(app.code));
-  }
-  
-  // Otherwise show all favorites
-  return accessibleFavoriteApps;
-}, [isInProjectContext, user.role, accessibleFavoriteApps, availableApps.meta_apps]);
-```
-
-### 3. Filter Apps in AppLauncher
-
-```typescript
-const visibleApps = useMemo(() => {
-  const { meta_apps } = availableApps;
-  const isProjectBasedRole = !['platform_admin', 'client_admin', 'contractor_admin'].includes(user.role);
-  
-  // If outside project context and user is project-based role
-  if (!isInProjectContext && isProjectBasedRole) {
-    // Show only meta apps
-    return accessibleApps.filter(app => meta_apps.includes(app.code));
-  }
-  
-  // Otherwise show all apps
-  return accessibleApps;
-}, [isInProjectContext, user.role, accessibleApps, availableApps.meta_apps]);
+---
+
+### 8. Reschedule Ticket
+```http
+POST /api/v1/tickets/{ticket_id}/reschedule
+```
+
+**Request:**
+```json
+{
+  "scheduled_date": "2024-03-25",
+  "scheduled_time_slot": "afternoon",
+  "reason": "Customer requested later date"
+}
 ```
 
-### 4. Handle Favorites
+---
 
-**Important:** When a user is outside a project context, their favorite apps should still be **saved** but just **not displayed** if they're project apps.
+### 9. Cancel Ticket
+```http
+POST /api/v1/tickets/{ticket_id}/cancel
+```
 
-**Behavior:**
-- User sets favorites: `['dashboard', 'tickets', 'inventory', 'settings']`
-- Outside project context: Only show `['dashboard', 'settings']` (meta apps)
-- Inside project context: Show all `['dashboard', 'tickets', 'inventory', 'settings']`
+**Request:**
+```json
+{
+  "reason": "Customer cancelled service"
+}
+```
 
-This ensures when they enter a project, their favorites are immediately available.
+**Rules:** Can only cancel `open` or `assigned` tickets.
 
 ---
 
-## User Experience Flow
+### 10. Get Ticket Stats
+```http
+GET /api/v1/tickets/stats?project_id=uuid
+```
+
+**Response:**
+```json
+{
+  "total_tickets": 150,
+  "open_tickets": 20,
+  "assigned_tickets": 30,
+  "in_progress_tickets": 15,
+  "completed_tickets": 80,
+  "cancelled_tickets": 5,
+  "overdue_tickets": 3,
+  "installation_tickets": 100,
+  "support_tickets": 30,
+  "infrastructure_tickets": 20,
+  "urgent_tickets": 5,
+  "high_tickets": 15,
+  "normal_tickets": 100,
+  "low_tickets": 30,
+  "avg_completion_time_hours": 4.5,
+  "completion_rate": 53.33
+}
+```
 
-### Scenario 1: PM Logs In (Multiple Projects)
+---
 
-1. **Login** → Lands on `/dashboard` (project selection)
-2. **Header Pills**: Shows only meta apps from favorites (e.g., Dashboard, Settings)
-3. **App Launcher**: Shows only meta apps (Dashboard, Settings, Help, Notifications)
-4. **User selects project** → Navigates to `/project/abc-123`
-5. **Header Pills**: Now shows ALL favorites (Dashboard, Tickets, Inventory, Settings)
-6. **App Launcher**: Shows ALL available apps
+## Ticket Assignments
 
-### Scenario 2: PM with Single Project (Auto-Navigate)
+### 11. Assign Ticket to Agent
+```http
+POST /api/v1/ticket-assignments/tickets/{ticket_id}/assign
+```
 
-1. **Login** → Lands on `/dashboard`
-2. **Auto-navigates** to `/project/abc-123` (single project)
-3. **Header Pills**: Shows all favorites immediately
-4. **App Launcher**: Shows all apps immediately
-5. **User never sees the restricted view** (seamless experience)
+**Request:**
+```json
+{
+  "user_id": "agent-uuid",
+  "execution_order": 1,
+  "planned_start_time": "2024-03-20T09:00:00Z",
+  "notes": "Customer prefers morning visit"
+}
+```
 
-### Scenario 3: Admin Logs In
+**Response:**
+```json
+{
+  "id": "assignment-uuid",
+  "ticket_id": "ticket-uuid",
+  "user_id": "agent-uuid",
+  "assigned_by_user_id": "dispatcher-uuid",
+  "action": "assigned",
+  "execution_order": 1,
+  "planned_start_time": "2024-03-20T09:00:00Z",
+  "assigned_at": "2024-03-19T14:00:00Z",
+  "responded_at": null,
+  "journey_started_at": null,
+  "arrived_at": null,
+  "ended_at": null,
+  "is_active": true,
+  "notes": "Customer prefers morning visit"
+}
+```
 
-1. **Login** → Lands on `/dashboard` (admin dashboard)
-2. **Header Pills**: Shows all favorites (no filtering)
-3. **App Launcher**: Shows all apps (no filtering)
-4. **No context switching** - always sees everything
+**Rules:**
+- Ticket must be `open` status
+- Agent must be on project team
+- Agent capacity: max 4 active tickets
+- No duplicate assignments
 
 ---
 
-## Benefits of Backend-Driven Approach
+### 12. Assign Ticket to Team
+```http
+POST /api/v1/ticket-assignments/tickets/{ticket_id}/assign-team
+```
+
+**Request:**
+```json
+{
+  "user_ids": ["agent-a-uuid", "agent-b-uuid", "agent-c-uuid"],
+  "required_team_size": 3,
+  "notes": "Infrastructure team for pole installation"
+}
+```
 
-### 1. **Centralized Logic**
-- App categorization lives in one place (backend)
-- Easy to update which apps are meta vs project-specific
-- No hardcoded lists in frontend
+**Response:**
+```json
+{
+  "ticket_id": "ticket-uuid",
+  "assignments": [
+    { "id": "assignment-1-uuid", "user_id": "agent-a-uuid" },
+    { "id": "assignment-2-uuid", "user_id": "agent-b-uuid" },
+    { "id": "assignment-3-uuid", "user_id": "agent-c-uuid" }
+  ],
+  "required_team_size": 3,
+  "successful": 3,
+  "failed": 0
+}
+```
 
-### 2. **Role Flexibility**
-- Different roles can have different meta apps
-- Easy to add new roles with custom meta app lists
-- Backend controls access, frontend just displays
+**Team Rules:**
+- Any team member can complete the ticket
+- Completing closes ALL active assignments
+- All agents must have capacity
 
-### 3. **Consistency**
-- Same logic applies to all frontend components
-- No risk of frontend/backend mismatch
-- Single source of truth
+---
 
-### 4. **Scalability**
-- Easy to add new app types in the future
-- Can introduce more context levels if needed
-- Frontend code stays simple
+### 13. Get Ticket Assignments
+```http
+GET /api/v1/ticket-assignments/tickets/{ticket_id}/assignments
+```
 
-### 5. **Security**
-- Backend enforces what apps are available
-- Frontend can't accidentally show unauthorized apps
-- Access control remains server-side
+**Response:**
+```json
+{
+  "current_assignments": [
+    {
+      "id": "uuid",
+      "user_id": "agent-uuid",
+      "user_name": "John Agent",
+      "assigned_at": "2024-03-19T14:00:00Z",
+      "responded_at": "2024-03-19T14:30:00Z",
+      "journey_started_at": "2024-03-20T08:00:00Z",
+      "arrived_at": "2024-03-20T09:15:00Z",
+      "is_active": true
+    }
+  ],
+  "past_assignments": [
+    {
+      "id": "uuid",
+      "user_id": "previous-agent-uuid",
+      "user_name": "Previous Agent",
+      "assigned_at": "2024-03-18T10:00:00Z",
+      "ended_at": "2024-03-18T11:00:00Z",
+      "action": "dropped",
+      "is_active": false
+    }
+  ]
+}
+```
 
 ---
 
-## Migration & Backward Compatibility
+### 14. Get Agent's Work Queue
+```http
+GET /api/v1/ticket-assignments/users/{user_id}/assignment-queue
+```
+
+**Response:**
+```json
+{
+  "user_id": "agent-uuid",
+  "active_count": 3,
+  "max_capacity": 4,
+  "can_accept_more": true,
+  "assignments": [
+    {
+      "id": "assignment-uuid",
+      "ticket_id": "ticket-uuid",
+      "ticket_name": "John Doe - Installation",
+      "execution_order": 1,
+      "planned_start_time": "2024-03-20T09:00:00Z",
+      "priority": "high"
+    }
+  ]
+}
+```
+
+---
 
-### Phase 1: Backend Update
-- Add `meta_apps` field to preferences response
-- Populate based on user role
-- Ensure existing fields remain unchanged
+## Ticket Expenses
 
-### Phase 2: Frontend Update
-- Update `useUserPreferences` types to include `meta_apps`
-- Implement filtering logic in StickyHeader
-- Implement filtering logic in AppLauncher
-- Add context detection
+### 15. Get Ticket Expenses
+```http
+GET /api/v1/ticket-expenses?ticket_id=uuid
+```
 
-### Phase 3: Testing
-- Test all role types
-- Test project context switching
-- Test favorite app persistence
-- Test edge cases (direct URLs, bookmarks)
+**Response:**
+```json
+{
+  "expenses": [
+    {
+      "id": "expense-uuid",
+      "ticket_id": "ticket-uuid",
+      "ticket_assignment_id": "assignment-uuid",
+      "incurred_by_user_id": "agent-uuid",
+      "incurred_by_user_name": "John Agent",
+      "category": "transport",
+      "description": "Taxi fare to customer site",
+      "quantity": 1,
+      "unit": "trip",
+      "unit_cost": 500.00,
+      "total_cost": 500.00,
+      "receipt_document_id": "doc-uuid",
+      "is_approved": false,
+      "is_paid": false,
+      "location_verified": true,
+      "notes": "Shared with 2 team members",
+      "created_at": "2024-03-20T10:00:00Z"
+    }
+  ],
+  "total": 1,
+  "page": 1,
+  "page_size": 50,
+  "pages": 1
+}
+```
 
-### Backward Compatibility
-- If `meta_apps` is missing or empty, show all apps (current behavior)
-- No breaking changes for existing users
-- Gradual rollout possible
+**Expense Categories:**
+- `transport` - Travel costs
+- `materials` - Materials purchased
+- `meals` - Food/drinks
+- `accommodation` - Lodging
+- `other` - Other expenses
 
 ---
 
-## Open Questions for Backend Team
+### 16. Approve/Reject Expense
+```http
+POST /api/v1/ticket-expenses/{expense_id}/approve
+```
 
-1. **Should `meta_apps` be role-based or user-specific?**
-   - Recommendation: Role-based for consistency, but allow user overrides if needed
+**Request:**
+```json
+{
+  "is_approved": true,
+  "rejection_reason": null
+}
+```
 
-2. **Should `projects` app be meta or project-specific?**
-   - For PM: Probably meta (they manage multiple projects)
-   - For Field Agent: Probably project-specific (they work in one project at a time)
+**Or reject:**
+```json
+{
+  "is_approved": false,
+  "rejection_reason": "Receipt not clear, please resubmit"
+}
+```
 
-3. **Should `dashboard` always be in meta apps?**
-   - Yes - users need a way to return to project selection
+---
 
-4. **How to handle apps that work in both contexts?**
-   - Example: `search` might work globally or within a project
-   - Recommendation: If it works outside project, include in meta apps
+### 17. Get Expense Stats
+```http
+GET /api/v1/ticket-expenses/stats?ticket_id=uuid
+```
 
-5. **Should we support per-user customization of meta apps?**
-   - Or is role-based sufficient?
-   - Recommendation: Start with role-based, add user customization later if needed
+**Response:**
+```json
+{
+  "total_expenses": 25,
+  "total_amount": 12500.00,
+  "approved_count": 20,
+  "approved_amount": 10000.00,
+  "pending_count": 3,
+  "pending_amount": 1500.00,
+  "rejected_count": 2,
+  "rejected_amount": 1000.00,
+  "paid_count": 15,
+  "paid_amount": 7500.00,
+  "by_category": {
+    "transport": 5000.00,
+    "materials": 4000.00,
+    "meals": 1500.00
+  }
+}
+```
 
 ---
 
-## Example API Responses by Role
+## Ticket Images/Photos
+
+### 18. Get Ticket Equipment
+```http
+GET /api/v1/tickets/{ticket_id}/equipment
+```
 
-### Project Manager
+**Response:**
 ```json
+[
+  {
+    "id": "uuid",
+    "unit_identifier": "HW12345678",
+    "equipment_type": "ONT",
+    "equipment_name": "Huawei HG8145V5",
+    "status": "installed",
+    "issued_at": "2025-11-15T08:00:00Z",
+    "installed_at": "2025-11-15T14:30:00Z",
+    "agent_name": "John Technician",
+    "agent_id": "agent-uuid"
+  }
+]
+```
+
+---
+
+## Database Models
+
+### Ticket Model
+```python
 {
-  "available_apps": [
-    { "code": "dashboard", "name": "Dashboard", "route": "/dashboard" },
-    { "code": "tickets", "name": "Tickets", "route": "/tickets" },
-    { "code": "inventory", "name": "Inventory", "route": "/inventory" },
-    { "code": "map", "name": "Map", "route": "/map" },
-    { "code": "finance", "name": "Finance", "route": "/finance" },
-    { "code": "team", "name": "Team", "route": "/team" },
-    { "code": "reports", "name": "Reports", "route": "/reports" },
-    { "code": "settings", "name": "Settings", "route": "/settings" },
-    { "code": "help", "name": "Help", "route": "/help" },
-    { "code": "notifications", "name": "Notifications", "route": "/notifications" }
-  ],
-  "meta_apps": ["dashboard", "settings", "help", "notifications"],
-  "current_favorites": ["dashboard", "tickets", "inventory", "map"],
-  "default_favorites": ["dashboard", "tickets", "inventory", "map"]
+  "id": UUID,
+  "project_id": UUID,
+  "source": "sales_order" | "incident" | "task",
+  "source_id": UUID,
+  "ticket_name": str,
+  "ticket_type": "installation" | "support" | "infrastructure",
+  "service_type": "ftth" | "fixed_wireless" | "dsl" | etc,
+  "work_description": str,
+  "status": "open" | "assigned" | "in_progress" | "pending_review" | "completed" | "cancelled",
+  "priority": "low" | "normal" | "high" | "urgent",
+  "scheduled_date": date,
+  "scheduled_time_slot": str,
+  "due_date": datetime,
+  "sla_target_date": datetime,
+  "sla_violated": bool,
+  "started_at": datetime,
+  "completed_at": datetime,
+  "is_invoiced": bool,
+  "project_region_id": UUID,
+  "work_location_latitude": decimal,
+  "work_location_longitude": decimal,
+  "work_location_verified": bool,
+  "dedup_key": str,  // Permanent unique identifier
+  "required_team_size": int,
+  "notes": str,
+  "version": int,  // Optimistic locking
+  "created_at": datetime,
+  "updated_at": datetime
 }
 ```
 
-### Platform Admin
-```json
+### TicketAssignment Model
+```python
 {
-  "available_apps": [
-    { "code": "dashboard", "name": "Dashboard", "route": "/dashboard" },
-    { "code": "organizations", "name": "Organizations", "route": "/organizations" },
-    { "code": "users", "name": "Users", "route": "/users" },
-    { "code": "activity", "name": "Activity", "route": "/activity" },
-    { "code": "billing", "name": "Billing", "route": "/billing" },
-    { "code": "invitations", "name": "Invitations", "route": "/invitations" },
-    { "code": "settings", "name": "Settings", "route": "/settings" },
-    { "code": "help", "name": "Help", "route": "/help" }
-  ],
-  "meta_apps": [],  // Empty - no context switching for admins
-  "current_favorites": ["dashboard", "organizations", "users"],
-  "default_favorites": ["dashboard", "organizations", "users"]
+  "id": UUID,
+  "ticket_id": UUID,
+  "user_id": UUID,  // Agent
+  "assigned_by_user_id": UUID,  // Dispatcher/PM
+  "action": "assigned" | "accepted" | "rejected" | "dropped",
+  "execution_order": int,
+  "planned_start_time": datetime,
+  "assigned_at": datetime,
+  "responded_at": datetime,  // When agent accepted/rejected
+  "journey_started_at": datetime,
+  "arrived_at": datetime,
+  "ended_at": datetime,  // When assignment closed
+  "is_self_assigned": bool,
+  "is_active": bool,  // ended_at IS NULL
+  "journey_start_location": {lat, lng, accuracy},
+  "arrival_location": {lat, lng, accuracy},
+  "arrival_verified": bool,
+  "journey_location_history": [{lat, lng, timestamp, speed}],  // GPS breadcrumbs
+  "notes": str
 }
 ```
 
-### Field Agent
-```json
+### TicketExpense Model
+```python
 {
-  "available_apps": [
-    { "code": "dashboard", "name": "Dashboard", "route": "/dashboard" },
-    { "code": "tickets", "name": "Tickets", "route": "/tickets" },
-    { "code": "map", "name": "Map", "route": "/map" },
-    { "code": "inventory", "name": "Inventory", "route": "/inventory" },
-    { "code": "settings", "name": "Settings", "route": "/settings" },
-    { "code": "help", "name": "Help", "route": "/help" }
-  ],
-  "meta_apps": ["dashboard", "settings", "help"],
-  "current_favorites": ["tickets", "map", "inventory"],
-  "default_favorites": ["tickets", "map", "inventory"]
+  "id": UUID,
+  "ticket_assignment_id": UUID,
+  "ticket_id": UUID,
+  "incurred_by_user_id": UUID,
+  "category": "transport" | "materials" | "meals" | "accommodation" | "other",
+  "description": str,
+  "quantity": decimal,
+  "unit": str,
+  "unit_cost": decimal,
+  "total_cost": decimal,
+  "receipt_document_id": UUID,
+  "location_verified": bool,
+  "is_approved": bool,
+  "approved_by_user_id": UUID,
+  "approved_at": datetime,
+  "rejection_reason": str,
+  "is_paid": bool,
+  "paid_to_user_id": UUID,
+  "paid_at": datetime,
+  "payment_reference": str,
+  "payment_recipient_type": "agent" | "vendor",
+  "payment_method": "send_money" | "till_number" | "paybill" | etc,
+  "payment_details": {},  // M-Pesa/bank details
+  "notes": str
 }
 ```
 
 ---
 
-## Summary
+## Key Business Rules
 
-**What we need from backend:**
-1. Add `meta_apps: string[]` field to `/api/v1/users/me/preferences` response
-2. Populate `meta_apps` based on user role
-3. For project-based roles: Include apps that work outside project context
-4. For admin roles: Empty array or all apps (no context switching)
+### Ticket Creation
+- One source (sales order/incident/task) = one ticket ever (permanent deduplication)
+- Cancelled tickets can be reactivated instead of creating duplicates
+- Installation tickets create subscriptions on completion
+- Support tickets update existing subscriptions (no new subscription)
 
-**What frontend will do:**
-1. Detect if user is in project context (via route)
-2. Filter favorite apps in header based on `meta_apps` when outside project
-3. Filter all apps in launcher based on `meta_apps` when outside project
-4. Show all apps normally when inside project or for admin roles
+### Ticket Assignment
+- Agent capacity: max 4 active tickets
+- Team assignments: any member can complete, closes all assignments
+- Self-assignment: agents can pick from available pool in their region
 
-**Result:**
-- Clean UX for project selection
-- No irrelevant apps shown
-- Seamless transition when entering/exiting projects
-- Backend controls app categorization
-- Frontend just displays what backend provides
+### Ticket Status Transitions
+- `open` → Can assign, update, reschedule, cancel
+- `assigned` → Can start journey, update, reschedule, cancel
+- `in_progress` → Can complete, cannot cancel
+- `completed` → Cannot modify
+- `cancelled` → Can reactivate by creating new ticket from same source
+
+### Expenses
+- Must be linked to assignment
+- Require approval before payment
+- Support M-Pesa, bank transfer, cash payments
+- Track location verification
+
+---
+
+## Common UI Flows
+
+### Flow 1: Create & Assign Installation Ticket
+1. `POST /tickets/from-sales-order` - Create ticket
+2. `POST /ticket-assignments/tickets/{id}/assign` - Assign to agent
+3. Agent accepts and completes work
+4. `GET /tickets/{id}` - View completed ticket
+
+### Flow 2: View Ticket Details
+1. `GET /tickets/{id}` - Get ticket
+2. `GET /ticket-assignments/tickets/{id}/assignments` - Get assignments
+3. `GET /ticket-expenses?ticket_id={id}` - Get expenses
+4. `GET /tickets/{id}/equipment` - Get equipment used
+
+### Flow 3: Manage Agent Workload
+1. `GET /ticket-assignments/users/{agent_id}/assignment-queue` - Check capacity
+2. If capacity available: `POST /ticket-assignments/tickets/{id}/assign`
+3. `GET /tickets/stats` - Monitor overall workload
+
+### Flow 4: Approve Expenses
+1. `GET /ticket-expenses?ticket_id={id}` - List expenses
+2. Review receipts and details
+3. `POST /ticket-expenses/{expense_id}/approve` - Approve/reject
+4. `GET /ticket-expenses/stats` - View expense summary
+
+---
+
+## Error Handling
+
+Common error codes:
+- `400` - Validation error (missing fields, invalid data)
+- `403` - Forbidden (no permission for this project/ticket)
+- `404` - Not found (ticket/assignment doesn't exist)
+- `409` - Conflict (duplicate ticket, agent at capacity, ticket already assigned)
+
+Error response format:
+```json
+{
+  "detail": "Error message explaining what went wrong"
+}
+```
 
 ---
 
-**Next Steps:**
-1. Backend team reviews this proposal
-2. Backend implements `meta_apps` field
-3. Frontend team updates filtering logic
-4. QA tests all role types and contexts
-5. Deploy and monitor
+## Tips for Frontend
+
+1. **Polling**: Poll ticket status every 30-60s for real-time updates
+2. **Filters**: Use query params to filter tickets by status, priority, region
+3. **Pagination**: Default limit is 50, adjust based on UI needs
+4. **Computed Properties**: Use `is_overdue`, `can_be_assigned`, etc. for UI state
+5. **Team Size**: Check `required_team_size` vs `assigned_team_size` for team tickets
+6. **GPS Tracking**: Display `journey_location_history` on map for route visualization
+7. **Expense Approval**: Filter by `is_approved: false` for pending expenses
+8. **Stats Dashboard**: Use `/stats` endpoints for analytics/charts
 
 ---
 
-**Contact:** Frontend Team  
-**For Questions:** Please review and provide feedback on the proposed API changes
+## Quick Reference: HTTP Methods
+
+- `GET` - Retrieve data (list, single item, stats)
+- `POST` - Create new resource or trigger action
+- `PUT` - Update existing resource
+- `DELETE` - Not used (soft deletes via cancel/drop)
+
+All endpoints require authentication via Bearer token in `Authorization` header.

docs/devlogs/browser/browserconsole.txt

@@ -1,105 +1,33 @@
-chunk-276SZO74.js?v=c40a0948:21551 Download the React DevTools for a better development experience: https://reactjs.org/link/react-devtools
-core.ts:167 %cGET%c http://localhost:8000/api/v1/auth/me
-react-router-dom.js?v=c40a0948:4393 ⚠️ React Router Future Flag Warning: React Router will begin wrapping state updates in `React.startTransition` in v7. You can use the `v7_startTransition` future flag to opt-in early. For more information, see https://reactrouter.com/v6/upgrading/future#v7_starttransition.
-warnOnce @ react-router-dom.js?v=c40a0948:4393
-logDeprecation @ react-router-dom.js?v=c40a0948:4396
-logV6DeprecationWarnings @ react-router-dom.js?v=c40a0948:4399
-(anonymous) @ react-router-dom.js?v=c40a0948:5271
-commitHookEffectListMount @ chunk-276SZO74.js?v=c40a0948:16915
-commitPassiveMountOnFiber @ chunk-276SZO74.js?v=c40a0948:18156
-commitPassiveMountEffects_complete @ chunk-276SZO74.js?v=c40a0948:18129
-commitPassiveMountEffects_begin @ chunk-276SZO74.js?v=c40a0948:18119
-commitPassiveMountEffects @ chunk-276SZO74.js?v=c40a0948:18109
-flushPassiveEffectsImpl @ chunk-276SZO74.js?v=c40a0948:19490
-flushPassiveEffects @ chunk-276SZO74.js?v=c40a0948:19447
-(anonymous) @ chunk-276SZO74.js?v=c40a0948:19328
-workLoop @ chunk-276SZO74.js?v=c40a0948:197
-flushWork @ chunk-276SZO74.js?v=c40a0948:176
-performWorkUntilDeadline @ chunk-276SZO74.js?v=c40a0948:384
-react-router-dom.js?v=c40a0948:4393 ⚠️ React Router Future Flag Warning: Relative route resolution within Splat routes is changing in v7. You can use the `v7_relativeSplatPath` future flag to opt-in early. For more information, see https://reactrouter.com/v6/upgrading/future#v7_relativesplatpath.
-warnOnce @ react-router-dom.js?v=c40a0948:4393
-logDeprecation @ react-router-dom.js?v=c40a0948:4396
-logV6DeprecationWarnings @ react-router-dom.js?v=c40a0948:4402
-(anonymous) @ react-router-dom.js?v=c40a0948:5271
-commitHookEffectListMount @ chunk-276SZO74.js?v=c40a0948:16915
-commitPassiveMountOnFiber @ chunk-276SZO74.js?v=c40a0948:18156
-commitPassiveMountEffects_complete @ chunk-276SZO74.js?v=c40a0948:18129
-commitPassiveMountEffects_begin @ chunk-276SZO74.js?v=c40a0948:18119
-commitPassiveMountEffects @ chunk-276SZO74.js?v=c40a0948:18109
-flushPassiveEffectsImpl @ chunk-276SZO74.js?v=c40a0948:19490
-flushPassiveEffects @ chunk-276SZO74.js?v=c40a0948:19447
-(anonymous) @ chunk-276SZO74.js?v=c40a0948:19328
-workLoop @ chunk-276SZO74.js?v=c40a0948:197
-flushWork @ chunk-276SZO74.js?v=c40a0948:176
-performWorkUntilDeadline @ chunk-276SZO74.js?v=c40a0948:384
-core.ts:167 GET http://localhost:8000/api/v1/auth/me → 200 (4.15s)
-core.ts:167 %cGET%c http://localhost:8000/api/v1/sales-orders/stats?project_id=0ade6bd1-e492-4e25-b681-59f42058d29a
-core.ts:167 %cGET%c http://localhost:8000/api/v1/sales-orders?project_id=0ade6bd1-e492-4e25-b681-59f42058d29a&page=1&per_page=20
-core.ts:117 ℹ️ [11:30:52] [COMPONENT] SalesOrdersDashboard: Sales orders dashboard loaded {projectId: '0ade6bd1-e492-4e25-b681-59f42058d29a'}
-core.ts:167 %cGET%c http://localhost:8000/api/v1/auth/me/preferences
-core.ts:167 GET http://localhost:8000/api/v1/sales-orders/stats?project_id=0ade6bd1-e492-4e25-b681-59f42058d29a → 200 (5.92s)
-core.ts:167 GET http://localhost:8000/api/v1/sales-orders?project_id=0ade6bd1-e492-4e25-b681-59f42058d29a&page=1&per_page=20 → 200 (12.56s)
-core.ts:167 %cGET%c http://localhost:8000/api/v1/projects/0ade6bd1-e492-4e25-b681-59f42058d29a/regions
-core.ts:167 GET http://localhost:8000/api/v1/auth/me/preferences → 200 (14.25s)
-core.ts:167 GET http://localhost:8000/api/v1/projects/0ade6bd1-e492-4e25-b681-59f42058d29a/regions → 200 (6.33s)
-core.ts:117 ℹ️ [11:47:03] [COMPONENT] SalesOrdersDashboard: Sales orders dashboard loaded {projectId: '0ade6bd1-e492-4e25-b681-59f42058d29a'}
-core.ts:167 %cGET%c http://localhost:8000/api/v1/projects/0ade6bd1-e492-4e25-b681-59f42058d29a/regions
-core.ts:167 GET http://localhost:8000/api/v1/projects/0ade6bd1-e492-4e25-b681-59f42058d29a/regions → 200 (5.81s)
-client:602  GET http://localhost:8080/src/components/sales-orders/CreateSalesOrderModal.tsx?t=1764071338286 net::ERR_ABORTED 500 (Internal Server Error)
-importUpdatedModule @ client:602
-fetchUpdate @ client:211
-queueUpdate @ client:186
-(anonymous) @ client:642
-handleMessage @ client:640
-(anonymous) @ client:550
-client:176 [hmr] Failed to reload /src/components/sales-orders/CreateSalesOrderModal.tsx. This could be due to syntax errors or importing non-existent modules. (see errors above)
-warnFailedUpdate @ client:176
-fetchUpdate @ client:213
-await in fetchUpdate
-queueUpdate @ client:186
-(anonymous) @ client:642
-handleMessage @ client:640
-(anonymous) @ client:550
-core.ts:167 %cGET%c http://localhost:8000/api/v1/customers?search=Sarah+Wangari
-api-client.ts:113  GET http://localhost:8000/api/v1/customers?search=Sarah+Wangari 403 (Forbidden)
-request @ api-client.ts:113
-get @ api-client.ts:179
-searchCustomers @ salesOrders.service.ts:78
-handleSearchCustomers @ CreateSalesOrderModal.tsx:123
-callCallback2 @ chunk-276SZO74.js?v=c40a0948:3674
-invokeGuardedCallbackDev @ chunk-276SZO74.js?v=c40a0948:3699
-invokeGuardedCallback @ chunk-276SZO74.js?v=c40a0948:3733
-invokeGuardedCallbackAndCatchFirstError @ chunk-276SZO74.js?v=c40a0948:3736
-executeDispatch @ chunk-276SZO74.js?v=c40a0948:7014
-processDispatchQueueItemsInOrder @ chunk-276SZO74.js?v=c40a0948:7034
-processDispatchQueue @ chunk-276SZO74.js?v=c40a0948:7043
-dispatchEventsForPlugins @ chunk-276SZO74.js?v=c40a0948:7051
-(anonymous) @ chunk-276SZO74.js?v=c40a0948:7174
-batchedUpdates$1 @ chunk-276SZO74.js?v=c40a0948:18913
-batchedUpdates @ chunk-276SZO74.js?v=c40a0948:3579
-dispatchEventForPluginEventSystem @ chunk-276SZO74.js?v=c40a0948:7173
-dispatchEventWithEnableCapturePhaseSelectiveHydrationWithoutDiscreteEventReplay @ chunk-276SZO74.js?v=c40a0948:5478
-dispatchEvent @ chunk-276SZO74.js?v=c40a0948:5472
-dispatchDiscreteEvent @ chunk-276SZO74.js?v=c40a0948:5449
-core.ts:167 GET http://localhost:8000/api/v1/customers?search=Sarah+Wangari → 403 (6.10s)
-CreateSalesOrderModal.tsx:126 Search failed APIError: Insufficient permissions. Required: view_customers
-    at APIClient.request (api-client.ts:141:15)
-    at async searchCustomers (salesOrders.service.ts:78:22)
-    at async handleSearchCustomers (CreateSalesOrderModal.tsx:123:29)
-handleSearchCustomers @ CreateSalesOrderModal.tsx:126
-await in handleSearchCustomers
-callCallback2 @ chunk-276SZO74.js?v=c40a0948:3674
-invokeGuardedCallbackDev @ chunk-276SZO74.js?v=c40a0948:3699
-invokeGuardedCallback @ chunk-276SZO74.js?v=c40a0948:3733
-invokeGuardedCallbackAndCatchFirstError @ chunk-276SZO74.js?v=c40a0948:3736
-executeDispatch @ chunk-276SZO74.js?v=c40a0948:7014
-processDispatchQueueItemsInOrder @ chunk-276SZO74.js?v=c40a0948:7034
-processDispatchQueue @ chunk-276SZO74.js?v=c40a0948:7043
-dispatchEventsForPlugins @ chunk-276SZO74.js?v=c40a0948:7051
-(anonymous) @ chunk-276SZO74.js?v=c40a0948:7174
-batchedUpdates$1 @ chunk-276SZO74.js?v=c40a0948:18913
-batchedUpdates @ chunk-276SZO74.js?v=c40a0948:3579
-dispatchEventForPluginEventSystem @ chunk-276SZO74.js?v=c40a0948:7173
-dispatchEventWithEnableCapturePhaseSelectiveHydrationWithoutDiscreteEventReplay @ chunk-276SZO74.js?v=c40a0948:5478
-dispatchEvent @ chunk-276SZO74.js?v=c40a0948:5472
-dispatchDiscreteEvent @ chunk-276SZO74.js?v=c40a0948:5449
+index-D-VTnNjg.js:533 %cGET%c https://kamau1-swiftops-backend.hf.space/api/v1/auth/me
+index-D-VTnNjg.js:533 GET https://kamau1-swiftops-backend.hf.space/api/v1/auth/me → 200 (1.75s)
+index-D-VTnNjg.js:533 %cGET%c https://kamau1-swiftops-backend.hf.space/api/v1/projects?page=1&per_page=100
+index-D-VTnNjg.js:533 %cGET%c https://kamau1-swiftops-backend.hf.space/api/v1/auth/me/preferences
+index-D-VTnNjg.js:533 GET https://kamau1-swiftops-backend.hf.space/api/v1/projects?page=1&per_page=100 → 200 (637ms)
+index-D-VTnNjg.js:533 GET https://kamau1-swiftops-backend.hf.space/api/v1/auth/me/preferences → 200 (963ms)
+index-D-VTnNjg.js:533 ℹ️ [07:45:28] [COMPONENT] ProjectList: Project selected Object
+index-D-VTnNjg.js:533 ℹ️ [07:45:28] [COMPONENT] ProjectList: Switching to project Object
+index-D-VTnNjg.js:533 ℹ️ [07:45:28] [AUTH] Updating user preferences Object
+index-D-VTnNjg.js:533 %cPUT%c https://kamau1-swiftops-backend.hf.space/api/v1/auth/me/preferences
+index-D-VTnNjg.js:533 PUT https://kamau1-swiftops-backend.hf.space/api/v1/auth/me/preferences → 200 (737ms)
+index-D-VTnNjg.js:533 ℹ️ [07:45:29] [AUTH] Preferences updated successfully Object
+index-D-VTnNjg.js:533 %cGET%c https://kamau1-swiftops-backend.hf.space/api/v1/auth/me
+index-D-VTnNjg.js:533 GET https://kamau1-swiftops-backend.hf.space/api/v1/auth/me → 200 (388ms)
+index-D-VTnNjg.js:533 %cGET%c https://kamau1-swiftops-backend.hf.space/api/v1/projects/0ade6bd1-e492-4e25-b681-59f42058d29a/dashboard
+index-D-VTnNjg.js:533 %cGET%c https://kamau1-swiftops-backend.hf.space/api/v1/projects/0ade6bd1-e492-4e25-b681-59f42058d29a/activity-feed?limit=20
+index-D-VTnNjg.js:533 ℹ️ [07:45:29] [COMPONENT] ProjectDashboardPage: Project dashboard loaded Object
+index-D-VTnNjg.js:533 GET https://kamau1-swiftops-backend.hf.space/api/v1/projects/0ade6bd1-e492-4e25-b681-59f42058d29a/dashboard → 200 (16.38s)
+index-D-VTnNjg.js:533 %cGET%c https://kamau1-swiftops-backend.hf.space/api/v1/sales-orders/stats?project_id=0ade6bd1-e492-4e25-b681-59f42058d29a
+index-D-VTnNjg.js:533 GET https://kamau1-swiftops-backend.hf.space/api/v1/projects/0ade6bd1-e492-4e25-b681-59f42058d29a/activity-feed?limit=20 → 200 (16.38s)
+index-D-VTnNjg.js:533 %cGET%c https://kamau1-swiftops-backend.hf.space/api/v1/tickets/stats?project_id=0ade6bd1-e492-4e25-b681-59f42058d29a
+index-D-VTnNjg.js:533 %cGET%c https://kamau1-swiftops-backend.hf.space/api/v1/tickets?project_id=0ade6bd1-e492-4e25-b681-59f42058d29a&skip=0&limit=50
+index-D-VTnNjg.js:533 ℹ️ [07:45:33] [COMPONENT] TicketsDashboard: Tickets dashboard loaded Object
+kamau1-swiftops-backend.hf.space/api/v1/tickets/stats?project_id=0ade6bd1-e492-4e25-b681-59f42058d29a:1  Failed to load resource: the server responded with a status of 422 ()
+index-D-VTnNjg.js:533 GET https://kamau1-swiftops-backend.hf.space/api/v1/tickets/stats?project_id=0ade6bd1-e492-4e25-b681-59f42058d29a → 422 (900ms)
+kamau1-swiftops-backend.hf.space/api/v1/tickets?project_id=0ade6bd1-e492-4e25-b681-59f42058d29a&skip=0&limit=50:1  Failed to load resource: the server responded with a status of 500 ()
+index-D-VTnNjg.js:533 GET https://kamau1-swiftops-backend.hf.space/api/v1/tickets?project_id=0ade6bd1-e492-4e25-b681-59f42058d29a&skip=0&limit=50 → 500 (1.26s)
+index-D-VTnNjg.js:533 %cGET%c https://kamau1-swiftops-backend.hf.space/api/v1/tickets/stats?project_id=0ade6bd1-e492-4e25-b681-59f42058d29a
+kamau1-swiftops-backend.hf.space/api/v1/tickets/stats?project_id=0ade6bd1-e492-4e25-b681-59f42058d29a:1  Failed to load resource: the server responded with a status of 422 ()
+index-D-VTnNjg.js:533 GET https://kamau1-swiftops-backend.hf.space/api/v1/tickets/stats?project_id=0ade6bd1-e492-4e25-b681-59f42058d29a → 422 (335ms)
+index-D-VTnNjg.js:533 %cGET%c https://kamau1-swiftops-backend.hf.space/api/v1/tickets?project_id=0ade6bd1-e492-4e25-b681-59f42058d29a&skip=0&limit=50
+kamau1-swiftops-backend.hf.space/api/v1/tickets?project_id=0ade6bd1-e492-4e25-b681-59f42058d29a&skip=0&limit=50:1  Failed to load resource: the server responded with a status of 500 ()
+index-D-VTnNjg.js:533 GET https://kamau1-swiftops-backend.hf.space/api/v1/tickets?project_id=0ade6bd1-e492-4e25-b681-59f42058d29a&skip=0&limit=50 → 500 (376ms)

src/app/api/v1/tickets.py

@@ -299,6 +299,67 @@ def list_tickets(
     )
 
 
+# ============================================
+# ANALYTICS
+# ============================================
+
+@router.get(
+    "/stats",
+    response_model=TicketStats,
+    summary="Get ticket analytics"
+)
+def get_ticket_stats(
+    project_id: Optional[UUID] = None,
+    project_region_id: Optional[UUID] = None,
+    db: Session = Depends(get_db),
+    current_user: User = Depends(get_current_user)
+):
+    """
+    Get ticket analytics and statistics.
+    
+    **Authorization:**
+    - Platform Admin: All projects
+    - Project Manager: Their projects only
+    - Dispatcher: Their contractor's projects
+    - Client Admin: Their client's projects
+    
+    **Filters:**
+    - `project_id`: Stats for specific project
+    - `project_region_id`: Stats for specific region
+    
+    **Returns:**
+    - Counts by status (open, assigned, in_progress, completed, cancelled)
+    - Counts by type (installation, support, infrastructure)
+    - Counts by priority (urgent, high, normal, low)
+    - Overdue/SLA violations
+    - Average completion time
+    - Completion rate
+    
+    **Example Response:**
+    ```json
+    {
+      "total_tickets": 150,
+      "open_tickets": 20,
+      "assigned_tickets": 30,
+      "in_progress_tickets": 15,
+      "completed_tickets": 80,
+      "cancelled_tickets": 5,
+      "overdue_tickets": 3,
+      "avg_completion_time_hours": 4.5,
+      "completion_rate": 53.33
+    }
+    ```
+    """
+    stats = TicketService.get_ticket_stats(
+        db=db,
+        current_user=current_user,
+        project_id=project_id,
+        project_region_id=project_region_id
+    )
+    
+    return stats
+
+
 @router.get(
     "/{ticket_id}",
     response_model=TicketResponse,
@@ -452,67 +513,6 @@ def cancel_ticket(
     return TicketResponse.from_orm(ticket)
 
 
-# ============================================
-# ANALYTICS
-# ============================================
-
-@router.get(
-    "/stats",
-    response_model=TicketStats,
-    summary="Get ticket analytics"
-)
-def get_ticket_stats(
-    project_id: Optional[UUID] = None,
-    project_region_id: Optional[UUID] = None,
-    db: Session = Depends(get_db),
-    current_user: User = Depends(get_current_user)
-):
-    """
-    Get ticket analytics and statistics.
-    
-    **Authorization:**
-    - Platform Admin: All projects
-    - Project Manager: Their projects only
-    - Dispatcher: Their contractor's projects
-    - Client Admin: Their client's projects
-    
-    **Filters:**
-    - `project_id`: Stats for specific project
-    - `project_region_id`: Stats for specific region
-    
-    **Returns:**
-    - Counts by status (open, assigned, in_progress, completed, cancelled)
-    - Counts by type (installation, support, infrastructure)
-    - Counts by priority (urgent, high, normal, low)
-    - Overdue/SLA violations
-    - Average completion time
-    - Completion rate
-    
-    **Example Response:**
-    ```json
-    {
-      "total_tickets": 150,
-      "open_tickets": 20,
-      "assigned_tickets": 30,
-      "in_progress_tickets": 15,
-      "completed_tickets": 80,
-      "cancelled_tickets": 5,
-      "overdue_tickets": 3,
-      "avg_completion_time_hours": 4.5,
-      "completion_rate": 53.33
-    }
-    ```
-    """
-    stats = TicketService.get_ticket_stats(
-        db=db,
-        current_user=current_user,
-        project_id=project_id,
-        project_region_id=project_region_id
-    )
-    
-    return stats
-
-
 @router.get(
     "/{ticket_id}/equipment",
     response_model=List[dict],

src/app/models/ticket.py

@@ -161,7 +161,10 @@ class Ticket(BaseModel):
         """Check if ticket is overdue (past due_date and still active)"""
         if not self.due_date or not self.is_active:
             return False
-        return datetime.utcnow() > self.due_date
+        # Make datetime timezone-aware for comparison
+        from datetime import timezone
+        now = datetime.now(timezone.utc)
+        return now > self.due_date
     
     @property
     def has_region(self) -> bool:

src/app/schemas/ticket.py

@@ -101,7 +101,6 @@ class TicketResponse(BaseModel):
     """Schema for ticket response with all details"""
     id: UUID
     project_id: UUID
-    project_subcontractor_id: Optional[UUID]
     
     # Source tracking
     source: TicketSource