- 1 Overview
- 2 Creating an Incident
- 3 Managing incidents
- 3.1 List view
- 3.2 Form view
An incident is defined as a disruption or interruption to a service. The incident management area provides the tools and process to log, categorize, prioritize, and resolve the incident and restore the service.
Creating an Incident
End users who can login to the system can use "Need Help" menu the end-user portal to open an incident. This will present some basic questions to aid in the prioritizing and categorizing of the incident. These fields can be configured by a system administrator.
Technicians have the ability to create an incident from a list view by clicking the + action in the upper right hand corner of the list. This will display a new incident form which has a different view that a saved incident form.
A user managing the intake queue can convert an intake record into an incident record by clicking the Convert action on the intake record.
For more information on the intake record visit Intake
Users can email the Dreamtsoft system create and intake record that can be converted into an incident record.
External system and be setup to access the out of the box table APIs or a custom REST API can be created.
Clicking the book icon allows users to view an incident using a slide-in pane. This will also keep the context of the page they are on without navigating away.
Note for MSPs using SPACES: The book icon allows users to reside in the MSP space and view incidents from lower customer spaces without hopping down into the lower space.
Users can also click the link in the first column of the list to navigate away from the list and to the incident record.
There are several ways to create a filter and quickly get to the data you need. As you build you filter it will appear at the top of a list page
Smart filters are are commonly used filters found on most tables. Users have the ability to save their own smart filter under the Saved action.
For more advanced filters (OR and IF filters) users can click the filter build icon.
This provides users with an interface to build the desired filter for their data.
Clicking the magnifying glass at the top right of the columns will expose the column filter and allow users to quickly search for a value in a specific column.
Mousing over any value will expose the quick filter icons. Clicking the magnifying glass with the + will create a filter that includes that value, whereas clicking the magnifying glass with the - will exclude that value from your filter.
In order to clear a filter simply click the name of the table in the upper left corner of the list.
Space selector (1)
Displays what space the record is located.
Tags are free form text fields that can be used to label and organize incidents and other records.
Contains the fields with time relative values. Such as:
- When the incident was created
- The last time the incident was updated
- The last email received from the requester
- The last email sent to the requester
Time entries (4)
This tab contains a list of all time entries associated with this incident.
Activity log (5)
The activity log is the focal point of the incident form. It allows for sending and logging of communication between technicians and the requester.
For more information see Activity log
Activity filter (6)
The activity filter helps users quickly access comments that have been made on the incident.
For more information visit Comments
The details component contains the supplementary fields that assist in managing the incident. These fields are created to aid in logging, categorizing, and resolving the incident. Out of the box the incident form includes standard ITIL based fields but administrators have the ability to configure these fields as they see fit.
The relationship component displays any records that are connected to the incident. This includes:
When adding a relationship users will either be presented with a
- Type - Select the type of relationship
- List - Select the relating record from a list
- Search and select - Search for a record and then create the relationship
Simply put, actions are buttons users can click to initiate workflow. The standard actions on the incident are:
- Create problem - Creates a problem and and a relationship to the incident
- Convert to request - If the incident was incorrectly classified it can be converted to a request record.
- Copy - Creates and unsaved copy of the record
- Delete - Deletes the record