Relating items to the current ticket

From Related Items, you can relate an existing ticket or asset to the current ticket, or create a new ticket and relate it to the current ticket. For example, you can create a work order from within the context of an incident, and important metadata (such as customer information) from the incident copied to the new work order. In addition, "Created" and "Created by" relationships are automatically established between the two tickets.

From Related Items on a change request, you can create a new outage for one or more of the configuration items (CIs) that are related to the change request. You can also relate an existing outage to the change request. In this case, the CIs associated with the outage are automatically related to the change request.

To relate items to a ticket

1. In Related Items for the incident, work order, change request, or release requests add a related item.
2. Specify the related item type, such as Work Order, Incident, or Outage (for change requests).
   When you relate an existing outage to a change request, some filters are applied by default. For example, the system searches for scheduled outages for CIs related to the change request. If you want to search for other outages or for all outages, uncheck the default filters and add new filters as needed.

3. Specify search criteria and initiate the search.
   You must specify some search criteria, such as a company name, status value, or keyword. To search for all records, enter the % wildcard character.

4. Select related items and specify the relationship type.
5. Save.

To create a related item

1. In Related Items for the incident, work order, problem, known error, or change request, create a related ticket, such as a Related Incident or Related Work Order. (For a change request, you can also create a Related Outage.)
   A new ticket opens in draft mode with some information prepopulated from the original ticket. Outages created from change requests require specific information, as explained in "Specifying an outage for a CI" in People profiles in Smart IT.
2. Update the new item as needed and save it.
   Relationships between the items appear in Related Items. The original ticket has a "Created" relationship that links to the new item, and the new item has a "Created by" relationship that links to the original ticket.

Information copied to a related ticket

The following minimum information is copied to the related incident, problem, known error, work order, or change request:

• Customer and Customer Company
• Summary
• Notes
• Affected Service
• Priority

The following additional information is copied only to related work orders and incidents:

• Contact and Contact Company

• Categorization (including Product and Operational Categorization, Location Company)—Copied from a work order to a work order, and from an incident to an incident. 

To create a related knowledge article

In addition to creating related items, you can also create related knowledge articles. You can create related knowledge articles from incidents, work orders, problem investigations, and known errors. In the related article, important information is prepopulated in the article content and metadata.

1. Use one of the following methods to navigate to the option to create a related knowledge article.
   • On the Resources tab of the ticket, under Recommended Knowledge, click Search for knowledge resources and then click Create a new article. 
   • Open the ticket, and click the Related Items tab. Click +Create > Related Knowledge Article.
2. On the Create Knowledge page, select an article template.
3. After you preview the selected template, click Use selected Template.
4. Review the information that is prepopulated into the article, and add more content as required.
5. Click Submit Changes.

When the article is created, it is pinned to that ticket in the Resources tab under Recommended Knowledge. Note that the article is not listed in the Related items tab of the ticket.

Information copied to a related knowledge article

When you create a related knowledge article, the following information is copied from tickets to knowledge article:

The following default values are prepopulated in the knowledge article:

• Author: Logged in user (assuming correct permissions and functional roles)
• Language: Language of the logged in user