...
Changes to issues are registered in the Issue History, but it is not known in advance how many changes are going to be made. You can iterate a section over all the history entries of an issue. This allows you to create a table that dynamically grows according to the number of changes denedone. The notation is:
| 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 |
|
...
If you want to take the previous iterations over comments, subtasks, and issue links to another level of control, you can use a JavaScript filter to define over which issues the iteration will be made. This can be useful in the following scenarios:
...