How saineshwar/vueticket-servicedesk works
VueTicket is a self-hosted service-management application: requesters and support staff use a React portal backed by an ASP.NET Core API and SQL Server, with a separately hosted worker for assignment, SLA, escalation, and housekeeping. The primary workflow is submitting and working a ticket, with access control and service-desk configuration shaping who can see and handle it. The README documents notifications, attachments, dashboards, and administration. Several backend service-to-store and API-to-service links were not shown, so those relationships are omitted rather than inferred.
Main entry points: Program.cs HTTP API host · endpoints.ts API endpoint client · App.tsx Portal routing · EngineHosting.cs Engine task hosting
Components 25
Web portal
- Portal routing
frontend/src/app/App.tsx - Ticket workspace
frontend/src/features/tickets/TicketDetailPage.tsx - Home dashboard
frontend/src/features/home/HomePage.tsx - Administration screens
frontend/src/features/admin/desks/ServiceDesksPage.tsx - Sign-in and setup
frontend/src/auth/AuthProvider.tsx - API endpoint client
frontend/src/api/endpoints.ts
API and domain
- HTTP API host
backend/src/TicketCore.Api/Program.cs - Authentication
backend/src/TicketCore.Core/Auth/AuthService.cs - Roles and permissions
backend/src/TicketCore.Core/Access/RoleService.cs - Organization tree
backend/src/TicketCore.Core/Organization/OrgUnitService.cs - Service desks
backend/src/TicketCore.Core/ServiceDesks/ServiceDeskService.cs - Ticket operations
backend/src/TicketCore.Core/Tickets/TicketService.cs - Dashboard queries
backend/src/TicketCore.Core/Dashboard/DashboardService.cs - SLA configuration
backend/src/TicketCore.Core/Sla/SlaConfigService.cs
Persistence
- Data access
backend/src/TicketCore.Data/TicketDbContext.cs - SQL Server
Automation worker
- Worker host
backend/src/TicketCore.Worker/Program.cs - Engine task hosting
backend/src/TicketCore.Engine/EngineHosting.cs - SLA and escalation
backend/src/TicketCore.Engine/Sla/SlaMonitor.cs - Ticket assignment
backend/src/TicketCore.Engine/Assignment/AssignmentEngine.cs - Engine data store
backend/src/TicketCore.Data/Engine/EngineStore.cs
Delivery services
- Ticket notifications
backend/src/TicketCore.Core/Notifications/TicketNotifier.cs - Email delivery
backend/src/TicketCore.Services/Email/EmailDelivery.cs - Attachment storage
backend/src/TicketCore.Services/Storage/FileStorage.cs
Other components
- Requester or agent
Connections 27
- Requester or agent → Portal routing: uses
- Portal routing → Sign-in and setup: routes to
frontend/src/app/App.tsx - Portal routing → Home dashboard: routes to
frontend/src/app/App.tsx - Portal routing → Ticket workspace: routes to
frontend/src/app/App.tsx - Ticket workspace → API endpoint client: requests data
frontend/src/features/tickets/TicketDetailPage.tsx - Home dashboard → API endpoint client: requests data
frontend/src/features/home/HomePage.tsx - Administration screens → API endpoint client: requests data
frontend/src/features/admin/desks/ServiceDesksPage.tsx - Sign-in and setup → API endpoint client: authenticates through
frontend/src/auth/AuthProvider.tsx - API endpoint client → HTTP API host: calls
frontend/src/api/endpoints.ts - HTTP API host → Authentication: handles sign-in
- HTTP API host → Roles and permissions: checks access
- HTTP API host → Organization tree: serves organization
- HTTP API host → Service desks: serves configuration
- HTTP API host → Ticket operations: handles tickets
- HTTP API host → Dashboard queries: serves dashboard
- HTTP API host → SLA configuration: serves SLA setup
- Ticket operations → Attachment storage: stores attachments
- Ticket operations → Ticket notifications: triggers notices
- Ticket notifications → Email delivery: queues email
- Worker host → Engine task hosting: starts tasks
backend/src/TicketCore.Engine/EngineHosting.cs - Engine task hosting → SLA and escalation: runs
backend/src/TicketCore.Engine/EngineHosting.cs - Engine task hosting → Ticket assignment: runs
backend/src/TicketCore.Engine/EngineHosting.cs - SLA and escalation → Engine data store: reads and writes
backend/src/TicketCore.Engine/EngineHosting.cs - Ticket assignment → Engine data store: assigns tickets
backend/src/TicketCore.Engine/Assignment/AssignmentEngine.cs - Engine task hosting → Engine data store: records runs
backend/src/TicketCore.Engine/EngineHosting.cs - Data access → SQL Server: persists data
- Engine data store → SQL Server: reads and writes
backend/src/TicketCore.Data/Engine/EngineStore.cs