Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 20 Next »

The main configuration of a relation is the creation of one or two relation fields called Inward or Outward field. It reflects the start and end point of a relation. But before you create the relation fields, you first have to create the relation itself:

To create a new Advanced Link, please navigate to the app administration and choose “Relations”. Here you can see all relations already created. Click “Add Relation” to create a new relation:

Next the following dialogue emerges:

Advanced Link Name: a name to identify your Advanced Link.

From Type: outward issue type.

Outward Field: field title of an outward issue.

To Type: inward issue type.

Inward Field: field title of an outward issue.

Color: the color of your Advanced Link when they are displayed in Issue Graphs.

Show in Graph: check the box to show your Advanced Link in graphs (checked by default).

You want to connect applications with databases. Your Advanced Link name is “Application - Database”. So you have the outward field named “Application Database” which will link the application with databases connected to it. Vice versa you have the inward field named “Database used by” which will link the database with applications.

Set Advanced Link Field Contexts

To make your Advanced Link work you have to define in which contexts your fields should appear. Going back to our example this means that we have to place our field “Application Database” in the screen(s) for the issue type “Application” and the field “Database used by” for the issue type “Database”. This way we link two issue types by linking two custom fields.

Unactived/activated indicates if your relation is searchable.

Click on the field you want to edit. Now you can add/delete or edit the relation field context:

Until now your relation is not more than an empty structure. We will fill it with data in the next step. Click on “Edit STAGIL Assets Relation” to proceed with the configuration:

Under the Data Logic tab you can define the scope of your relation:

Maximum Selection: Defines, how many issues can be linked to the relation field.

Selectable Issues: Defines, what kind of issues you can select in the relation field. Insert valid JQL.

Searching User: User, who is used to run the query from the step above. Can be used to apply further restrictions based on the users view permissions.

Out-of-Scope Strategy: Defines the strategy to keep or remove relations.

In the “selectable issues” field you can use the {reporter} and {assignee} placeholder as well.

Under the Display Style tab you can define the appearance of the issue panels that display relations in the issue view:

Panel: Relations (Left) / Relations (Right). Select if you want to display the relation table at the left or right side of your issue. Select “Hidden” if you want to hide the relation field from the issue view screen.

Display Style: Table / List / Table + pop-up.

Rows per page: Select the max. amount of rows per page (rest will be shown with pagination).

Fields to show: Select the fields that should be displayed in the panel.

Issue Progress Bar: Sums up the progress of linked issues in panel based on status and visualizes it in a progress bar.

Add new: When you choose the display style "Table", you can allow users to create new assets directly at the table in the issue view. To enable this feature, please choose the project and the issue type that should be pre-selected in the create new issue screen that will appear after the user clicks on the small plus icon above the table.

In case you want to make your relation field available in Jira Service Management as well you can define projects and issuetypes in this menu.

Projects: Shows the list of JSM projects included in the relation field context.

Request Types: Shows the list of request types that are mapped to an issue type part of the relation context.

In this tab, you can apply a filter on the configured amount of assets you chose in the Data Logic tab based on a selected parent field. So it is possible to have a different list of assets for selection in issues, depending on the selected asset relation:

Parent field: Select the asset relation upon which you want to base the dynamic behavior.

Link types: Choose what link types should be shown.

Link level: Define the levels of links that should be displayed.

The Relations panel appears on the issue view screen when the related project and issue type is configured in at least one Asset custom field (Relation or Lookup).

Click on the button below to be redirected to the Relations panel on the issue view screen.

On the top right section of the Relations page, you will find the button “Migrate Links”, which will allow you to convert regular issue links to advanced issue relations, and vice versa:

By clicking on “Migrate Links”, a pop up screen will appear asking you to select by JQL the issues within which you want to migrate the links and to map the source link with the corresponding relations:

In the Relation tab of the same screen, you can migrate advanced issue relations to native Jira links:

(info) Issues that current user cannot see/edit/link will be ignored.

  • No labels