Links Between Requests
The following link types are defined in the basic database:
|
Source Request
|
Link Meaning |
|
Related
|
Generic link type.
This link type has no functionality. |
|
Parent – Child
|
The meaning corresponds to the links between the project tasks. A parent request consists of child requests.
Parent requests cannot be closed if they include open child requests.
Note: Sub-requests from version 6.0 will be converted to this link type during the system upgrade. |
|
Previous – Next |
The meaning corresponds to the order of creating requests in corporate processes. The request was created based on a different request.
It documents the request origin and solving process. |
|
Blocking – Blocked |
The meaning corresponds to the links between the project tasks. The blocked request depends on the blocking request. Blocked requests can be solved or finished only after the blocking request has been finished. |
|
Duplicated – Duplicate |
Duplicate requests are identical to duplicated requests. |
You can create custom link types that are written to the database table TicketRelationType. Predefined link types cannot be edited.
Tip: If you want to create new link types, select the link beginning and end to allow new links to be created from original requests in most cases. When creating a new link, you will be offered the end names of all types first and the initial names second.
Related
 Example: Two change requests concern one and the same CI. The relation of these requests is as follows.
Previous – Next
 Example: Previous tasks must be completed before next tasks can be worked on.
Parent – Child
Example: The parent task consists of partial child tasks (decomposition).
Duplicated – Duplicate
Example: Two users submitted incidents concerning the same problem. The first incident will be Duplicated, the second Duplicate.
If the link is used for full duplicity, this will create trees with a depth of 2:
If the link is set up also for partial duplicity, this will create a more complex graph:
ITIL
We recommend using the following link types for relations between the records of individual ITIL processes:
 All links for "simple" ITIL should be recorded as "related".
If you want to implement ITIL more rigorously, we recommend using the following link types:
|
ITIL |
Link Type |
Note |
|
Incident – similar Incident (parent – child) |
duplicated – duplicate |
The first incident is marked as "duplicated". All other incidents relating to the same problem are duplicates.
|
|
Incident – Problem / Known Issue |
related |
The incident can be created for an existing problem. A problem can be created based on existing incidents. Therefore, using "previous – next" is not recommended.
|
|
Incident – Service Request |
previous – next |
The Service Request will be created based on an incident (SR is involved in an incident).
|
|
Incident – RFC (N:N) – RFC is triggered by an incident |
previous – next |
RFC is involved in an incident.
|
|
RFC – Incident (caused by) |
previous – next |
The incident was caused by a change made incorrectly.
|
|
Problem – RFC |
previous – next |
The problem is being solved through RFC.
|
Working With Links
You can use the Request Details page to add, edit and delete links. The Request Details page contains the Links tab with an overview of current links within the request. You can use this tab to process the links further. The number in the parentheses on this tab shows how many links there are in the current request.
If you want to work with existing links, you need to select the required links by selecting the appropriate checkboxes on the left.
The View parent/child requests command will open a new window with a tree of requests with the Parent/Child links where the current request is saved.
The Display in window command will open a window with a new list of requests. This window will only list requests from the Links tab.
Note: Starting with ALVAO 7.0, the "Parent – Child" relation has replaced the system of sub-requests known from ALVAO 6.0. When you upgrade from a legacy version, all sub-requests will be automatically converted to the "Parent – Child" relation.
Did not find what you were looking for? Ask our technical support team.
|