| Table of Contents |
|---|
Nested vLinks Fields example
| Multimedia | ||
|---|---|---|
|
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. 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
Is blocked by
JQL Filter
JQL filter provide a powerful sorting possibility. Only issues matching the JQL filter will be displayed in the vLinks field. Already known filter options given by Jira can be used for this field. To make sure the JQL filter is built correctly, user have a green or red check mark that shows if the field is valid or not. Here are some examples and a descriptions on there purposes.
Only issues with issue type milestone can be linked to this issue
Only issues with issue type task and the admin as assignee can be linked to this issue
Only issues created before or after the current month can be linked to the issue
Only issues from a specific project and with a different issue type than "IT Help" can be linked to the issue
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 build from the project key that it belongs to and the issue number. With this key every issues becomes individual and no issues can be messed up. Here are some examples for different template keys and the way there are displayed.
View Template: $assignee
The assignee is displayed next to the linked issue key
View Template: $summary
The summary is displayed next to the linked issue key
View Template: $reporter
The reporter is displayed next to the linked issue key
