...
Code Block | ||||
---|---|---|---|---|
| ||||
#{for n=historyEntries} ${fullname:HistoryEntries[n].Author} made changes ${dateformat("dd-MM-yyyy HH:mm:ss"):HistoryEntries[n].Created} #{for ch=HistoryEntries[n].ChangedItemsCount} Field Name: ${HistoryEntries[n].ChangedItems[ch].Field} Old Value: ${HistoryEntries[n].ChangedItems[ch].From} New Value: ${HistoryEntries[n].ChangedItems[ch].To} #{end} #{end} or #{for h<VariableName>=HistoryEntriesCount} ${fullname:HistoryEntries[h].Author} made changes ${dateformat("dd-MM-yyyy HH:mm:ss"):HistoryEntries[h].Created} #{for ch=HistoryEntries[h].ChangedItemsCount} Field Name: ${HistoryEntries[h].ChangedItems[ch].Field} Old Value: ${HistoryEntries[h].ChangedItems[ch].From} New Value: ${HistoryEntries[h].ChangedItems[ch].To} #{end} #{end}Content and Issue History Mappings. Example:${fullname:HistoryEntries[VariableName].Author} #{end} |
Below is an example of using the Issue History iteration in a Word template:
or
Below is an example of using the Issue History iteration in an Excel template:
or
Iterating Issue Activity
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:
...
Code Block | ||||
---|---|---|---|---|
| ||||
&{for issues|filter=%{'${IssueTypeName}'.equals('Sub-task')}} ${Parent.Key} ${Parent.Summary} ${Parent.Description} ${wiki:Parent.Description} ${html:Parent.Description} ${dateformat(“dd-MM-yyyy HH:mm:ss”):Parent.date} ${emailaddress:Parent.userpicker} &{end} This example only has a few fields, but this new feature allows you to get all information from a parent issue. |
Iterating Issues In Epic
All fields listed here are available on IssuesInEpic[n] because they represent an issue.
Because it is not known in advance how many issues exist for an epic, you can iterate a section over all the issues of an epic issue. This allows you to create a table that dynamically grows according to the number of existing issues. The notation is:
Code Block | ||||
---|---|---|---|---|
| ||||
#{for IssuesInEpic} ${IssuesInEpic[n].Key} ${IssuesInEpic[n].Summary} ${IssuesInEpic[n].Description} ${IssuesInEpic[n].Epic Link.Key} #{end} or #{for <VariableName>=IssuesInEpicCount} Content and Issue Mappings. Example: ${IssuesInEpic[VariableName].Field} #{end} |
...