Analyze a problem
Start a problem's analysis and record the root cause and the workaround in the record as you find them.
On this page
Analyzing a problem means investigating why the failure happens. While you do, the problem record stores what you learn: the root cause, when you find it, and a workaround so the desk can keep helping the affected people.
Before you start
You need Operate in Problems and a desk role other than Viewer.
The problem must be Assigned, that is, have a resolver group. If it's New, assign it a group first (see Record a problem).
The problem record
Open the problem from Problems, by clicking its number or title. The record has:
Top: the title, number and status; the buttons to change the status and Conversation and SLA, which opens the general ticket record with the conversation, attachments and deadlines.
Description: what was written when it was created. It's the symptom, what the affected people see. If it came by email or from another system, it has the External text label.
Analysis: the Root cause and Workaround fields, and the It's a known error (the desk already knows how to work around it) checkbox.
Linked incidents: the incidents that share this cause (see Link incidents to a problem).
Side panel: Status, Priority, Group, Assignee, Service, how many Incidents it has, Created (the creation date) and, if already resolved, the Resolution. Below it, the Known error article section.
Start the analysis
With the problem Assigned, press Start analysis at the top.
The status changes to In analysis.
From In analysis, the Mark as known error, Resolve and Cancel problem buttons appear.
Record the root cause and the workaround
In the Analysis section, write in the relevant fields:
Root cause: why it happens. Required to resolve the problem.
Workaround: how to keep working until there's a permanent fix. Required to mark it as a known error.
Press Save. You'll see the message Problem saved.
Each field allows up to 20,000 characters. Save only turns on when there's something new; if you change your mind before saving, press Discard and you go back to the last saved version.
Don't wait to have the root cause before writing the workaround. As soon as the desk knows how to work around the failure, record it: it's what helps most the people handling incidents in the meantime.
You can fill in these fields over several passes as long as the problem isn't in a final state. If you press a status button with unsaved changes, Elion ITSM saves them first.
If someone else edits at the same time
The record updates on its own when someone changes the problem. If you had unsaved text, Elion ITSM doesn't overwrite it: the message Someone else changed this problem while you were typing. appears with the See the latest (discards yours) button.
If you press See the latest (discards yours), the other person's version loads and what you had written is lost.
If what you wrote is important, copy it first, press the button and paste it back where it belongs.
If you try to save after someone else saved, you'll see Someone else saved first: review the latest before saving again. and the same message.