// the find
django-helpdesk/django-helpdesk
A Django application to manage tickets for an internal helpdesk. Formerly known as Jutda Helpdesk.
django-helpdesk is a Django app that turns email and web submissions into tickets, sorted into queues with assignees and escalation rules. It suits small support or internal IT teams that want a self-hosted tracker and are fine running it inside their own Django project or as a standalone install. It descends from the Jutda Helpdesk code and is still BSD-3 licensed.
- The email path is real plumbing: a get_email management command, a polling shell script, and per-queue mailbox settings with local-directory and logging options (migration 0013). It is not a stub you have to finish yourself.
- The migration history shows upgrades were treated as a requirement. Forty-two migrations include data migrations for the usersettings and queue-membership moves (0002, 0003, 0009) and a depickling step (0020) for old installs.
- Extension points are documented on their own pages: custom fields, custom templates, webhooks, the API, iframe submission, and spam handling. Each one is a place you would otherwise patch the code.
- jQuery, flot, morris, and timeline3 are checked into static/helpdesk/vendor rather than coming through a package manager. Upgrades are manual copies, and security bumps are easy to miss.
- The README admits keyword search does not work properly on the SQLite demo, since SQLite has no case-insensitive match. The first thing an evaluator tries may look broken, and production needs PostgreSQL or MySQL, which the README mentions only in passing.
- Migrations 0018 and 0019 both carry the name ticket_secret_key, which makes the history harder to read for anyone writing a follow-on migration. The build badge points at Azure DevOps, but the only CI config in the tree I can see is under .github/workflows.