This year was wild and challenging at times for us at Rother OSS.
OTOBO has taken on quicker and spread much wider than we had hoped in our wildest dreams when we set off to create our fork and build a community again.
There are many more things to improve, so many ideas and plans, there’s so much more work to do, but the team is growing, our energy is high, and we look full of confidence to the future!
As we release OTOBO 10.1 beta, we’re stepping back for a second, and look at the things we have accomplished over the last year. Together.
It is time to say Thank You to the many many people collaborating on this project. We have a fantastic team, wonderful clients, brilliant partners, and a great community – all this would not be possible without you. THANK YOU!!
Originally, we had planned to release OTOBO 11 now. As 2021 went a little different than expected, we are releasing OTOBO 10.1 instead and OTOBO 11 will follow suit next year. We are working on it already.
OTOBO 10.1 is setting a strong base for the things to come. We changed the framework in the background, added functionality and adapted a few more default configuration settings to make the start with this mighty system easier.
OTOBO supports OpenIDConnect now in the standard – modern SSO authentication based on OAuth2. Agents can be authorised, too.
Enhanced S/MIME functionality – graphical pointers for encrypted / signed mails. Performance boost.
Enhanced process functionality – processes in the customer interface, process templates (actions to be run without preceding activity dialogue to come)
PSGI is used consistently now under Apache, too (in OTOBO 10.0 only in Docker with Gazelle) – facilitating easier integration of OTOBO in diverse web server scenarios as well as integrating middleware with OTOBO
S3 implementation – setting the base for easier clustering (Kubernetes, MinIO, AWS) – experimental)
Template web services – making it so much easier to connect OTOBO with third party systems such as Jira or Bugzilla
Reporting – Generate reports, e.g. by combining several statistics, and send them out via email as a PDF file
Changed default configuration for an easier start with the system:
The system user root@localhost is “- – “ now, and unlocked tickets are passed back to this user with a view to avoid confusions regarding ticket owner and lock/unlock.
Internal notes are active by default to enable communication between agents
Escalation notifications are sent only to subscribing agents (instead of: to all agents with write permissions for the given queue)
Linked tickets are displayed below the articles of a ticket
Please check the Release Notes for a more detailed list of new features and improvements (in German and English.
You can prevent the setting of cookies at any time by making the appropriate setting in your internet browser. Cookies that have already been set can be deleted manually or automatically at any time. This is possible in all common internet browsers. If the setting of cookies is deactivated in the browser, not all functions of the website may be fully usable.
We deliberately use very little cookies.
Essential Cookies are necessary to deliver this website and some of its features correctly.
For this reason, we do not provide any opportunity here to disable them.
Notwithstanding this, you can deactivate all Cookies in your Browser Settings at any time. Please be aware, however, that this might have an impact on the functionality of this website.
Google Analytics' Cookies
When you visit this website, Google Analytics sets cookies on your system. This will help us analyse how you use our website ans tailor it to the needs of our visitors. Your IP address will be automatically anonymised (IP anonymisation and deactivation of your User ID). Therefore, we cannot trace which data a certain user is accessing. The data are not saved together with any other personal user data.
You can deactivate tracking in your browser if you do not want us to be able to track your visit on our website.