Welcome to OTRS Documentation. Manuals & API docs Learn more about OTRS Download OTRS
We are glad about all contributions that you may want to make. Please note that you need to accept the OTRS contributor agreement (CLA) once. This effectively means that you transfer the copyright of the code to OTRS — see this blog entry for a discussion of when and why it is good for open source projects to use a CLA. Please print and sign this document and send us the scan and your github username.
While the administrator's manual has lots of information about how to setup, use and tune OTRS, there is also a developer's manual that goes into the details of OTRS development. It can tell you how to setup a development environment and how you can contribute to OTRS.
The contributing section also has information about the OTRS code style guide that you should read and follow. We also recommend that you checkout and use the OTRSCodePolicy module. You can run this manually on your code and/or register it as a git commit hook that will perform the checks every time that you commit. Please see the module documentation for details. Using this module before sending a pull request is mandatory.
If you have any questions, please don't hesitate to ask on the developer's mailing list.
The current maintenance branch of OTRS is rel-5_0. All bugfixes should be applied to this branch. New features will not be accepted in a stable branch but should be directed to the master branch instead.
Professional Services for OTRS
We offer best professional support from the OTRS team, reliable OTRS security and regular free updates as well as an exclusive set of additional Business Features that you can flexibly activate or deactivate according to different deployment scenarios.
The OTRS Group offers specific training programs in different countries. You can either participate in one of our public OTRS Administrator training seminars which take place regularly, or benefit from an inhouse training seminar that covers all the specific needs of your company.