Skip to main content
Matrix42 Self-Service Help Center

Incident

Overview

An incident is reported by a customer that does not belong to the standard operation of a service and actually or potentially causes an interruption or reduction of service quality. An incident is the first instance in service management for which the support employee creates a ticket. If the incident can be sorted out immediately, the ticket and the incident are closed. If it is not possible, the support employee can convert the incident into a problem or a change.

incident.jpg

General

  • User: Person who reported the incident.
  • Phone: Callback - Telephone number for inquiries. This information is automatically entered by the system, if available. If it is changed later, the new number is not written back to Active Directory/LDAP. It is also not written back to the master data under Master Data > Users > Persons.
  • User Reachable at: Time at which the person can be reached by the specified phone number.
  • Details: Information about users (AccountsOrg. UnitLocationCost Center and E-Mail).
  • History: Further reported incidents of the user. These incidents can be filtered by status.

Reported CIS:

  • Asset: Link an asset from Matrix42 Asset Management with this incident to start remote support or manage the mobile terminal equipment that is imported by using Matrix42 Mobile Device Management. The selection list is filtered automatically so that you can select only the assets of the person who reports the incident.
  • Service: Link a service from Matrix42 Service Catalog with this incident to start remote support (for example). The selection list is filtered automatically so that you can select only the services of the person who reports the incident.
  • Show all assets and services: Select this option to turn off the automatic filter that is used for selection of assets and services.

Affected CIs:

  • Asset: actually affected asset can be different from the reported asset (e.g., a user reports an incident for own PC, but actually the email server has a problem). If a tighter SLA is available for the affected asset, you will be asked to use the new SLA after you specify the asset.
  • Service: The actually affected service can be different from the reported service (e.g., a user reports an incident for Outlook but actually the Internet connection is down). ). If a tighter SLA is available for the affected asset, you will be asked to use the new SLA after you specify the service.
  • Show all assets and services: Select this checkbox to turn off the automatic filter that is used for selection of assets and services.

The reported and affected assets and services are automatically added to the Assets and Services dialog pages under Related Objects.

  • Quick Call: Select a quick call template for reporting a specific incident.
  • Summary: Brief description of the incident.
  • Category: Category for organizing your incidents.
  • SLA: Link to a Service Level Agreement. The predefined reaction and solution times depend on this. The selection list is filtered automatically so that you can select only those Service Level Agreements that result from combination of entries in the UserAssetService, and Priority fields.
  • Show All: Select this option to turn off the automatic filter that is used for selection of SLA/OLA/UC.
  • Get SLA: Automatically select the Service Level Agreement/Operation Level Agreement or Underpinning Contract with the most critical solution times. The selected agreement should correspond to the combination of the entries in the UserAssetService, and Priority fields.
  • Impact: Select a group (UserWorkgroup, or Company) which is affected by this incident. If a related asset or service has a higher business impact, then this higher business impact will be applied automatically when the ticket is saved.
  • Urgency: Urgency level for solution of this ticket.
  • Reported Per: Select how this ticket was reported. This data is purely informative and is not processed by the system.
  • Resubmission: Date on which the person or responsible role receives an email reminder about the ticket. The email contains a link by which the ticket can be accessed.
  • Inform responsible roles or users via email: By default, members of roles that are responsible for a ticket are notified by email when work starts on it. You can turn off this option here.
  • Description: Detailed description of the incident. Link a quick call template to pre-fill the description with the content of the template description, if the description was empty before. As long as the incident has the New status, opening of the ticket points to this tabulator.
  • Journal/Activities: In the journal, all actions that were made for the ticket will be automatically recorded. This also includes mails that were received for this ticket or sent out of the ticket. Each journal entry can be marked as Visible in Portal for the reporter (user) and related users of the incident (see also Changing Visibility of Journal Entries). Journal entries for mails/comments from the user and mails to the user are checked by default. Under My Activities, you can enter your own activities for the ticket. Click Add to record the activity in the journal. Until the incident is not in the New or Closed status, opening of the ticket points directly to this tabulator.
  • Solution: Description of the solution that was entered when the incident was closed. When the incident gets the Closed status, opening of the ticket points directly to this tabulator. The solution cannot be directly edited.

Attachments

  • For this incident, copies of digital documents can be saved and later reopened.

Time Tracking

User Ratings

  • Shows user ratings with the following data: when this rating was submitted (Created), number of stars (Rating), Comment, and by which User it was created. If the Disable incident rating checkbox is selected in Global System Settings > Service Desk, this dialog page is hidden.

Related Objects

On the Related Objects dialog pages, you can manage all configuration items that are related to this incident.

  • Caused By: Here you can attach tickets that caused the respective incident. It is also possible to specify these tickets with the Close action.
  • Incidents: Similar incidents that can be put down to the same cause. If you select the Close related incidents when closing this incident checkbox, all incidents that are listed here will be closed when the status of this ticket is set to Closed.
  • Assets: Assets that were selected on the Reported CIs and/or Affected CIs tabs of the General dialog page and other additional assets that are affected by this ticket. For example, if a customer reports a computer incident and you know that other computers of the same model are affected, add these computers here. This data is purely informative and is not processed by the system.
  • Services: Services that were selected on the Reported CIs and/or Affected CIs tabs of the General dialog page and other additional services that are affected by this ticket. For example, if a customer reports a service incident, and you know that other services are affected, add these services here. This data is purely informative and is not processed by the system.
  • Users: Other users that are affected by the ticket. Select the Inform related users about status change to notify by email other users that are listed here about the status changes of this ticket.
  • Tasks: Create tasks and assign them to employees that are related to this ticket. If you select the Close this incident when the last task is closed checkbox, this ticket is closed when the status of the last task on the list is set to Closed. The solution is copied from the task to the ticket.

