OTOBO 11.1 – Features, Install & Upgrade

In this guide: What stable OTOBO 11.1 changes, which tag to install, and what the upgrade from 11.0 or from the 11.1 beta requires.

Related: OTOBO 11.0 features · Installation · Docker Compose · Updating

OTOBO 11.1 is the current stable minor release of the open-source ticket system. Rother OSS published it as stable on 26 October 2026 (English announcement dated 27 October 2026). The Git tag is rel-11_1_1, recorded in CHANGES.md as OTOBO 11.1.1. It builds on the OTOBO 11.0 CMDB, dynamic forms, and Docker stack.

Official notes: OTOBO 11.1. Beta history: Beta, Beta2, Beta3. Source changelog: CHANGES.md on rel-11_1.

Release status

Build	Date	Role
11.1.0 Beta	24 June 2026	First public beta
11.1.0 Beta2	27 July 2026	Security patch (upload-cache session binding, CSRF on ticket actions, template XSS)
11.1.0 Beta3	16 September 2026	Security patch. High-severity HTTP Basic Auth session takeover in specific setups
11.1.1	26 October 2026	Stable. Tag rel-11_1_1 on otobo and otobo-docker

Install 11.1.1. Beta3 is not the current build. From 11.1 onward, the application and the Docker project have separate release cycles, so a later Docker tag may not share the application patch number. Check both repositories before you pin a tag. Example files now state versions more clearly, and latest images stay maintained.

Support windows published on the OTOBO download page:

Line	Released	End of life
11.1	October 2026	Not before October 2029
11.0	May 2024	Not before May 2028
10.1	May 2022	May 2027 (six months after 11.1)
10.0	July 2020	1 January 2026 (already ended)

Ticket handling

Agents spend most of the day in the ticket. 11.1 shortens that work.

• Elasticsearch in core. Extra dialogs, field queries, and boolean syntax such as Title:Test* AND Body:Test* or AND / NOT. Boost-suffix weights on search-field attributes are fully supported. Article edits are indexed correctly. You do not install the Elasticsearch extension package anymore.
• Similar Tickets. An Elasticsearch widget on Ticket Zoom shows related tickets without a manual search. Nothing extra to enable when Elasticsearch is already running.
• Article history. Editing, including time accounting, is standard. In Ticket Zoom you can edit, delete, or pin articles. External article bodies (not emails), article dynamic fields, and attributes such as visibility are editable. The editor can open full-window and insert checklists (CKEditor 5).
• List filters. Ticket lists accept several filters at once and keep that view.
• Customer lists. After a set period (24 hours by default), ticket lists switch from ticket age to creation time.
• Customer search. Full-text search in the customer portal is in core.

Process management

• Namespaces group process elements so large setups stay sortable. Sorting in the admin area takes those namespaces into account.
• Global or process-specific. A checkbox marks an element as available in every process or only in one. Copying a process with private elements now rewrites layout and path correctly.
• Transitions support Not, Any, and All, including empty-field checks. Fields inside a set are addressed as Field1::Field2. Array operators also apply to Dynamic Field sets.
• Transition actions. DynamicFieldSet accepts an ExternalSource parameter so incoming values can be treated as an external source. TicketCustomerSet accepts reference-field values passed with the _Data tag.
• Templates in process dialogs. Ticket templates work in process dialogs and can select the next ticket state.
• Customer interface. Process and activity details can be hidden so customers see only what they need.
• Dynamic fields as control data. Reference fields are used instead of raw object IDs, and field sets can drive the process.

Dynamic fields

Reference fields link FAQ articles, services, customers, customer users, or config items to a ticket or to each other. Lens fields can point at references and at sets, so agents see linked details without opening the object. Multi-value reference fields show multiple links (Ticket Zoom and Config Zoom first; more screens follow).

Other field changes:

• ACLs apply to fields inside a set, and also on the agent reply screen.
• Customer reply dialogs can be assigned in Dynamic Field screens.
• Database-type dynamic fields can sit inside sets, with tighter filters for which database fields are selectable.
• Script fields can use FieldTypeSettings.
• Admin → Dynamic Fields can filter by field type.
• Set rendering in the Ticket Zoom dynamic-field widget uses a clearer layout.
• Hide/show for sets, lenses, and reference fields was fixed, including the article area on customer ticket creation when the form updates dynamically.
• Mandatory autocomplete reference fields validate correctly. Import/export no longer drops reference-field attributes.
• Clearing script-field update events is stored in the database.

Security and authentication

• OAuth token management is in core (the former MailAccountOAuth2 package). Tokens cover POP, IMAP, and now SMTP, plus outgoing web services. Password changes are managed in one place.
• OpenID Connect is single sign-on for agents and customers. Separate OTOBO passwords are optional when the corporate identity provider is connected.
• Web services accept OIDC/OAuth2. Outgoing calls can force XSLT data types such as array or boolean, and can send multipart/form-data attachments (required by Jira, OpenProject, and similar APIs).
• Database driver. The backend moves from DBD::mysql to DBD::MariaDB. Encrypted connections for MySQL and MariaDB are available, and the installer lets you pick the authentication plugin. A daemon crash in DBD::MariaDB disconnect_all() during global destruction (seen on Beta1 with DBD::MariaDB 1.24) is fixed.
• Nginx sets server_tokens off.
• Beta security fixes stay in 11.1.1: session-bound upload cache, CSRF on MarkAsImportant and QuickClose, template XSS, and the high-severity HTTP Basic Auth session takeover.
• 11.1.1 also checks permission on EmailOutbound and Forward regardless of subaction (#6220).

Data exchange and administration

• Configuration CSV. Processes, dynamic fields, notifications, queues, and ACLs export to CSV and import again from the screen where you edit them.
• Object import/export lives under Admin → Import/Export for tickets, customers, customer users, and config items. Customer-company import includes dynamic field values. These were the packages ImportExportCustomerCompany and ImportExportStandardObjects.
• External ticket updates can use the external system’s identifier (former TicketUpdateOperationExternalIdentifier package).
• PostMaster. Customer users can be set from information in the email body (former PostMasterXFromHeader package). Filters have a validity state, the overview shows a “stop after match” indicator, and attachment detection was rewritten.
• LDAP. Nested sync uses the full memberurl attribute.
• Reports. Docker chart rendering uses Gnuplot instead of Chromium (#3550), which shrinks the image and drops browser-only dependencies. Build a local image if you still want Chromium charts. The default of Stats::CustomerUserLoginsAsMultiSelect changed (#6296).
• Docker cache is a file-system cache instead of Redis (#5728).
• Native systemd no longer depends on entrypoint.sh.
• Backups can follow symlinks.
• Customer UI. New CSS color variable for links, wider selection lists, corrected placeholder-avatar initials, and accessibility fixes (selection fields no longer use the ARIA role search; main navigation was adjusted).
• Rich text. Font size and line height were reworked. Editor menus are no longer clipped by overflow: hidden on .FieldCell and .RichTextField. CKEditor height calculation was corrected.

Packages merged into the framework

Do not reinstall these as separate packages on 11.1:

Former package	What you get in core
Elasticsearch extension	Field search, similar tickets, article-edit indexing
ExtendedArticleEdit	Edit, delete, and pin articles, including time accounting
CK5-FullWindowMode	Full-window editor and checklists
CustomerTicketSearch	Full-text search in the customer portal
ProcessTicketTemplates	Ticket templates inside process dialogs
ImportExportCustomerCompany	Customer import/export, including dynamic fields
ImportExportStandardObjects	Tickets, customer users, and config items under Admin → Import/Export
TicketUpdateOperationExternalIdentifier	Match external systems by their ticket identifier
PostMasterXFromHeader	Set the customer user from the email body
MailAccountOAuth2	Central OAuth tokens for mail and outgoing web services

Bugfixes shipped with 11.1.1

These are the fixes called out in the stable release notes, on top of the beta line:

• Upgrade interruptions, including ITSM systems failing the move to 11.1, and DBUpdate-to-11.1.pl failing when long-lived databases lack ProcessManagement dynamic fields. The script now returns a sensible exit code.
• Elasticsearch migration when no Elasticsearch web service exists.
• Nested-queue permission check in AgentTicketQueue that was too strict after #6092.
• TicketACL::Autoselect inside processes.
• Zero values missing from customer information in Ticket Zoom.
• Core dump during Maint::PostMaster::MailAccountFetch on the 11.1 branch.
• Missing index on article_version.source_article_id.
• Lens-on-set errors that corrupted import data, and lens set values that reset the AJAX form update when a reference field reappeared.
• Selection menus and narrow customer-interface dropdowns.
• Invalid package install showing no error, duplicate Kerberos Nginx template entries, and foreign-key checks left enabled in Kernel::System::DB::new().

Install OTOBO 11.1

Docker remains the recommended path.

1. Clone otobo-docker at tag rel-11_1_1 (11.0 uses rel-11_0; the latest 11.0 tag at the time of the 11.1 release is rel-11_0_18).
2. Copy .docker_compose_env_http or .docker_compose_env_https to .env and set OTOBO_DB_ROOT_PASSWORD.
3. Start the stack and open http://your-host/otobo/installer.pl. Leave the database host as db. Choose the database authentication plugin in the installer when you need encrypted MariaDB or MySQL.

Native install (Ubuntu or RHEL) downloads a tarball from ftp.otobo.org/pub/otobo/, unpacks it to /opt/otobo, installs Perl dependencies, and fronts Gazelle with Nginx. Step-by-step sources: 11.1 installation manual, Ubuntu, Docker. Our installation overview compares tags for 11.1, 11.0, and 10.1.

Upgrade to OTOBO 11.1

The 11.1 Ubuntu update guide covers 11.0 → 11.1. Patch moves inside 11.1 skip the database migration. Beta users follow the same path onto 11.1.1.

1. Stop the web server and the OTOBO daemon.
2. Back up /opt/otobo and the database.
3. Package local file changes. On Docker the updater writes a backup to /opt/otobo_update/ and will not keep unpackaged edits.
4. Unpack the new release over /opt/otobo, or check out rel-11_1_1 in otobo-docker.
5. Install the Perl modules the 11.1 guide lists for Ubuntu or Debian before the migration.
6. Run scripts/DBUpdate-to-11.1.pl only when leaving 11.0 (or a 11.1 beta that has not had the migration applied).
7. Migrate mail OAuth. MailAccountOAuth2 is no longer an add-on; follow the OAuth migration steps in the 11.1 release notes.
8. Rebuild configuration and start services. Confirm statistics charts. They render with Gnuplot. Keep Chromium only by building a local image, as described in those release notes.

[!IMPORTANT] Three backend changes need a manual step: the Docker backup directory /opt/otobo_update/, the MailAccountOAuth2 merge, and Gnuplot instead of Chromium for report charts.

How 11.1 compares with other versions

Line	Install this when	Docker tag	Support
11.1.1	New production systems	rel-11_1_1	Stable since 26 October 2026. End of life not before October 2029
11.0	You must stay on 11.0	rel-11_0 (latest tag rel-11_0_18)	Supported. End of life not before May 2028
10.1	You must stay on 10.x	rel-10_1	Security patches until May 2027
10.0	Do not install	—	End of life 1 January 2026

See OTOBO version 11 for the 11.0 feature set (CMDB, dynamic forms, Docker) that 11.1 extends.

Frequently asked questions

Is OTOBO 11.1 ready for production?

Yes. OTOBO 11.1 left beta on 26 October 2026. The stable patch is OTOBO 11.1.1 (Git tag rel-11_1_1). Rother OSS supports this line at least until October 2029. Move beta systems to 11.1.1; do not stay on 11.1.0 Beta3.

How do I install OTOBO 11.1?

Prefer Docker Compose and check out otobo-docker tag rel-11_1_1. Copy the HTTP or HTTPS env file to .env, set OTOBO_DB_ROOT_PASSWORD, and open installer.pl. A native install uses the tarball from https://ftp.otobo.org/pub/otobo/ and the official 11.1 installation guide.

What must I change when upgrading to OTOBO 11.1?

Back up first, then run the 11.0-to-11.1 database update. On Docker the updater writes a backup under /opt/otobo_update/, so package manual changes before the upgrade. MailAccountOAuth2 is now in core and needs a manual OAuth migration. Report charts use Gnuplot instead of Chromium unless you build a local image that keeps Chromium.