Page History
...
| 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 h=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} |
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:
...
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} |
| 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} |
...
The image below demonstrates an example of a Word template that iterates over attached images.
or
| Info |
|---|
Xporter Doc. Generartor will automatically read the EXIF orientation property of an image and rotate it to its correct orientation. You can turn this off by adding this property to your template. |
...
of an image and rotate it to its correct orientation. You can turn this off by adding this property to your template. |
| Code Block | ||||
|---|---|---|---|---|
| ||||
#{for images}
${Images[n].Image|width=150|height=150}
#{end} |
...
The image below demonstrates an example of an Excel template that iterates over attached images.
or
...
...
You can iterate over ${Images[n].Image} in Excel on Xporter version 5.4.0 and above.
Iterating Issue Attachments
...
| Info |
|---|
You can also use a Filter Name or a Filter Id as a clause. For more info, check [http://confluence.xpand-addons.com/display/public/XPORTER/JQL] read this. |
Iterating Issue Commits
Because it is not known in advance how many commits exist for an issue, you can iterate a section over all the commits of an issue. This allows you to create a table that dynamically grows according to the number of existing commits. The notation is:
...
| Code Block | ||||
|---|---|---|---|---|
| ||||
Imagine that you have a Jira Issue that contains these comments:
- Hello
- World
- Greetings
- Hi
For the Break functionality, lets say that you want to stop the iteration if the current comment is "World". Here is the template for that:
#{for comments}
Current Comment: ${Comments[n].Body}
#{if (%{'${Comments[n].Body}'.equals('World')})}
#{break}
#{end}
Current Comment Author: ${Comments[n].Author}
#{end}
In this case, Xporter for Jirait will print the comment "Hello" and it´s author. Next it will print the comment Body "World" but since the Conditional expression is true, it will stop the iteration all together and not print anything else.
Note: Anything after the #{break} mapping will not be printed in the exported document.
For the Continue functionality, lets say that you want to skip to the next iteration if the current comment is "World", bypassing the Author mapping for this iteration. Here is the template for that:
#{for comments}
Current Comment: ${Comments[n].Body}
#{if (%{'${Comments[n].Body}'.equals('World')})}
#{continue}
#{end}
Current Comment Author: ${Comments[n].Author}
#{end}
In this case, Xporter forit Jira will print the comment "Hello" and it´s author. Next, it will print the comment Body "World" but since the Conditional expression is true, it will continue to the next iteration, not printing the Author of the "World" comment. |
...
| Code Block | ||||
|---|---|---|---|---|
| ||||
This iteration will be sorted by the Body of all the comments in the issue.
#{for comments|sortby=Body}
${Comments[n].Author}
${Comments[n].Body}
#{end} |
Sort By
...
on multi issue export
The sortby can also be used to sort a &{for issues} iteration on a Bulk Export.
...