...
To add a new entry scroll to the bottom of the configuration page and click on the green Add button.
A new empty entry form is displayed:
| Field | Description | Example | |||||||
|---|---|---|---|---|---|---|---|---|---|
| Name of the relation | A human readable label that will be displayed on the tab in the issue view. This field is required. | High priority stories | |||||||
| Related issue match | A JQL query that controls the results displayed in the tab in the issue view. It supports templating described in the next subsection. | Show high priority stories:
| |||||||
| Only show for isssues that match the filter | A JQL query that allows you to show the tab only in the issues that match this query. You can leave it blank to show the tab for all the issues. |
Show only |
the tab for stories |
Only show for isssues that match the filter is a JQL query that allows you to show the tab only in the issues that match this query. You can leave it blank to show the tab for all the issues.
...
|
Simple query templating
You can use values from the currently displayed issue to create more dynamic and context aware queries.
Templated keywords or JSON path expressions need to be within double quotes and a curly bracket. For example:
| Code Block | ||||
|---|---|---|---|---|
| ||||
"{assignee}" |
The following query matches stories that are assigned to the same person as the current issue:
| Code Block | ||||
|---|---|---|---|---|
| ||||
type=Story and assigne="{assignee}" |
Supported keywords:
- assignee
- reporter
...
You can also use expressions that will be executed as a JSON Path expression to access all the data returned by issue REST endpoint: https://YOUR_JIRA_URL/rest/api/2/issue/ISSUE_KEY.
Most of the data in the issue JSON is in the fields field where you can access project id and labels:
| Code Block | ||||
|---|---|---|---|---|
| ||||
project="{fields.project.id}" and labels in ("{fields.labels}") |
You can match the ids of all the fix versions:
| Code Block | ||||
|---|---|---|---|---|
| ||||
fixVersion in ("{fields.fixVersions[*].id}") |
The simplest way to create you own advanced JSON path queries is to paste the issue JSON to JSON Path online Evaluator. If the value returned by the JSON Path is a single element array that element will substitute the template. If there are more values or the arrays are nested then all the elements will be put together and separated by a comma.
...
Restricting access to the configuration page
JQL JQL Search Extensions Related issues settings global permission controls the access to the configuration page.
...