Page History
In this page, it's explained how to export a property when it has more than a single value such as:
| Table of Contents | ||||
|---|---|---|---|---|
|
The Document Generator also provide way to handle provides data by filtering nad and sorting data directly on the iteration definition. Read the following topics:
| Table of Contents | ||
|---|---|---|
|
Issue History
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 dene. The notation is:
...
The image below demonstrates an example of a Word template that iterates over linked issues.
or
For a working example of this functionality, check the SampleIterations.docx template in the Template Store.
The image below demonstrates an example of an Excel template that iterates over linked issues.
...
The image below demonstrates an example of a Word template that iterates over issue comments.
or
For a working example of this functionality, check the SampleIterations.docx template in the Template Store.
The image below demonstrates an example of an Excel template that iterates over issue comments.
or
| Info | ||
|---|---|---|
| ||
If you are using Jira Service Desk you can see more information about comments here. |
Issue Worklogs
Issue Worklogs
Because it is Because it is not known in advance how many worklogs exist for an issue, you can iterate a section over all the worklogs of an issue. This allow you to create a table that dynamically grows according to the number of existing worklogs. The notation is:
...
| Code Block | ||||
|---|---|---|---|---|
| ||||
#{for worklogs}
${Worklogs[n].Author}
${Worklogs[n].AuthorFullName}
${Worklogs[n].Comment}
${dateformat("dd-MM-yyyy HH:mm:ss"):Worklogs[n].Created}
${dateformat("dd-MM-yyyy HH:mm:ss"):Worklogs[n].Date Started}
${Worklogs[n].Time Spent}
${Worklogs[n].TimeSpentFormatted}
${Worklogs[n].BilledHours}
${Worklogs[n].BilledHoursFormatted}
#{end}
or
#{for <VariableName>=WorklogsCount}
Content and Worklog Mappings. Example: ${Worklogs[VariableName].Field}
#{end} |
The image below demonstrates an example of a Word template that iterates over issue worklogs.
or
For a working example of this functionality, check the SampleIterations.docx template in the Template Store.
The image below demonstrates an example of a template in Excel that iterates over issue work logs.
...
or
...
Field}
#{end} |
Issue Sub-Tasks
Because it is not known in advance how many subtasks exist for an issue, you can iterate a section over all the subtasks of an issue. This allows you to create a table that dynamically grows according to the number of existing subtasks. The notation is:
...
The image below demonstrates an example of a Word template that iterates over issue subtasks.
or
For a working example of this functionality, check the SampleIterations.docx template in the Template Store.
The image below demonstrates an example of an Excel template that iterates over issue subtasks.
...
For an example of how to iterate the details of a subtask Parent issue, please check the Iterating the Iterating JQL Queries area below.
Issue Components
...
The image below demonstrates an example of a Word template that iterates over attached images.
or
| Info |
|---|
Doc. Generartor Generator 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. |
...
The image below demonstrates an example of a Word template that iterates over issue subtasks.
...
The image below demonstrates an example of an Excel template that iterates over issue subtasks.
...
Links Bugs with High Priority:
Nested Iterations:
For a working example of this functionality, check the template Sample Iterations in the Template Store.
Iterating in the same line of the document
...