Welcome to OTRS Documentation.

All public repositories of OTRS can be found at github, for example the OTRS framework itself.


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. Read the blog article from Julien Ponge for a discussion of when and why it is good for open source projects to use a CLA. Please print and sign the OTRS contributor agreement document and send us the scan and your GitHub username to cla@otrs.com.

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. In the manual you will find information about 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 OTRS code policy 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)) Community Edition is rel-6_0. All bugfixes should be applied to this branch.

OTRS uses a deferred release strategy, which means that OTRS is first made available to paying customers, and only later as ((OTRS)) Community Edition to the public. Therefore, the master branch is not available on GitHub.

Paying customers may also contribute features to the development version of OTRS. Please contact us if you are interested in doing so.

Public feature contributions can only be made via the public maintenance branch. This means that there can be cases where features may not be accepted into the (internal) master branch of OTRS if the newer code in there is already too different.

Translating OTRS

Translators should use translate.otrs.com to translate OTRS. We have summarized all you need to know about translating the OTRS service management suite or the OTRS documentation.


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 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.