Page History
...
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:
| Activity Fields | Description |
|---|---|
| Title | The title of the issue |
| Summary | The summary of the activity |
| Content | When an activity involves a change in the Issue contents, this field displays the new contents |
| Author | The author of the activity |
| AuthorEmail | The email of the author of the activity |
| Published | The time the issue was published |
| Updated | The time the issue was updated |
| Categories | When an activity regards an Issue Status change, this field displays the new Issue Status |
| 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} |
| Info |
|---|
We suggest that you use the html function to render the data because almost all content is HTML, e.g., ${html:ActivityEntries[n].Title} |
Below is an example are two examples of using the Activity iteration in a Word and Excel template:
or
Below is an example of using the Activity iteration in an Excel template:
or
...
Iterating_Activity_Entries.docx
Iterating_Activity_Entries.xlsx
Issue History
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 done.
...