...
| Field | Description | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| HistoryEntriesCount | Returns the number of changes made. | ||||||||
| Author | Returns the user who made the change. | ||||||||
| Created | Date of the change | ||||||||
| ChangedItemsCout | Returns the number of fields changed in the current change. | ||||||||
| ChangedItem |
|
| Code Block | ||||
|---|---|---|---|---|
| ||||
#{for 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 <VariableName>=HistoryEntriesCount}
Content and Issue History Mappings. Example:${fullname:HistoryEntries[VariableName].Field}
#{end} |
...
| Field | 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 |
...
The documents below demonstrate examples both in Word and Excel templates that iterates over the issue status transitions.
Iterating_Issue_StatusTransitions.xlsx
Iterating Issue Attached Images
Because it is not known in advance how many Images can exist for an issue (as an attachment), you can iterate a section over all the attached images of an issue to get some metadata about them. This allows you to create a table that dynamically grows according to the number of existing images. The notation is:
...