---
title: Relating Items to the Problem
slug: pink/relating-items-to-the-problem
description: Learn how to effectively link different types of information like releases, knowledge, and services to a problem using our step-by-step guide. This document provides detailed instructions on how to link incidents, configuration items, changes, services, r
docTags: 
createdAt: 2021-10-27T19:35:33.000Z
---

It is possible to <font color="#3b9f0f">**link to the Problem a series of information**</font>, such as release, knowledge, services related, and others.

## Before getting started

The information link can occur throughout the entire lifecycle of the Problem, this&#x20;way, it can - and should - be used at any time, if necessary.

- [x] However, it is  &#x20;necessary to have access to a Problem.

## Procedure

1. Access the main menu `Process >    Problem Management > Problem`;
2. To inform additional data, select the capture option   , or problem view;
3. To view the information about specific fields, click on the tabs:   &#x20;<font color="#3b9f0f">**Requester**</font>, <font color="#3b9f0f">**Incidents**</font>**,** and <font color="#3b9f0f">**Problem**</font>;

### <font color="#3b9f0f">Relate Incidents</font>

- To link **Incidents**, click on the area of the same name and then on the  &#x20;"**Add**" icon, being necessary searching and selecting the incident that will be linked. It will  &#x20;be also available the possibility of creating an incident and from this problem,  &#x20;when clicking on the "**Register**" icon and complete the data necessary.

:::hint{type="success"}
✅ <u>**Rule**</u>**:&#x20;**&#x57;hen linking or registering the incident and saving the problem, a notification will be triggered in the e-mail and on the screen of the current responsible for the incident. However, this notification will be only sent if the incident has already been captured by its executor, moreover, if it is not captured and designated to the responsible, **there will be no notification**. The notification sending mentioned above is automatic, without the need for parameterization.
:::

### <font color="#3b9f0f">Relate Configuration Items</font>

- To link **Configuration Items**, click on "**Related CI**" and then on "**Search  &#x20;Configuration Item**". Search and click on "**Select**" to complete the operation.  &#x20;Therefore, it is possible to click on the "**Services**" icon, link it to the same  &#x20;problem, and click on the icon "**Info**", it will be possible to view all information  &#x20;to the CI that is linked;

### <font color="#3b9f0f">Relate Change</font>

- To link **Change**, click on the "**SOLUTION**" phase, and in the "<font color="#3b9f0f">**Changes**</font>" tab, you  &#x20;can search for the Change number or even register a new Change. After the link  &#x20;you can edit the Change. In addition, you can observe the "**Configuration Items**"  &#x20;by clicking on the icon of the same name. To remove the link from the Service,  &#x20;just click on the "**Remove**" icon and confirm the operation;

### <font color="#3b9f0f">Relate Services</font>

- Clicking on the **"Related Services"** area, it will be presented the service  &#x20;related to the problem (if it has already been linked) with some  &#x20;available actions. The "**Service Map**" view is displayed by clicking on the  &#x20;icon of the same name, besides, it is possible to note the "**Configuration Items**"  &#x20;when clicking on the icon of the same name. Now, to remove the Service link, just  &#x20;click on the icon "**Remove**" and confirm the operation;

:::hint{type="info"}
💡 <u>**Tip**</u>**:&#x20;**&#x49;f there is any service-related, it is possible to link a new service to the problem, just click on the "**Related Services**" area and then on the "**Add Service**". Therefore, it is necessary to select the service you want and click on it.
:::

### <font color="#3b9f0f">Relate Release</font>

- To link **Release**, click on the area of the same name, then click on the  &#x20;search field and select the release you want. If you want to register a  &#x20;new release, click on "**Register**" and complete the data;

### <font color="#3b9f0f">Relate others Problems</font>

- To link other **Problems**, click on the area of the same name and then on  &#x20;the search field and select the problem you want. If you want to create  &#x20;a new problem to be related, to just click on "**Register**" and complete the  &#x20;necessary data;

### <font color="#3b9f0f">Relate Knowledge</font>

- To link a **Knowledge**, click on the area of the same name, then on the search  &#x20;field and select the knowledge you want. If you want to create new knowledge,  &#x20;click on "**Register**" and complete the necessary data.

### <font color="#3b9f0f">Save Changes</font>

- Click on "**Options**" and then on "**Save and advance flow**" or "**Save and keep current  &#x20;task**". This last option makes it possible to not advance to the next phase of the problem.

