Launching GOTRS 0.1.0 set the baseline for everything that follows. We delivered the essential plumbing that lets teams log in securely, manage tickets end to end, and run the platform inside a hardened container fleet.
What Shipped
- Security-first authentication with JWT, RBAC, and secret management gives us a compliant, auditable core.
- OTRS-compatible schema import carries 116 tables forward so migrations from legacy deployments stay realistic.
- Complete ticket lifecycle including articles, canned responses, workflow automation, and file storage keeps parity with what service desks expect.
- Integration-ready surface area via REST and GraphQL previews the APIs we will stabilize in upcoming slices.
Why It Matters
With these foundations, GOTRS is already usable for pilot desks. The authentication wall is trustworthy, ticket data stores safely, and the codebase runs entirely through the container toolchain we need for OpenShift and Podman.
What’s Next
Next we focused on developer ergonomics and resilience—the 0.2.0 work that landed just a couple of weeks later.
Bonus Track: Hardening Early
Aligning with OTRS semantics meant reconciling historical assumptions with stricter security defaults. We hardened password generation, removed every hardcoded credential, and revalidated each migration against clean-room datasets to avoid drift. On the infrastructure side we invested early in multi-stage Dockerfiles, rootless runtime defaults, and CI hooks so contributors can ship changes without babysitting bespoke environments.