django-helpdesk
A Django application to manage tickets for an internal helpdesk. Formerly known as Jutda Helpdesk.
Runssource: GitHubPythonBSD-3-Clausecommit a3d61c598a72
Python, BSD-3-Clause licensed. The project labels itself: agile, bugs, cases, django, hacktoberfest, hacktoberfest2020, helpdesk and incidents.
django-helpdesk runs. An Argusic agent installed it in 0.5 minutes and hit 1 error and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Django-helpdesk demo server answers HTTP 200 on /, test suite passes all 430 tests, all 42 migrations applied, admin user admin:Pa33w0rd loaded
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 100 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.
What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- uv not installed in container0.3 minutes
- Install time
- under a minute
- Cold machine to finish
- 2 minutes
- Errors hit and fixed
- 1 hit, 1 fixed with no human help
- How the result was proved
- curl -s -o /dev/null -w '%{http_code}' localhost:8080 returned 200; 'uv run quicktest.py' exited OK with 430 tests passed, 0 failures
- Model tokens used
- 21,985
- Exact commit tested
- a3d61c598a72
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
tokens used 21,985 All the core pieces are working. Let me record the final report. **Summary of what happened:** 1. **`uv` missing** — installed via the official install script to `/tmp/uv-bin`. 2. **`uv venv`** — created a virtual environment successfully. 3. **`uv sync --dev --group test`** — installed all 35 packages (Django 6.0.8, djangorestframework,… 4. **`manage.py migrate`** — all 42 migrations applied cleanly. 5. **Fixture loading** — `emailtemplate.json` (160 objects) and `demo.json` (19 objects) loaded wit… 6. **Demo server** — launched on port 8080; `curl` returned **HTTP 200** with a 13034-byte page. 7. **Test suite** — 430 tests ran in 12.97s, all passed (2 skipped, both expected). The email-proce… Only minor observation: `yarn` is not in the container, so `make static-vendor` (vendor JavaScript/…
Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Reached a running state on a clean machine, with the session recorded.
- Installed in 0.5 minutes.
- Recovered from all 1 error without a human stepping in, which says the failures are documented well enough to solve.
- Ran without a GPU, so it does not need one to start.
- Licensed BSD-3-Clause, as reported by its host.
What did not, or is not known
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
- A quick evaluation: it was running 0.5 minutes after the clone.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
Topics (from GitHub)
agilebugscasesdjangohacktoberfesthacktoberfest2020helpdeskincidentsissueskanbanpythonscrumservicedesksupportticketstracker
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/django-helpdesk)Questions
- Does django-helpdesk run?
- Yes. django-helpdesk runs. Argusic installed and launched it on a clean machine in 1 minutes, hitting 1 error on the way, and recorded the session.
- How did Argusic test django-helpdesk?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit a3d61c598a72. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test django-helpdesk?
- The run that produced this verdict cost $0.01: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does django-helpdesk take to install?
- 0.5 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does django-helpdesk need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing django-helpdesk?
- 1 thing broke in the recorded run, and 1 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for django-helpdesk?
- The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.