OTOBO 11.1 Beta: What's New — Ticket Handling, Process Management & Integration

OTOBO 11.1 is available as a beta release (24 June 2026). Where OTOBO Version 11 established the new CMDB, dynamic fields, and Docker-first platform, 11.1 focuses on quality-of-life improvements where agents and admins spend most of their time: ticket handling, process modeling, security, and integration.

Release status: 11.1 is beta. Production systems should stay on the stable 11.0.x line (latest: 11.0.16, April 2026) until the stable 11.1 release. Official release notes: otobo.io/en/otobo-11-1-beta.

Highlights at a Glance

Ticket handling — richer Elasticsearch search, Similar Tickets widget, article edit/pin in core, parallel list filters
Process management — namespaces, global vs. process-specific elements, Not/Any/All transition logic
Dynamic fields — stronger reference lenses and sets; less context switching in Ticket Zoom
Security & auth — OAuth token management, OpenID Connect SSO, encrypted DB connectivity (DBD::MariaDB)
Integration — multipart web services, configuration and object import/export built into core
Packaging — several former add-on packages merged into the standard (Elasticsearch extension, article edit, process templates, and more)

Ticket Handling — Better Overview, Faster Results

Agents spend most of their day inside tickets. 11.1 targets exactly that workflow.

Elasticsearch — Search at a New Level

The Elasticsearch extension is now part of core. Search supports additional dialogues, field-based queries, and extended syntax — for example Title:Test* AND Body:Test* or Boolean operators with AND / NOT. Teams already using Elasticsearch should notice more precise, concurrent search immediately.

A new Similar Tickets widget in Ticket Zoom shows related tickets powered by Elasticsearch — no manual searching through history. Rother OSS notes this is one of the tasks that will eventually be handled by OTOBO AI (Rotobo), planned for a broader release in September 2026.

Article Editing in Core

Extended article edit is integrated into the standard. Agents can edit, delete, or pin articles directly in Ticket Zoom — including time tracking on edits. Correct mistakes, remove clutter, and keep key information visible without installing a separate package.

Parallel Filters in Ticket Lists

Ticket overviews now support multiple filters in parallel. Configure the view once and return to it with one click — no repeated manual re-filtering on long lists.

Process Management — Model with Precision

Complex process setups grow quickly. 11.1 adds structure and control for admins who maintain them.

Namespaces group process elements logically so large workflows stay navigable
Global vs. process-specific elements — a checkbox decides whether an element is shared across all processes or limited to one
Transition logic supports Not, Any, and All, including checks for empty fields; dynamic fields inside a set can be addressed as Field1::Field2
Ticket templates in process dialogs — templates from the familiar ticket UI now work in process dialogues too
Customer interface — process and activity details can be hidden so customers see only what they need
Improved sorting for process elements in the admin area

Process ticket templates are now core — no separate package required.

Dynamic Fields — Information Where It Is Needed

Reference-type dynamic fields link FAQ articles, services, customers, customer users, or ConfigItems to tickets (or to each other). Lens fields show linked object details inside the ticket without opening another screen.

11.1 extends this further: lens fields can point directly to reference fields and to sets, reducing clicks and context switching per ticket.

Security — Modern Authentication, Secure Connectivity

OAuth Token Management

OTOBO now includes central OAuth token management for external services — email via POP, IMAP (now also SMTP), and outgoing web services. Tokens replace scattered password configs and reduce overhead when credentials rotate.

OpenID Connect (SSO)

OpenID Connect enables single sign-on for agents and customers. One corporate login can cover OTOBO and other systems — no separate OTOBO passwords required.

Encrypted Database Connectivity

The DB backend moves from DBD::mysql to DBD::MariaDB — actively maintained and aligned with current MySQL/MariaDB versions. Encrypted connectivity is available; authentication plugins can be selected in the installer.

Upgrade warning: The MailAccountOAuth2 package has been merged into core. Manual adjustments are required during upgrade if you used that package separately.

Data Exchange & Integration — Simplified

Web Services

Attachments via multipart/form-data — required for direct integration with JIRA, OpenProject, and similar systems
Outgoing data can enforce specific formats (e.g. arrays) in XSLT
OAuth as authentication for outgoing web services

Import & Export in Core

Configuration packages — processes, dynamic fields, notifications, queues, ACLs — export to CSV and re-import from the respective admin screens
Standard objects — tickets, customers, customer users, and ConfigItems via Admin → Import/Export for migration or data exchange

Former packages ImportExportStandardObjects, ImportExportCustomerCompany, and related tools are now part of the standard.

Other Notable Core Integrations

Several community packages moved into 11.1 core, including:

CustomerTicketSearch — full-text search in the customer portal
CK5 Full Window Mode and checklists in the CKEditor 5 editor
TicketUpdateOperationExternalIdentifier — external IDs in automated ticket updates
PostMasterXFromHeader — set customer user from email body content
Hide/Show for dynamic fields in sets and in the agent reply mask

Docker-based installations also switch from Redis cache to filesystem caching for simpler operations.

OTOBO and OTOBO Docker — Independent Release Cycles

From 11.1 onward, OTOBO and OTOBO Docker follow independent release schedules. You can update application and container stack separately — clearer version tags in example files and continuously updated latest images.

Upgrade Notes for Admins

Before moving a production system to 11.1 stable, plan for:

Beta only today — test on staging; keep production on 11.0.x until GA
New folder structure — the update process creates a new layout; manual customisations must be packaged or reapplied
MailAccountOAuth2 — merged into core; review mail account OAuth settings after upgrade
SessionUseCookie = 0 — support removed
Custom kernel code — package changes before upgrade

Download (beta): ftp.otobo.org/pub/otobo/otobo-latest-11.1.tar.gz
Changelog: GitHub rel-11_1 CHANGES.md

How 11.1 Relates to OTOBO 11.0.x

	11.0.x (stable)	11.1 (beta)
Status	Production-ready	Beta — test and give feedback
Focus	CMDB, dynamic fields, ITSM foundation	Agent UX, processes, auth, integration
AI	Third-party add-ons (e.g. OpenTicketAI) via REST API	Similar Tickets → future Rotobo AI
Recommendation	Run production here today	Evaluate on staging; upgrade when stable

For the full 11.0 platform overview — CMDB redesign, dynamic field types, patch history — see our OTOBO Version 11 guide.

Getting Help

Installation & upgrades: OTOBO Documentation and otobo-docs.softoft.de
Professional support: Softoft OTOBO services — health checks, upgrades, and hosting

Keywords: OTOBO 11.1, OTOBO beta, OTOBO Elasticsearch, OTOBO process management, OTOBO OAuth, OpenID Connect OTOBO, OTOBO upgrade, open source ticketing, ITSM, help desk