Page History
...
Because it is not known in advance how many linked issues exist for an issue, you can iterate a section over all the linked issues of an issue. This allows you to create a table that dynamically grows according to the number of existing linked issues. The notation is:
| Links Fields | Description |
|---|---|
| AppType | The application type of the link |
| LinkType | The type of the link |
| Key | The key of the linked issue |
| Summary | The summary of the linked issue |
| URL | The URL of the link |
| Code Block | ||||
|---|---|---|---|---|
| ||||
#{for links}
${Links[n].AppType}
${Links[n].LinkType}
${Links[n].Key}
${Links[n].Summary}
${Links[n].URL}
#{end}
or
#{for <VariableName>=LinksCount}
Content and Linked Issue Mappings. Example: ${Links[VariableName].Field}
#{end} |
All fields listed here are available on Links[n] because they represent an issue. In addition, there are two new fields at the Links[n] level:
...
Returns the Application Type. The values can be:
| Application Value | Description |
|---|---|
JIRA | Link from the same Jira Instance |
| External Jira | Link from the another Jira Instance |
| Confluence | Link from a Confluence page |
| External | External link |
...
The documents below demonstrate examples both in Word and Excel template that iterates over all the issue comments.
...