How arshad1428/ticketflow works
TicketFlow is a client-and-staff ticketing portal backed by an Express API and PostgreSQL. The main workflow is client ticket creation, staff assignment and replies, business-calendar SLA tracking and escalation, then resolution, rating or reopening. The portal also exposes administration, reports, security settings and knowledge-base content; the server supports inbound email, queued SMTP delivery, attachment scanning, licensing and extension hooks. The API is concentrated in app.js. Relationships involving the UI are documented at the product level; unsampled implementation details are not inferred.
Main entry points: app.js Express API · worker.js Background worker · main.jsx React portal · db.js PostgreSQL
Components 19
User experience
- React portal
client/src/main.jsx
Ticket operations
- Express API
server/src/app.js - Ticket lifecycle
server/src/app.js - Administration
server/src/app.js - Reports and alerts
server/src/app.js
Platform and security
- MFA security
server/src/mfa.js - License validation
server/src/license.js - Extension hooks
server/src/modules/index.js - Server runtime
server/src/index.js
SLA and messaging
- Business-time SLA
server/src/sla.js - Background worker
server/src/worker.js - Mail outbox
server/src/worker.js
Integrations and storage
- Upload scanning
server/src/scanner.js - PostgreSQL
server/src/db.js
Other components
- Clients
- Support staff
- SMTP service
- ClamAV scanner
- Mail provider
Connections 24
- Clients → React portal: use portal
README.md - Support staff → React portal: use workspace
README.md - React portal → Express API: request API
README.md - Express API → Ticket lifecycle: routes tickets
server/src/app.js - Express API → Administration: routes administration
server/src/app.js - Express API → Reports and alerts: serves reports
server/src/app.js - Express API → PostgreSQL: queries and writes
server/src/app.js - Express API → MFA security: validates MFA
server/src/app.js - Express API → License validation: validates license
server/src/app.js - Express API → Extension hooks: runs hooks
server/src/app.js - Express API → Upload scanning: scans uploads
server/src/app.js - Express API → Business-time SLA: computes SLA
server/src/app.js - Express API → Background worker: notifies worker
server/src/worker.js - Ticket lifecycle → PostgreSQL: stores ticket data
server/src/app.js - Ticket lifecycle → Extension hooks: invokes ticket hook
server/src/app.js - Upload scanning → ClamAV scanner: scans bytes
server/src/scanner.js - Server runtime → Express API: starts server
server/src/index.js - Server runtime → Background worker: schedules ticks
server/src/index.js - Background worker → PostgreSQL: reads and updates
server/src/worker.js - Background worker → Business-time SLA: computes elapsed time
server/src/worker.js - Background worker → Express API: uses config and notifications
server/src/worker.js - Background worker → Mail outbox: delivers queued mail
server/src/worker.js - Mail outbox → SMTP service: sends email
server/src/worker.js - Mail provider → Express API: posts inbound mail
README.md