• 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ü
Ansicht von 2 Antwort-Threads
  • Autor
    Beiträge
    • 24. November 2020 um 11:01 Uhr - Views: 1150 #10248
      Linda
      Teilnehmer

        Hi,

        I’ve set the Priority Matrix as follows:

        When creating a new ticket, the Service Criticality is set to 1 – Critical. I have made it so that an Agent/Customer has to fill in the Impact field (ITSMImpact). But no matter what I fill in the Impact field, it will always set the Priority to 1 – Critical. It seems the calculation is not being done right, but I can’t figure out why/how.

        On the other hand, when the ticket is being created in the Customer Portal, it will set the priority to the default value, and it will not change it based on the Criticality / Impact, it will always remain the default value.

        In addition to this, the Criticality seems to be linked to the Service, however, for our ticket system a service can have all four criticalities, is it possible to unlink Criticality from Service and make it so an Agent/Customer has to fill in Criticality as a dynamic field, the same way that Impact is filled in, and then the matrix calculates the right priority based on those two fields. At the moment I made it so that an Agent/Customer has to fill in both Criticality and Impact in the form, but it seems that the Criticality field is being overwritten by the Criticality that is linked to the service.

        Thank you in advance.

      • 30. November 2020 um 8:25 Uhr #10330
        Sven Oesterling
        Administrator

          Hello Linda,

          first your second point – you can just add the dynamic field ITSMCriticality to the forms in the admin area (Dynamic Field Screens).

          Regarding the calculation – I will have a look at this, as soon as I have time for it.

          Best regards, Sven

        • 1. Dezember 2020 um 12:20 Uhr #10334
          Linda
          Teilnehmer

            Hi,

            I did add the ITSMCriticality field to the form. But the system overwrites this criticality with the critcality that is linked to the service.

            Kind regards,

            Linda

        • Autor
          Beiträge
        Ansicht von 2 Antwort-Threads
        • 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

        • Dynamische Felder in AgentTicketNote mit ACL verstecken
        • FAQ: kaputtes Copy & Paste von Bildern zwischen Artikeln
        • 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