Table of Contents |
---|
Iterating
...
Status | ||||
---|---|---|---|---|
|
Changes to issues are registered in the Issue Activity, but it is not known in advance how many changes are going to be made. You can iterate a section over all the activities of an issue. This allows you to create a table that dynamically grows according to the number of existing activities. The notation is:
...
The title of the issue
...
Code Block | ||||
---|---|---|---|---|
| ||||
#{for activityEntries}
${ActivityEntries[n].Title}
${ActivityEntries[n].Summary}
${ActivityEntries[n].Content}
${ActivityEntries[n].Author}
${ActivityEntries[n].AuthorEmail}
${dateformat("dd-MM-yyyy HH:mm:ss"):ActivityEntries[n].Published}
${dateformat("dd-MM-yyyy HH:mm:ss"):ActivityEntries[n].Updated}
${ActivityEntries[n].Categories}
#{end}
or
#{for <VariableName>=ActivityEntriesCount}
Content and Issue Mappings. Example: ${ActivityEntries[VariableName].Field}
#{end} |
The documents below demonstrate examples both in Word and Excel template that iterates over linked issues.
Iterating Issue Links
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.
...