[{"data":1,"prerenderedAt":821},["ShallowReactive",2],{"navbar-en":3,"footer-en":25,"company-en":65,"blog-post-en-otobo-11-1":152},{"id":4,"extension":5,"items":6,"meta":22,"stem":23,"__hash__":24},"navbar_en/en/_data/navbar.yml","yml",[7,10,13,16,19],{"label":8,"to":9},"Home","/",{"label":11,"to":12},"Services","/services",{"label":14,"to":15},"Blog","/blogs",{"label":17,"to":18},"Booking","/booking",{"label":20,"to":21},"Contact","/contact",{},"en/_data/navbar","0s4EZWfFOzJefxw_XvqUtNphYWEmsyUdeXrL4zEnryI",{"id":26,"columns":27,"extension":5,"meta":62,"stem":63,"__hash__":64},"footer_en/en/_data/footer.yml",[28,38,48],{"title":29,"links":30},"Company",[31,32,35],{"label":20,"to":21},{"label":33,"to":34},"Impressum","/contact/impressum",{"label":36,"to":37},"Data Privacy","/contact/dataprivacy",{"title":11,"links":39},[40,42,45],{"label":41,"to":12},"All Services",{"label":43,"to":44},"Consulting","/services#integration",{"label":46,"to":47},"Support","/services#flexible",{"title":49,"links":50},"Resources",[51,53,56,59],{"label":14,"to":52},"/blog",{"label":54,"to":55},"OTOBO Docs","https://otobo-docs.softoft.de",{"label":57,"to":58},"Znuny Docs","https://znuny-docs.softoft.de/en/",{"label":60,"to":61},"OpenITSMHub","https://openitsmhub.com",{},"en/_data/footer","ru01KVwkTI-zjvMXolvBHRhsXJnb_wJIvjJcy8bAabQ",{"id":66,"contact":67,"descriptor":76,"extension":5,"fullName":77,"meta":78,"metrics":79,"name":92,"partners":93,"qualification":98,"socialMedia":106,"stem":123,"tagline":124,"testimonials":125,"whySoftoft":138,"__hash__":151},"company_en/en/_data/company.yml",{"email":68,"appointmentUrl":69,"googleReviewsUrl":70,"address":71},"info@softoft.de","https://calendar.app.google/fXPHuhqQvx9Gf4LT9","https://www.google.com/maps/place/SoftOft/@50.0040865,8.2451374,17z/data=!3m1!4b1!4m6!3m5!1s0x47bd97c3c5e853d3:0x63a648317d57a53d!8m2!3d50.0040865!4d8.2451374!16s%2Fg%2F11rg8q5d69",{"street":72,"city":73,"zip":74,"country":75},"Am Judensand 7","Mainz","55122","Germany","Ticket System & AI Automation","Softoft Tobias Bück Einzelunternehmen",{},[80,83,86,89],{"value":81,"label":82},"5+","Years of ticket-system experience",{"value":84,"label":85},"5.0 ★","Rating on Google",{"value":87,"label":88},"Top 1000","Kaggle Datasets worldwide",{"value":90,"label":91},"100%","On-premise & privacy-first","Tobias Bück",[94],{"name":95,"description":96,"url":97},"Open Ticket AI","AI-powered ticket classification and routing for on-prem OTOBO/Znuny via REST APIs and Python SDKs","https://openticketai.com",{"heading":99,"intro":100,"bullets":101},"Who is this for?","Best fit for teams with clear ticket-system goals:",[102,103,104,105],"On-premise ticket systems","OTOBO or Znuny teams","REST APIs & Python SDK integrations",">500 tickets per month or AI automation plans",[107,111,115,119],{"platform":108,"url":109,"icon":110},"LinkedIn","https://www.linkedin.com/company/softoft-it-services/","fa-brands:linkedin",{"platform":112,"url":113,"icon":114},"GitHub","https://github.com/Softoft","fa-brands:github",{"platform":116,"url":117,"icon":118},"Kaggle","https://www.kaggle.com/tobiasbueck","simple-icons:kaggle",{"platform":120,"url":121,"icon":122},"Medium","https://medium.com/@softoft","fa-brands:medium","en/_data/company","Your Partner for On-Prem Ticket Automation & AI",[126,131,135],{"text":127,"name":128,"role":129,"company":130},"Tobi did some fine-tuning on our OTOBO ticket system. It was quick and uncomplicated. He knows what he is doing and implements it with creative solutions. Would do it again any time. Thank you!","Dennis Lohmann","Google review","",{"text":132,"name":133,"role":129,"company":134},"Softoft helped us (Vianova Service GmbH) set up the OTOBO ticket system. Everything worked out well.","Reinhard Sczech","Vianova Service GmbH",{"text":136,"name":137,"role":129,"company":130},"SoftOft helped us further develop our website. Fast, uncomplicated, affordable! Happy to work with them again!","Jochen Petersen",[139,142,145,148],{"icon":140,"text":141},"heroicons:star-20-solid","Less manual triage — your team replies faster",{"icon":143,"text":144},"heroicons:rocket-launch-20-solid","Live in weeks, not months",{"icon":146,"text":147},"heroicons:shield-check-20-solid","Your data never leaves your servers",{"icon":149,"text":150},"heroicons:user-20-solid","A direct line to the expert — no middlemen","4ybQcZov1bdfjDMPhJjfYr_SrSBATncI9Z8P9mqP32k",{"id":153,"title":154,"author":155,"blogId":156,"body":157,"description":808,"extension":809,"externalUrl":810,"layout":810,"mainImage":811,"meta":812,"mobileImage":811,"navigation":813,"order":814,"path":815,"publishedAt":810,"seo":816,"stem":817,"tags":818,"__hash__":820},"blog_en/en/blog/otobo-11-1.md","OTOBO 11.1 Beta: What's New — Ticket Handling, Process Management & Integration","Tobias Bueck","otobo-11-1",{"type":158,"value":159,"toc":781},"minimark",[160,164,186,210,215,255,259,262,267,287,291,306,310,316,320,327,331,334,387,393,397,404,411,415,419,426,430,436,440,451,467,471,475,493,497,515,525,529,532,568,575,579,597,601,604,636,653,657,735,741,745,772,775],[161,162,154],"h1",{"id":163},"otobo-111-beta-whats-new-ticket-handling-process-management-integration",[165,166,167,171,172,175,176,181,182,185],"p",{},[168,169,170],"strong",{},"OTOBO 11.1"," is available as a ",[168,173,174],{},"beta release"," (24 June 2026). Where ",[177,178,180],"a",{"href":179},"/en/blog/otobo-version-11","OTOBO Version 11"," established the new CMDB, dynamic fields, and Docker-first platform, 11.1 focuses on ",[168,183,184],{},"quality-of-life improvements"," where agents and admins spend most of their time: ticket handling, process modeling, security, and integration.",[187,188,189],"blockquote",{},[165,190,191,194,195,198,199,202,203,209],{},[168,192,193],{},"Release status:"," 11.1 is beta. Production systems should stay on the stable ",[168,196,197],{},"11.0.x"," line (latest: ",[168,200,201],{},"11.0.16",", April 2026) until the stable 11.1 release. Official release notes: ",[177,204,208],{"href":205,"rel":206},"https://otobo.io/en/otobo-11-1-beta/",[207],"nofollow","otobo.io/en/otobo-11-1-beta",".",[211,212,214],"h2",{"id":213},"highlights-at-a-glance","Highlights at a Glance",[216,217,218,225,231,237,243,249],"ul",{},[219,220,221,224],"li",{},[168,222,223],{},"Ticket handling"," — richer Elasticsearch search, Similar Tickets widget, article edit/pin in core, parallel list filters",[219,226,227,230],{},[168,228,229],{},"Process management"," — namespaces, global vs. process-specific elements, Not/Any/All transition logic",[219,232,233,236],{},[168,234,235],{},"Dynamic fields"," — stronger reference lenses and sets; less context switching in Ticket Zoom",[219,238,239,242],{},[168,240,241],{},"Security & auth"," — OAuth token management, OpenID Connect SSO, encrypted DB connectivity (DBD::MariaDB)",[219,244,245,248],{},[168,246,247],{},"Integration"," — multipart web services, configuration and object import/export built into core",[219,250,251,254],{},[168,252,253],{},"Packaging"," — several former add-on packages merged into the standard (Elasticsearch extension, article edit, process templates, and more)",[211,256,258],{"id":257},"ticket-handling-better-overview-faster-results","Ticket Handling — Better Overview, Faster Results",[165,260,261],{},"Agents spend most of their day inside tickets. 11.1 targets exactly that workflow.",[263,264,266],"h3",{"id":265},"elasticsearch-search-at-a-new-level","Elasticsearch — Search at a New Level",[165,268,269,270,273,274,278,279,282,283,286],{},"The ",[168,271,272],{},"Elasticsearch extension is now part of core",". Search supports additional dialogues, field-based queries, and extended syntax — for example ",[275,276,277],"code",{},"Title:Test* AND Body:Test*"," or Boolean operators with ",[275,280,281],{},"AND"," / ",[275,284,285],{},"NOT",". Teams already using Elasticsearch should notice more precise, concurrent search immediately.",[263,288,290],{"id":289},"similar-tickets-widget","Similar Tickets Widget",[165,292,293,294,297,298,305],{},"A new ",[168,295,296],{},"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 ",[168,299,300],{},[177,301,304],{"href":302,"rel":303},"https://otobo.io/en/otobo-is-becoming-ai-powered/",[207],"OTOBO AI (Rotobo)",", planned for a broader release in September 2026.",[263,307,309],{"id":308},"article-editing-in-core","Article Editing in Core",[165,311,312,315],{},[168,313,314],{},"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.",[263,317,319],{"id":318},"parallel-filters-in-ticket-lists","Parallel Filters in Ticket Lists",[165,321,322,323,326],{},"Ticket overviews now support ",[168,324,325],{},"multiple filters in parallel",". Configure the view once and return to it with one click — no repeated manual re-filtering on long lists.",[211,328,330],{"id":329},"process-management-model-with-precision","Process Management — Model with Precision",[165,332,333],{},"Complex process setups grow quickly. 11.1 adds structure and control for admins who maintain them.",[216,335,336,342,348,369,375,381],{},[219,337,338,341],{},[168,339,340],{},"Namespaces"," group process elements logically so large workflows stay navigable",[219,343,344,347],{},[168,345,346],{},"Global vs. process-specific"," elements — a checkbox decides whether an element is shared across all processes or limited to one",[219,349,350,353,354,357,358,361,362,365,366],{},[168,351,352],{},"Transition logic"," supports ",[168,355,356],{},"Not",", ",[168,359,360],{},"Any",", and ",[168,363,364],{},"All",", including checks for empty fields; dynamic fields inside a set can be addressed as ",[275,367,368],{},"Field1::Field2",[219,370,371,374],{},[168,372,373],{},"Ticket templates in process dialogs"," — templates from the familiar ticket UI now work in process dialogues too",[219,376,377,380],{},[168,378,379],{},"Customer interface"," — process and activity details can be hidden so customers see only what they need",[219,382,383,386],{},[168,384,385],{},"Improved sorting"," for process elements in the admin area",[165,388,389,392],{},[168,390,391],{},"Process ticket templates"," are now core — no separate package required.",[211,394,396],{"id":395},"dynamic-fields-information-where-it-is-needed","Dynamic Fields — Information Where It Is Needed",[165,398,399,400,403],{},"Reference-type dynamic fields link FAQ articles, services, customers, customer users, or ConfigItems to tickets (or to each other). ",[168,401,402],{},"Lens fields"," show linked object details inside the ticket without opening another screen.",[165,405,406,407,410],{},"11.1 extends this further: lens fields can point directly to reference fields and to ",[168,408,409],{},"sets",", reducing clicks and context switching per ticket.",[211,412,414],{"id":413},"security-modern-authentication-secure-connectivity","Security — Modern Authentication, Secure Connectivity",[263,416,418],{"id":417},"oauth-token-management","OAuth Token Management",[165,420,421,422,425],{},"OTOBO now includes ",[168,423,424],{},"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.",[263,427,429],{"id":428},"openid-connect-sso","OpenID Connect (SSO)",[165,431,432,435],{},[168,433,434],{},"OpenID Connect"," enables single sign-on for agents and customers. One corporate login can cover OTOBO and other systems — no separate OTOBO passwords required.",[263,437,439],{"id":438},"encrypted-database-connectivity","Encrypted Database Connectivity",[165,441,442,443,446,447,450],{},"The DB backend moves from ",[168,444,445],{},"DBD::mysql"," to ",[168,448,449],{},"DBD::MariaDB"," — actively maintained and aligned with current MySQL/MariaDB versions. Encrypted connectivity is available; authentication plugins can be selected in the installer.",[187,452,453],{},[165,454,455,458,459,462,463,466],{},[168,456,457],{},"Upgrade warning:"," The ",[168,460,461],{},"MailAccountOAuth2"," package has been ",[168,464,465],{},"merged into core",". Manual adjustments are required during upgrade if you used that package separately.",[211,468,470],{"id":469},"data-exchange-integration-simplified","Data Exchange & Integration — Simplified",[263,472,474],{"id":473},"web-services","Web Services",[216,476,477,484,487],{},[219,478,479,480,483],{},"Attachments via ",[168,481,482],{},"multipart/form-data"," — required for direct integration with JIRA, OpenProject, and similar systems",[219,485,486],{},"Outgoing data can enforce specific formats (e.g. arrays) in XSLT",[219,488,489,492],{},[168,490,491],{},"OAuth"," as authentication for outgoing web services",[263,494,496],{"id":495},"import-export-in-core","Import & Export in Core",[216,498,499,505],{},[219,500,501,504],{},[168,502,503],{},"Configuration packages"," — processes, dynamic fields, notifications, queues, ACLs — export to CSV and re-import from the respective admin screens",[219,506,507,510,511,514],{},[168,508,509],{},"Standard objects"," — tickets, customers, customer users, and ConfigItems via ",[168,512,513],{},"Admin → Import/Export"," for migration or data exchange",[165,516,517,518,357,521,524],{},"Former packages ",[168,519,520],{},"ImportExportStandardObjects",[168,522,523],{},"ImportExportCustomerCompany",", and related tools are now part of the standard.",[211,526,528],{"id":527},"other-notable-core-integrations","Other Notable Core Integrations",[165,530,531],{},"Several community packages moved into 11.1 core, including:",[216,533,534,540,550,556,562],{},[219,535,536,539],{},[168,537,538],{},"CustomerTicketSearch"," — full-text search in the customer portal",[219,541,542,545,546,549],{},[168,543,544],{},"CK5 Full Window Mode"," and ",[168,547,548],{},"checklists"," in the CKEditor 5 editor",[219,551,552,555],{},[168,553,554],{},"TicketUpdateOperationExternalIdentifier"," — external IDs in automated ticket updates",[219,557,558,561],{},[168,559,560],{},"PostMasterXFromHeader"," — set customer user from email body content",[219,563,564,567],{},[168,565,566],{},"Hide/Show"," for dynamic fields in sets and in the agent reply mask",[165,569,570,571,574],{},"Docker-based installations also switch from Redis cache to ",[168,572,573],{},"filesystem caching"," for simpler operations.",[211,576,578],{"id":577},"otobo-and-otobo-docker-independent-release-cycles","OTOBO and OTOBO Docker — Independent Release Cycles",[165,580,581,582,545,585,588,589,592,593,596],{},"From 11.1 onward, ",[168,583,584],{},"OTOBO",[168,586,587],{},"OTOBO Docker"," follow ",[168,590,591],{},"independent release schedules",". You can update application and container stack separately — clearer version tags in example files and continuously updated ",[275,594,595],{},"latest"," images.",[211,598,600],{"id":599},"upgrade-notes-for-admins","Upgrade Notes for Admins",[165,602,603],{},"Before moving a production system to 11.1 stable, plan for:",[605,606,607,613,619,624,630],"ol",{},[219,608,609,612],{},[168,610,611],{},"Beta only today"," — test on staging; keep production on 11.0.x until GA",[219,614,615,618],{},[168,616,617],{},"New folder structure"," — the update process creates a new layout; manual customisations must be packaged or reapplied",[219,620,621,623],{},[168,622,461],{}," — merged into core; review mail account OAuth settings after upgrade",[219,625,626,629],{},[168,627,628],{},"SessionUseCookie = 0"," — support removed",[219,631,632,635],{},[168,633,634],{},"Custom kernel code"," — package changes before upgrade",[165,637,638,639,644,647,648],{},"Download (beta): ",[177,640,643],{"href":641,"rel":642},"https://ftp.otobo.org/pub/otobo/otobo-latest-11.1.tar.gz",[207],"ftp.otobo.org/pub/otobo/otobo-latest-11.1.tar.gz",[645,646],"br",{},"\nChangelog: ",[177,649,652],{"href":650,"rel":651},"https://github.com/RotherOSS/otobo/blob/rel-11_1/CHANGES.md",[207],"GitHub rel-11_1 CHANGES.md",[211,654,656],{"id":655},"how-111-relates-to-otobo-110x","How 11.1 Relates to OTOBO 11.0.x",[658,659,660,679],"table",{},[661,662,663],"thead",{},[664,665,666,669,674],"tr",{},[667,668],"th",{},[667,670,671],{},[168,672,673],{},"11.0.x (stable)",[667,675,676],{},[168,677,678],{},"11.1 (beta)",[680,681,682,696,709,722],"tbody",{},[664,683,684,690,693],{},[685,686,687],"td",{},[168,688,689],{},"Status",[685,691,692],{},"Production-ready",[685,694,695],{},"Beta — test and give feedback",[664,697,698,703,706],{},[685,699,700],{},[168,701,702],{},"Focus",[685,704,705],{},"CMDB, dynamic fields, ITSM foundation",[685,707,708],{},"Agent UX, processes, auth, integration",[664,710,711,716,719],{},[685,712,713],{},[168,714,715],{},"AI",[685,717,718],{},"Third-party add-ons (e.g. OpenTicketAI) via REST API",[685,720,721],{},"Similar Tickets → future Rotobo AI",[664,723,724,729,732],{},[685,725,726],{},[168,727,728],{},"Recommendation",[685,730,731],{},"Run production here today",[685,733,734],{},"Evaluate on staging; upgrade when stable",[165,736,737,738,209],{},"For the full 11.0 platform overview — CMDB redesign, dynamic field types, patch history — see our ",[177,739,740],{"href":179},"OTOBO Version 11 guide",[211,742,744],{"id":743},"getting-help","Getting Help",[216,746,747,762],{},[219,748,749,752,753,545,757],{},[168,750,751],{},"Installation & upgrades:"," ",[177,754,756],{"href":755},"/en/blog/otobo-docs","OTOBO Documentation",[177,758,761],{"href":759,"rel":760},"https://otobo-docs.softoft.de/en/other/otobo-version-11/",[207],"otobo-docs.softoft.de",[219,763,764,752,767,771],{},[168,765,766],{},"Professional support:",[177,768,770],{"href":769},"/en/services","Softoft OTOBO services"," — health checks, upgrades, and hosting",[773,774],"hr",{},[165,776,777,780],{},[168,778,779],{},"Keywords:"," OTOBO 11.1, OTOBO beta, OTOBO Elasticsearch, OTOBO process management, OTOBO OAuth, OpenID Connect OTOBO, OTOBO upgrade, open source ticketing, ITSM, help desk",{"title":130,"searchDepth":782,"depth":782,"links":783},2,[784,785,792,793,794,799,803,804,805,806,807],{"id":213,"depth":782,"text":214},{"id":257,"depth":782,"text":258,"children":786},[787,789,790,791],{"id":265,"depth":788,"text":266},3,{"id":289,"depth":788,"text":290},{"id":308,"depth":788,"text":309},{"id":318,"depth":788,"text":319},{"id":329,"depth":782,"text":330},{"id":395,"depth":782,"text":396},{"id":413,"depth":782,"text":414,"children":795},[796,797,798],{"id":417,"depth":788,"text":418},{"id":428,"depth":788,"text":429},{"id":438,"depth":788,"text":439},{"id":469,"depth":782,"text":470,"children":800},[801,802],{"id":473,"depth":788,"text":474},{"id":495,"depth":788,"text":496},{"id":527,"depth":782,"text":528},{"id":577,"depth":782,"text":578},{"id":599,"depth":782,"text":600},{"id":655,"depth":782,"text":656},{"id":743,"depth":782,"text":744},"OTOBO 11.1 beta brings faster ticket handling, stronger process management, OAuth and OpenID Connect, import/export in core, and packages merged into the standard release. Overview of highlights, upgrade notes, and what to expect before stable.","md",null,"/images/blog/otobo-version-11.webp",{},true,901,"/en/blog/otobo-11-1",{"title":154,"description":808},"en/blog/otobo-11-1",[819],"otobo","HMY-F6vr12QqmgRGduKBO9b6yuvdsKR3wD-7g5WoQS0",1783234383526]