Nested vLinks Fields example
You can create vLinks fields where the Issues are related to the details already entered in a issue. This example shows three vLinks fields which are related to each other. Based on Werk you can select other values.
| Multimedia | ||
|---|---|---|
|
The JQL for that is:
| Code Block |
|---|
issuetype = Standort AND Werk = customFieldValueFromIssue(currentIssue(), 10200) |
Issue Link Type
Issues link type defines the way issues will be linked by the field. This describes the relationship between the issues and what information is displayed on linked issues even without the linking field.
Relates to
| Section | |||||||
|---|---|---|---|---|---|---|---|
|
| Section | |||||||
|---|---|---|---|---|---|---|---|
|
JQL Filter
A JQL filter provides a powerful sorting possibility. Only issues matching the JQL filter will be displayed in the vLinks field. Existing Jira filter options can be used for this field. To ensure the JQL filter is built correctly, users have a green or red check mark that shows if the field is valid or not. Here are some examples and descriptions of their purposes.
| Section | |||||||
|---|---|---|---|---|---|---|---|
|
| Section | |||||||
|---|---|---|---|---|---|---|---|
|
| Section | |||||||
|---|---|---|---|---|---|---|---|
|
| Section | |||||||
|---|---|---|---|---|---|---|---|
|
View Template
The view template defines what a user will see next to the linked issues key. The issue key is always displayed. It is built from the project key that it belongs to and the issue number. This key means that each issue is unique and can't be confused with other issues. Here are some examples of different template keys and the way they are displayed.
View Template: $assignee
| Section | |||||||
|---|---|---|---|---|---|---|---|
|
View Template: $summary
| Section | |||||||
|---|---|---|---|---|---|---|---|
|
View Template: $reporter
| Section | |||||||
|---|---|---|---|---|---|---|---|
|
