How sudhir3116/enterprise-it-servicedesk works
Product Support Portal is a multi-tenant SaaS ITSM platform. Its main workflow takes a merchant issue through ticket intake, routing and SLA tracking, support-engineer investigation, developer bug handling, and knowledge capture; a separate feedback portal supports product-roadmap requests. The graph combines documented product stages with relationships visible in the supplied excerpts and SOURCE INDEX. Several route/controller and background-job details were not sampled, so those links are omitted rather than inferred.
Main entry points: App.jsx Portal SPA · ticketController.js Ticket Workflow · server.js Express API · api.js API Client
Components 23
Role-Based Experience
- Portal SPA
frontend/src/App.jsx - Session Context
frontend/src/context/AuthContext.jsx - Customer Workspace
frontend/src/pages/CreateTicket.jsx - Engineer Workspace
frontend/src/pages/EngineerTickets.jsx - Bug Investigation
frontend/src/pages/EngineerBugInvestigation.jsx - API Client
frontend/src/services/api.js
API and Workflows
- Express API
backend/server.js - Authentication
backend/services/authService.js - User Records
backend/models/User.js
Support Operations
- Ticket Workflow
backend/controllers/ticketController.js - Auto Routing
backend/services/routingService.js - SLA Engine
backend/services/slaService.js - SLA Monitor
backend/jobs/slaMonitor.js - Bug Lifecycle
backend/services/bugService.js - Ticket Records
backend/models/Ticket.js - Bug Reports
backend/models/BugReport.js
Knowledge and Product
- Knowledge Base
backend/controllers/kbController.js - Knowledge Articles
backend/models/KnowledgeArticle.js - Product Feedback
backend/controllers/feedbackController.js
Other components
- Merchant / Customer
- Support Staff
- Developer
- MongoDB
Connections 27
- Merchant / Customer → Portal SPA: uses portal
README.md - Support Staff → Portal SPA: uses portal
README.md - Developer → Portal SPA: uses portal
README.md - Portal SPA → Customer Workspace: routes to
frontend/src/App.jsx - Portal SPA → Engineer Workspace: routes to
frontend/src/App.jsx - Portal SPA → Bug Investigation: routes to
frontend/src/App.jsx - Session Context → API Client: uses
frontend/src/context/AuthContext.jsx - Engineer Workspace → API Client: calls
frontend/src/pages/EngineerTickets.jsx - Bug Investigation → Express API: requests API
README.md - Customer Workspace → Express API: requests API
README.md - API Client → Express API: sends REST requests
README.md - Express API → Authentication: routes auth requests
- Authentication → User Records: reads and updates
backend/services/authService.js - Express API → Ticket Workflow: routes ticket requests
- Ticket Workflow → Ticket Records: reads and writes
backend/controllers/ticketController.js - Ticket Workflow → Auto Routing: uses for assignment
- Ticket Workflow → SLA Engine: uses SLA logic
- SLA Monitor → Ticket Records: monitors deadlines
- Ticket Workflow → Bug Lifecycle: creates bug handoff
- Bug Lifecycle → Bug Reports: manages reports
- Ticket Workflow → Knowledge Base: converts resolution
- Knowledge Base → Knowledge Articles: reads and writes
backend/controllers/kbController.js - Portal SPA → Product Feedback: offers feedback portal
README.md - Ticket Records → MongoDB: persists in
README.md - User Records → MongoDB: persists in
README.md - Knowledge Articles → MongoDB: persists in
README.md - Bug Reports → MongoDB: persists in
README.md