investigation and analysis of a problem
An unresolved problem can cause different system malfunctions that users register as incidents.
To create new caused incidents directly from the problem form, follow the steps below:
The filter condition of the Related Lists tab defines the current problem as an incident parent.
You can also assign a problem as parent to registered Incidents with the steps below:
When logging the problem, it is important to assess the time spent by users on resolving it.
To register the time you spent on a particular problem, create new Time Card with the steps below:
Users can add Time Cards on their own right from the problem form.
Field | Description |
---|---|
Number | Automatically filled with the unique identificator of the TMCXXXXXXX format. |
Employee | Automatically filled with the user's name. |
Company | Automatically filled with the users' company name. |
Time Spent Category | Specifies the time category that user spent on resolving the problem. It is necessary when analysing working time and schedules. (?) |
Related Task | Automatically filled with the issue from where the Time Card has been created. |
Comment | Add an additional information if it is needed. |
Date | Determine the date when a user worked on the problem. Automatically filled with the current date. |
Time Spent, hours | Specify the duration of user's time spent. |
To Invoice | Turn this checkbox active to mark the need for billing. |
When investigating the issue, in case of detection relations or dependencies with other problems register these relationships with the following features:
The system records every change on the Problem record with the Activities available on the Notes tab of the related information area. These activities collect all information about record changes, such as date, time, changed field and its previous value, and a user's name who apllied these changes.
A good practice is to record an additional information when working on the problem. Users can make notes and comments with
All saved notes and comments are available as Activities on the Notes tab and have colored marks:
Assign users with the Watcher List to monitor the problem processing and receive notifications sent by email.
The incident tracking process allows the caller to be informed about the work progress.
In SimpleOne, this process is implemented as "notifications" sent by email. For now, there are four types of notifications:
This type of notification is sent when the assigned person or end-user added any comment to the Additional Comments field.
All notifications are sent out to the email that is a contact for a person specified in the Caller field.
You can create new notification rules, or modify existing ones. To create a new notification rule, please refer to the Notifications article.