OTOBO is one of the most flexible web-based ticketing systems used for Customer Service, Help Desk, IT Service Management. https://otobo.io/
Find a file
bernhard 728184014c
Some checks failed
CacheLocalLib / CacheLocalLib (push) Has been cancelled
DockerImageBuilderDevel / BuildDockerImage (., otobo.web.dockerfile, rotheross/otobo, devel-, otobo-web) (push) Has been cancelled
DockerImageBuilderDevel / BuildDockerImage (scripts/elasticsearch, otobo.elasticsearch.dockerfile, rotheross/otobo-elasticsearch, devel-, otobo-elasticsearch) (push) Has been cancelled
DockerImageBuilderDevel / BuildDockerImage (scripts/nginx, otobo.nginx.dockerfile, rotheross/otobo-nginx-kerberos-webproxy, devel-, otobo-nginx-kerberos-webproxy) (push) Has been cancelled
DockerImageBuilderDevel / BuildDockerImage (scripts/nginx, otobo.nginx.dockerfile, rotheross/otobo-nginx-webproxy, devel-, otobo-nginx-webproxy) (push) Has been cancelled
DockerImageBuilderDevel / BuildDockerImage (scripts/test/sample, otobo.selenium-chrome.dockerfile, rotheross/otobo-selenium-chrome, devel-, otobo-selenium-chrome) (push) Has been cancelled
Be more verbose in code comment on DB::Attribute
2025-12-29 12:28:32 +01:00
.github Elaborate on how to test the autobuild images. 2025-12-09 11:40:13 +01:00
bin Issue #2612: add package names for Plack 2025-12-21 13:37:30 +01:00
Custom Issue #20: remove references and workarounds for PerlEx 2020-05-14 12:52:56 +02:00
development Issue #4060: Update copyright year range to 2019-2025 2025-01-14 15:56:21 +01:00
doc Fixed issue #313. Thanks to Helmut Wollmersdorfer! 2020-08-05 22:48:47 +02:00
hooks Merge branch 'rel-10_1' into rel-11_0 2024-07-30 17:45:07 +02:00
i18n/otobo Translated using Weblate (German) 2025-12-25 00:53:07 +01:00
Kernel Be more verbose in code comment on DB::Attribute 2025-12-29 12:28:32 +01:00
scripts Issue #4972: no advisory is expected for libwww-perl 2025-12-23 13:33:01 +01:00
var Issue #4816: Fix styles for richtext headings 2025-12-16 14:07:16 +01:00
.bash_completion Issue #4060: Update copyright year range to 2019-2025 2025-01-14 15:40:05 +01:00
.dockerignore Issue #4707: we need cpanfile.docker.snapshot in the Docker image 2025-09-17 17:24:47 +02:00
.fetchmailrc.dist Issue #4060: Update copyright year range to 2019-2025 2025-01-14 15:40:05 +01:00
.gitattributes Issue #4731: Add CHANGES.md and language files as merge=ours to gitattributes. 2025-11-12 14:51:15 +01:00
.gitignore Merge branch 'rel-10_1' into rel-11_0 2025-11-21 12:29:02 +01:00
.mailfilter.dist Merge branch 'rel-10_0' into rel-10_1 2025-01-14 15:44:32 +01:00
.perlimports.toml Tidy some more perlimports. 2024-02-18 13:19:53 +01:00
.procmailrc.dist Issue #4060: Update copyright year range to 2019-2025 2025-01-14 15:40:05 +01:00
.screenrc Issue #4060: Update copyright year range to 2019-2025 2025-01-14 15:40:05 +01:00
AUTHORS.md Issue #3425: Updated mail addresses. 2024-06-17 14:32:28 +02:00
CHANGES.md Fix CHANGES. 2025-12-17 11:02:22 +01:00
CONTRIBUTING.md Issue #313: fix two more links. doc.otobo.de => doc.otobo.org 2020-08-06 10:20:44 +02:00
COPYING-Third-Party Merge branch 'rel-10_1' into rel-11_0 2025-12-22 12:44:30 +01:00
cpanfile Issue #4376: document which modules are in Perl core 2025-12-01 14:27:37 +01:00
cpanfile.docker Issue #4376: document which modules are in Perl core 2025-12-01 14:27:37 +01:00
cpanfile.docker.snapshot Update the CPAN snapshot 2025-12-15 15:22:47 +01:00
INSTALL.md Update version numbers from 10.1 to 11.0 2022-07-19 15:53:25 +02:00
LICENSE Initial commit 2020-01-30 21:46:00 +01:00
otobo.elasticsearch.dockerfile Issue #4183: enhance comments in Dockerfile 2025-02-24 11:32:57 +01:00
otobo.kerberos.web.dockerfile Issue #3628: prematurely removed the dummy Kerberos Dockerfiles 2024-07-31 09:23:58 +02:00
otobo.nginx-kerberos.dockerfile Merge branch 'rel-10_0' into rel-10_1 2025-10-14 17:24:28 +02:00
otobo.nginx.dockerfile Merge branch 'rel-10_1' into rel-11_0 2025-10-14 17:27:13 +02:00
otobo.selenium-chrome.dockerfile Issue #4839: reinstate the target otobo-selenium-chrome 2025-12-01 18:28:53 +01:00
otobo.web.dockerfile Merge branch 'rel-10_1' into rel-11_0 2025-12-16 20:41:17 +01:00
README.md Merge branch 'rel-10_1' into rel-11_0 2024-07-25 15:49:56 +02:00
RELEASE Update version numbers from 10.1 to 11.0 2022-07-19 15:53:25 +02:00
SECURITY.md Issue #1855: Declare OTOBO 11 as supported in SECURITY.md 2022-07-29 12:04:57 +02:00
UPDATING.md Update version numbers from 10.1 to 11.0 2022-07-19 15:53:25 +02:00

