SYSTEMS / SUPPORT
IT Help Desk Ticketing
A local Flask application that keeps ticket ownership, state and troubleshooting history together.
← All projectsObjective
Make support requests traceable from submission through assignment and resolution.
Tools & architecture
Python, Flask, SQLite. Requester and technician roles → Flask application → transactional ticket and history updates in SQLite.
Development & challenges
Requesters see their own tickets; technicians manage the queue. State changes and their history are saved in the same transaction.
Security considerations
The application uses parameterized SQL, escaping, CSRF checks and a session reset on login. Local database owners can still modify history directly.
Testing & verification
The October 21, 2026 test record contains seven Flask test-client checks. Browser, load and penetration testing are next steps.
Outcome & limitations
Local application with fictional tickets. The development server and unencrypted local storage are not configured for customer production use.
What I learned
A status change is only useful when someone can understand what happened and who owns the next step.
Source code is maintained in my private GitHub repositories.