• Deutsch
  • English
  • Anmeldung OTOBO Community
+49 (0)9427 68 39 000
OTOBO
  • SOFTWARE
    • Software | Überblick
    • IT Service Management
    • Customer Service Management
    • Enterprise Service Management
    • Demo
    • Download
    • Dokumentation
  • SERVICES
    • Überblick Services
    • Beratung
    • Training
    • Entwicklung
    • OTRS Migration zu OTOBO
    • Support
    • Managed Service
    • Support-Portal
  • UNTERNEHMEN
    • Über uns
    • Karriere
    • Partner
    • Kontakt
    • Newsletter
  • RESSOURCEN
  • COMMUNITY
    • Open Source
    • Community Forum
    • Download
    • Dokumentation
    • OTOBO übersetzen
  • Click to open the search input field Click to open the search input field Suche
  • Menü Menü

Schlagwörter: CMDB

Ansicht von 1 Antwort-Thread
  • Autor
    Beiträge
    • 16. April 2025 um 13:19 Uhr - Views: 1138 #34868
      James Mohr
      Teilnehmer

        Greetings!

        I just installed Otobo 11.0 and have added ITSM, Change Management, Configuration Management, FAQ, and a couple of other packages.

        From what I see, the only way to „categorize“ a ticket is by assigning it to a specific queue. For example, I have a ticket concerning a problem with a particular software. It will be handled by a specific team (SysAdmin)  so I would put it in that queue. However, I want to keep track of the fact that a ticket was opened for this particular software, so I want to assign it the category for this software. (for example) I see no way of categoring tickets like this.

        Creating individual queues for all of the categories is impracticle as our taxonomy is already close to 400 entries and it will increase substantially in the near future. Is there an easy way to assign categories to tickets?

        Since there is an obvious relationship between tickets and the FAQ, it makes sense that the taxonomy is the same. However, I do not see any way to add categories to FAQ articles. What am I missing?

        Thanks in advance.

      • 29. Juli 2025 um 11:10 Uhr #35706
        Dmytro Gierman
        Teilnehmer

          Hi,

          You can create a sub-categories, thus making a complex tree, e.g.

          SysAdmin
          SysAdmin::Hardware
          SysAdmin::Hardware::mac
          SysAdmin::Hardware::IBM
          SysAdmin::Software
          SysAdmin::Software::Window
          SysAdmin::Software::Linux
          etc

          Each category and sub-category is assigned to an Agents group, so having a few core teams you could still have a complex structure with dosens or even hundreds Queues.

          Another way to go is to use a „Service“ entity, which is ortogonal to Queues. In the new ticket form the client will see a „Service“ dropdown. I didn’t dive into Services though, you have to play with it on a test installation.
          Warning! once you enabled services, you see this „Service“ fields in many views in Otobo, and to disable them you have to search a lot in the „System config“ section.

          Regards!

      • Autor
        Beiträge
      Ansicht von 1 Antwort-Thread
      • Du musst angemeldet sein, um auf dieses Thema antworten zu können.

      Foren durchsuchen

      Anmeldung

      Anmeldung

      Konto erstellen
      Passwort vergessen?

      Login via Social

      Profil

      Bitte vervollständigen Sie nach der Registrierung Ihr Profil, das vereinfacht die spätere Kommunikation enorm. Ihre Profileinstellung finden Sie, wenn Sie auf Ihr Avatarbild klicken.

      Sie können Ihren Avatar ändern, indem Sie sich mit Ihrer E-Mail-Adresse unter gravatar.com registrieren.

      Letzte Aktivitäten

      • FAQ: kaputtes Copy & Paste von Bildern zwischen Artikeln
      • Dynamische Felder in AgentTicketNote mit ACL verstecken
      • Benachrichtigung „Ticket wurde mir entzogen“ möglich?
      • Statistik Anzahl Tickets pro Agent
      • Docker: Ändern des redis Hosts

      Unternehmen

      Über uns
      Karriere
      Stellenbörse
      Partner werden
      Kontakt
      Newsletter

      OTOBO | Simplify work and create exceptional service experiences.

      Die Source Code Owner und Maintainer hinter OTOBO.

      Software

      Service Management-Plattform
      OTOBO Demo
      OTOBO Download
      OTOBO Dokumentation

      Security-Problem melden:
      security@otobo.org

      Services

      Support-Portal
      Beratung
      Training
      Support
      Managed Services
      Erweiterung
      OTRS Migration
      Partner finden

      Community

      Open Source
      Community Forum
      Mitmachen
      OTOBO Developer
      OTOBO@GitHub

      © 2026 Rother OSS GmbH | All rights reserved.
      • Cookie-Einstellungen
      • Impressum
      • Datenschutz
      • Haftungsausschluss
      Nach oben scrollen Nach oben scrollen Nach oben scrollen