Creating, configuring and managing relations between issues is the key feature of STAGIL Assets - Advanced Links for Jira. Relations Advanced Links are connecting two custom fields and therefore two issues, which contain the connected fields. Connecting issues that way with Advanced Links offers you many possible use cases, which will be covered in the course of this documentation . As there are lots of possibilities, we will focus on the main ones, such as with a focus on CMDB, CRM and HR.
The main idea of all use cases is to show information with their relation(s) between each other, for example, linking devices like laptops, monitors and mobile phones to the belonging person (CMDB use case) or connecting contact data to an organization (CRM). Relations Advanced Links can be configured and shown in graphs/panels/tables. These topics are covered in the following sections.
| Table of Contents | ||||
|---|---|---|---|---|
|
...
How to create an Advanced Link
Go to the app administration and choose “RelationsAdvanced Links”. Click “Add RelationAdvanced Link” to create a new relation:
...
Now you have the following configuration options:
...
Link Color: Color of your relation if they are displayed in graphs.
Relation: Link type of your relation. Choose “Custom” to create a new link type (standard use case of STAGIL Assets!).
Relation Name: Name to identify your relationopen a create dialogue.
...
Advanced Link Name: a name to identify your Advanced Link.
From Type: field type of an outward issue link.
Outward Issue Link: Imagine imagine 2 issues A and B. The outward link is in the direction from A → B.
To Type: field type of an inward issue link.
Inward Issue Link: The the inward link is in the opposite direction from B → A.
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.
...
Link Color: the colour of your Advanced Link when they are displayed in Issue Graphs.
...
Set Screens
To make your relation work sure your Advanced Links are displayed you have to set associate them with the 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.
...
related fields.
...
Advanced Link Configuration
Until now your relation is not more than Advanced Link is just 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”Advanced Link”:
...
Data Logic
...
Fill in the Maximum Selection
...
Fill in field with the number of issues you should allow to select in this field. You can type 1 for a single selection or any positive integer for multiple selections. Type 0 if you want a multi-select field with an unlimited selection.
Use JQL for the Selectable Issues
...
Type JQL for field to set the scope of issue the user should see for selection.You can also define a Searching User here, to define other views. You could use this if you want to have a selection for a user over issues he/she normally cannot see because of View Permission / Issue Security. So user can select this issues, but can not see them, if they click on the linkissues available for selection or check the box below to restrict results to issues of the current project.
Defining the Searching User will allow selected users to browse issues they do not have permission for.
With Out-of-Scope Strategy you can define , what to do, if you have selected issues in some fields, that doesn't the behaviour if some field values do not fit the JQL anymore. You can choose between Keep between “Keep until it is actively removed by removed” by the user or Remove or “Remove on next update automaticallyupdate” automatically.
...
Display Style
By defining the display style you can configure the look of your relation fields Advanced Links in the issue view.
...
Panel: The position where your lookup panel should appear.
Display Style: table, list, table + pop-up, label + pop-up
...
| Expand | ||
|---|---|---|
| ||
The following field types are supported in the "Fields to show" section:
System fields:
|
Fields on Navigator: Fields that should be displayed in the issue navigator.
...
Show key in edit/create screen: If you mark this checkbox you can see the summary and additionally the key of the related issue you have selected in the edit and the create screen create a screen of your issue.
Example with key + summary (unchecking the option would only show “Start Enterprise”):
...
Show changes in issue history: If you select this checkbox the changes in an issue, like add or remove issue in relation to a 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 Advanced Links
To edit/create/delete relations Advanced Links you can use the overview page under app administration → STAGIL Assets → RelationsAdvanced Links:
...
| Warning |
|---|
If you delete a relationan Advanced Link, then the related custom fields are deleted, too! |
...