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 21 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 “Advanced Link”. Here you can see all relations already created. Click “Add Advanced Link” 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(s).

Outward Field: field title in an outward issue.

To Type: inward issue type(s).

Inward Field: field title in 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 whether your Advanced Link is searchable.

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

At this stage, an Advanced Link is simply an empty structure. We will fill it with data in the next step. Click on “Edit Advanced Link Filed” to proceed with the configuration:

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

Maximum Selection: number of issues that can be linked to the Advanced Link field.

Selectable Issues: issue types that can be selected in the field. Insert valid JQL.

Searching User: user, who runs the query from the step above. Can be used to apply further restrictions based on the user's view permissions.

Out-of-Scope Strategy: strategy on selected issues that do not fit the defined JQL anymore.

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 Advanced Links in the issue view:

Panel: select where to display the Advanced Link table in the issue view.

Display Style: select panel view: table or list.

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

Fields to show: select the fields that should be displayed in the table.

Fields to sum up: sums up the number fields if table view is configured.

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

Add new: if the table view is selected, you can allow users to create new assets directly in the table from 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 Advanced Link field available in Jira Service Management as well you can define projects and issue types in this menu.

Projects: the list of JSM projects included in the Advanced Link field context.

Request Types: the list of request types that are mapped to an issue type part of the Advanced Link 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: Advanced Link upon which you want to base the dynamic behaviour.

Link types: link types that should be shown.

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

The Advanced Link panel appears on the issue view screen when the related project and issue type is configured in at least one Asset custom field.

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

On the top right section of the Advanced Link page, you will find the button “Migrate Links”, which allows you to convert regular issue links to Advanced Links, 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 Advanced Link tab of the same screen, you can turn Advanced Links into native Jira links:

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

  • No labels