| Info |
|---|
The currentIssue() placeholder can be used to reference a field value from the current issue. To reference a field, put it’s name or ID in the function argument:  This placeholder will be substituted in the edit mode of the field. Because the function doesn’t actually exist and Jira doesn’t know how to parse it, it won’t be possible to preview the number of issues found by it in the configuration (it will show 0). |
Below are a few examples of what can be done using JQL placeholders:
System field “reporter”
Only issues by the same reporter are shown.
System field “project”
Only issues from the same project as the current issue will be shown.
System field “labels”
Only issues where the labels match one of the labels in the current issue. Note the usage of extra brackets around the placeholder; value of labels is an array which requires the IN operator to be used and the value limited by brackets.
Single select custom field
Only issues having the same value of a custom field as the current one will be shown.
Reference other Linksy fields
It’s possible to reference other Linksy fields and create some sort of a cascading structure.
Combine multiple field values in a list
It’s possible to reference other Linksy fields and create some sort of a cascading structure.
| Info |
|---|
Fields that return an array need to be wrapped in round brackets and compared with the JQL operator IN; eg. (currentIssue(“labels“)) becomes (label1, label2) That is because Linksy will convert the array values to a comma-separated list but won’t add the brackets on its own. Currently, it’s not possible to reference a specific element in the field like currentIssue(“customfield_10101.data[0].name”) If you need this feature please let us know by suggesting it in our service desk portal. |
Create issue and transition screens
The currentIssue() placeholder
won’twill work in
the Create issue screen. To maintain usability of the field in the Create issue screen, there is now an optional setting in the Linksy field configuration to use a different JQL filter forthe “Global Issue Create” screen and the new issue transition experience.
However, not all fields can be supported; here is a list of all supported fields per screen (create or transition).
| Info |
|---|
In case the currentIssue() placeholder interferes with the ticket creation process, there is an option to enable an alternative JQL filter specifically to be used in the Create issue screen.  |
With dynamic JQL, it’s possible to use Linksy fields to create a cascading structure, where one Linksy field depends on one or more other Linksy fields:
