DocumentaciónHelp

Problems and changes

Investigate the cause of recurring incidents and plan infrastructure changes with their CAB approval, in IT help desks (MDA).

On this page

An incident is closed when the person can get back to work. But if the same failure shows up again and again, someone has to find out why it happens and fix it at the root. That's a problem. And when the fix (or any other modification) touches services in production, it's planned, approved and carried out as a change. Elion ITSM follows the ITIL model for both.

Only in IT help desks (MDA)

Problems and changes exist only in desks created with the IT help desk (MDA) template. When you open one of them, four views appear under its name in the side menu:

View

What it's for

Tickets

Day-to-day incidents and requests (see Service desks).

Problems

Root cause investigation and known errors.

Changes

Changes with their type, risk, plans, window and CAB approval.

Calendar

The month's planned changes and the ones that clash with each other.

ESM and CSM desks don't have these views.

What a problem is

A problem gathers the incidents that share the same cause and stores what the team learns along the way:

  • the root cause: why it happens;

  • the workaround: how to keep working until there's a permanent fix;

  • the linked incidents: each time the failure shows up again.

When the desk already knows how to work around the failure, the problem becomes a known error and its workaround can be published as an article in Knowledge, so the rest of the desk and the portal can find it.

Nuevo ──► Asignado ──► En análisis ──► Error conocido
                            │                │
                            └──► Resuelto ◄──┘
                                    │
                                    ▼
                                 Cerrado

Cualquier estado no final ──► Cancelado

(New → Assigned → In analysis → Known error; In analysis or Known error → Resolved → Closed. Any non-final state → Cancelled.)

What a change is

A change is a planned modification: update a firmware, move a server, release a version. Before doing it, you write what will be done, how to test it, how to undo it and in what time window. Depending on its type, it's approved by the CAB (change advisory board).

Type

When to use it

Approval

Standard

Pre-approved: low-risk and repeatable.

Doesn't go through the CAB.

Normal

Most changes.

Goes through the CAB before being scheduled.

Emergency

Urgent: can't wait for the usual meeting.

Approved by the emergency CAB.

Borrador ──► En evaluación ──► Esperando al CAB ──► Programado ──► En implementación ──► En revisión ──► Cerrado
                  │                   │
                  │                   └──► Rechazado
                  └── (Estándar) ──────────► Programado

Cualquier estado no final ──► Cancelado

(Draft → In assessment → Awaiting CAB → Scheduled → Implementing → In review → Closed; Awaiting CAB → Rejected; Standard: In assessment → Scheduled. Any non-final state → Cancelled.)

How they relate to everything else

  • Incidents: incidents that repeat the same failure are linked to the problem. That way you see how many times it happened and measure the real impact.

  • Knowledge: a known error generates a draft article with the symptom, the workaround and the root cause (see Known errors).

  • Workflows and My tasks: CAB approval is a workflow. CAB members approve or reject from My tasks (see Workflows and tasks).

  • Agile releases: if an agile board requires an approved change to go to production, releasing a version creates a change in the MDA desk, and the release goes out when the CAB approves it (see Release a version).

What you can do depending on your access

  • To see problems you need at least View in the Problems module; for changes, View in Changes.

  • To create, edit and change states you need Operate in that module. The built-in Agent role already has it in both.

  • Your desk role also counts: if you're a Viewer, you see everything but the buttons to create and edit don't appear.

  • A problem or change in a final state (Closed, Cancelled or, for changes, Rejected) is read-only for everyone.

Pages in this section

Problems

Changes

The conversation, attachments and SLA of a problem or change stay in the general ticket record. From the problem or change record you get there with Conversation and SLA or Conversation.

Search Elion ITSM

Type at least 2 characters to search Elion ITSM.

↑↓ to navigate · Enter to open · Esc to close