What is OTOBO?

OTOBO is an extremely flexible, web-based open-source ticketing tool. The application is used for streamlining communication in service organisations such as IT helpdesks, customer service centers, call centers etc.

It provides classical ticketing functionality, a knowledgebase/FAQs with internal and external interface, helps to automate processes and can be extended by an ITSM component with a CMDB to keep track of IT components or buildings, office plants, cars etc.

OTOBO is a fork based on ((OTRS)) Community Edition, started in 2019 to go back to the roots and offer a 100 % free tool, rooted in a strong community, and backed up by professional business services.

Find a list of features here.

License

OTOBO is distributed under the GNU General Public License - see the accompanying LICENSE file for more details.

Documentation

OTOBO documentation can be found at https://doc.otobo.org/

The source code of OTOBO and its extension modules is available on GitHub.

Professional Services for OTOBO

OTOBO is a mighty and highly flexible tool. Pretty much everything can be individualized and adapted to your needs. And more often than not there is more than one way to achieve a goal.

No reason to feel overwhelmed, though. We are happy to help adapt the system optimally to your needs, make sure you take full advantage of it, and assist in securing your operations. Theres also a fully managed version of OTOBO if you do not want to take care of that yourself.

We are Rother OSS GmbH, source code owner of OTOBO. Founder Stefan Rother was first employee of OTRS GmbH back in 2004, and created Rother OSS when he left there in 2011. We have been working with the ticketing tool ever since, and know what we are doing.

Read more about

Or directly get in touch.

Software requirements

The software and hardware requirements can be found in our documentation.

How to contribute

We take the open-source idea very seriously and explicitly invite the community to engage with us.

If you have a request or think you have found a bug, please visit our forums or open an issue on GitHub.

To make our lives a bit easier, please

  • Search the forums before issuing new topics
  • Try to be as precise and complete as possible when reporting bugs it helps a lot if we know how to reproduce them
  • Use the labels provided on GitHub to categorize your request
  • Start a pull request, if you have implemented a feature or fix yourself.

THANK YOU!