Actions

In the action pane, you can access the actions that are available for incidents.

  • Accept: A new ticket is always assigned to a role, not to a specific person. With this action, a role member says that they take over this ticket, which means that they accept responsibility for the ticket. The ticket status is set to Assigned. This informs other members of this role that somebody is already working on this ticket.
  • Return to Role: The Accept action is reset, the entry under Responsible is deleted, and the status set to Assigned. If the status was previously On Hold, then this is not changed.
  • Forward: Forward the ticket to a role or a user.
  • Edit: A new ticket is always assigned to a role, not to a specific person. With this action, a role member says that they take over this ticket, which means that they accept responsibility for the ticket. The ticket status is set to In Progress. This informs other members of this role that somebody is already working on this ticket.

If you select only one ticket on a search page and click Edit, the selected ticket will be opened directly for further handling, after the status is set to In Progress.

  • Pause: Set the ticket status to Paused by using a wizard. The reminder date is calculated automatically based on the value in the Default span for pausing tickets (days) field of the global system settings. If the ticket status does not change by the set date, a reminder email is automatically sent to the person who is responsible for the ticket. The reason and the description are saved in the journal.
  • Close: Finish the processing of the ticket is ended and set the status to Closed.
  • Merge Incidents: If two or more tickets have been created for a single incident, you can close or pause all duplicates. The journal entries and attachments of the merged tickets can be copied to the remaining incident. The incident then continues to run on one ticket. The customer is informed by email that the reported incident was merged into one ticket.
  • Reopen: Reopen the closed ticket, set its status to New, and notify the related persons by email.
  • Track Working Time: Start tracking the working time that was spent on this ticket.

If the Enable Automatic Time Tracking checkbox is selected under Administration > Global System Settings > Service Desk, the Track Working Time wizard opens automatically after you close the ticket. The start and end of the processing time are entered automatically. You can edit this data later. When you close several incidents, the spent time will be proportionally shared among the tickets.

  • Send E-mail: Send an email to any user, business contact, business partner, role or email address to request further information or to distribute any information about the incident. The User field of the incident will be pre-filled automatically as the "TO…" recipient.
  • Start Phone Call: The Matrix42 Call Tracker application should be installed on the local workplace before you can use this feature.
  • Assign Service: Assign a service from Matrix42 Service Catalog and specify the further handling of the incident. The order will be linked to the incident after the action is finished.
  • Unassign Service: Withdraw a previously assigned service from Matrix42 Service Catalog and specify the further handling of the incident. The order will be linked to the incident after the action is finished.
  • Repair Service: Repair or reinstall the previously assigned service from Matrix42 Service Catalog and specify the further handling of the incident. The order will be linked to the incident after the action is finished.
  • Reset Account: Open a wizard with the following options:
    • Unlock account.
    • Reset Password: Create a new password for the person who reported the incident.
    • Define additional parameters for passwords; specifically, whether a user should be asked to change their password after the first login, whether a user has permissions to change their password, and whether this password can expire.
  • Mobile Device Management: Open a wizard that gives you direct access to the Matrix42 Mobile Device Management system, so that you can execute the selected functions for the mobile device. For more information about these functions, see Managing Mobile Devices.
  • Establish Remote Connection: Establish a remote maintenance session with this computer by using Matrix42 Remote Control. For this purpose, Matrix42 Remote Control should be installed and correctly configured.
  • Recover Computer: Restore a selected computer completely or partition by partition from a backup image. For this option, Matrix42 EasyRecovery should be installed and activated on the computer.
  • Reinstall Computer: Reinstall the already installed software programs and the operating system on a computer. For this option, Matrix42 Empirum should be configured for the computer.
  • Show Dependencies: Show the defined dependencies in an interactive chart.
  • Search in Knowledge Base: Search for knowledge base articles that match this ticket.
  • Search Problems: Search for problems that match this ticket. If you open the search dialog within the context of a problem and this problem was linked with an asset or a service, the respective filters are pre-filled automatically. Based on the search result, you can link individual tickets with the problem.
  • Search Incidents: Search for incidents that match this ticket. If you open the search dialog within the context of an incident and this incident was linked with an asset or a service, the respective filters are pre-filled automatically. Based on the search result, you can link individual tickets with the incident.
  • Create Announcement: Create an announcement from the ticket. The information from the ticket is copied to the announcement. The ticket is retained and linked to the announcement.
  • Create Task: Create a task from the ticket. The information from the ticket is copied to the task. The ticket is retained and linked to the task.
  • Create Problem: Create a problem from the incident. The information from the incident is automatically copied to the problem. The incident is retained and linked to the problem. When the problem is closed, the related incident is closed, too.
  • Create Change: Create a change from this ticket. The information from the ticket is automatically copied to the change. The ticket is retained and linked to the change. When the change is closed, the ticket is closed, too.
  • Create KB Article: Create a knowledge base article from the ticket. The information from the ticket is automatically copied to the knowledge base article. The ticket is retained and linked to the knowledge base article.
  • Was this article helpful?