Use the Problem Management features to investigate problems and objects related to them. Establish hierarchical and functional relationships with Incidents and Change Requests to identify the issue cause.
Role required: problem_manager. |
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 a 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 a new Time Card with the steps below:
Users can add their Time Cards right from the problem form with the steps below:
Field | Description |
---|---|
Number | Automatically filled with the unique identifier 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 the user spent on resolving the problem. It is necessary for proper calculating the employee's working time. |
Related Task | Automatically filled with the issue from where the Time Card has been created. |
Comment | Add additional information if it is needed. |
Date | Determine the date when a user worked on the problem. It is automatically filled with the current date. |
Time Spent, hours | Specify the duration of the user's time spent in hours. |
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:
When investigating the issue, in case of detection change requests that caused the problem, register these relationships with the following features: