Developer docs
Practical guides for creating, testing, and publishing OTOBO, Znuny, and OTRS packages and skins.
- Building OTOBO & Znuny Packages (.opm)
Step-by-step: From directory structure to the .sopm manifest and the final .opm file for OTOBO, Znuny, and OTRS CE.
- .sopm Reference
Reference of all important .sopm elements for OTOBO, Znuny, and OTRS CE: name, version, framework, filelist, dependencies, and install sections.
- OTOBO/Znuny Skin Development
Create custom agent and customer skins for OTOBO, Znuny, and OTRS CE: SysConfig loader entries, directory structure, and CSS overrides.
- Will my package run on OTOBO and Znuny?
Why OTOBO, Znuny, and OTRS packages usually work across forks — and how to make your .opm available for all three forks using the correct <Framework> settings.
- Publish a Package on Open ITSM Hub
List your OTOBO or Znuny package for free in the Open ITSM Hub directory via a pre-filled GitHub pull request — no backend login required.
- Build .opm in CI/CD with opmbuild
Automate building and testing OTOBO and Znuny packages without a full ticketing system installed — using the CPAN tool OPM::Maker (opmbuild) in GitHub Actions.