...
| Table of Contents | ||||
|---|---|---|---|---|
|
Create a Relation
Go to the app administration and choose “Relations”. Click “Add Relation” to create a new relation:
...
Example Relation: You want to connect CIs with their costs. Your relation name is “CI - Cost”. So you have the outward link named “paid by” which will link the cost issues. Vice versa you have the inward link named “Payment for” which will link the costs with the CI.
...
Set Screens
To make your relation work you have to set screens for the relation fields you created in the first step. Going back to our example relation this means that we have to place our field “Paid by” in the screen(s) for the issue type “CI” and the field “Payment for” for the issue type “Cost”. This way we link two issue types by linking two custom fields.
...
Configure a Relation
Until now your relation is not more than an empty structure. We will fill it with data in the next step. Click on the inward/outward link names to proceed with the configuration:
...
Now choose “Edit STAGIL Assets Relation”:
...
Data Logic
...
Maximum Selection
Fill in the number of issues you should allow to select in this field. You can type 1 for single selection or any positive integer for multiple selections. Type 0 if you want a multi-select field with an unlimited selection.
Selectable Issues
Type JQL for the scope of issue the user should see for selection.
...
With Out-of-Scope Strategy you can define, what to do, if you have selected issues in some fields, that doesn't fit the JQL anymore. You can choose between Keep until it is actively removed by the user or Remove on next update automatically.
Display Style
By defining the display style you can configure the look of your relation fields in the issue view.
...
Show changes in issue history: If you select this checkbox the changes in an issue, like add or remove issue in relation custom field, will be shown in issue history.
Dynamic
In this tab you can select subsets of your configured amount of assets you chose in the Data Logic tab and assign it to issue types. So it is possible to have a different list of assets for selection in issues. Also you can make use of dynamic dependencies and define, which conditions have to be met, that your field appears in your masks. This is useful, if you only want to select assets if they match specific criteria.
| Note |
|---|
Please notice that the JQL in the dynamic tab is a subset of the amount in the Data Logic tab. Otherwise you will not get any matches. |
Dynamic Based on Current Issue
To create a subset of your assets, fill in Project, Issue Type and a JQL to define selectable issues. You can define more than one subset, so that the same field will show different subsets of assets in different contexts.
...
Dynamic Based on Relation
With relation based dynamics you can define conditions for your field to appear in a mask. Only if the conditions are true, your relation field will pop up in your masks. To set conditions and selectable issues, please fill in a Condition JQL and a JQL for Selectable Issues.
...
| Expand | ||
|---|---|---|
| ||
ExampleA user wants to send a request of a problem of one of the asset he owns via the Service Desk customer portal. When he creates a ticket, he has the possibility to select a building and a CMDB. The following example shows how to limit the option with dynamics to the building where the employee is stationed and the assets which belong to him.
 For the configuration, the following relations (Outward Field / Inward Field) need to be created which could be named like this:
Further, following relations are needed for the
  Starting with 1. The building where he is working, the special JQL function Issue in Relation is used as Data Logic to select the HR issue of the user and only the issues of the relations connected to it. With the restriction of type = building, only the value of "Job Site" can be selected now.  To configure 2. The assets which are assigned to him, the Data Logic needs to be based on all CMDB issue types except buildings.Now, the Dynamic is based on the relation ITSMSupport-Building(Building Affected) which the user selects first by creating the ticket. In this case, the Condition need to be issue type = building. The Selectable Issues are based on the issue selected before. The JQL goes into the relation which displays all CMDB of that specific building in the first level of the current user.  
|
Manage Relations
To edit/create/delete relations you can use the overview page under app administration → STAGIL Assets → Relations:
...