Page History
...
Table of Content Zone | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Issue HistoryChanges 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: History Entry
Issue LinksBecause it is not known in advance how many linked issues exist for an issue, you can iterate a section over all the linked issues of an issue. This allows you to create a table that dynamically grows according to the number of existing linked issues. The notation is:
All fields listed here are available on Links[n] because they represent an issue. In addition, there are two new fields at the Links[n] level:
Note: When the link you are iterating is of AppTypes External Jira or Confluence, the name is obtained using the Summary property. 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. or Issue CommentsBecause it is not known in advance how many comments exist for an issue, you can iterate a section over all the comments on an issue. This allows you to create a table that dynamically grows according to the number of existing comments. The notation is:
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
Issue WorklogsBecause 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:
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 Issue Sub-TasksBecause 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.
or For an example of how to iterate the details of a subtask Parent issue, please check the Iterating JQL Queries area below. Issue ComponentsBecause it is not known in advance how many components exist for an issue, you can iterate a section over all the components of an issue. This allows you to create a table that dynamically grows according to the number of existing components. The notation is:
The image below demonstrates an example of a Word template that iterates over issue components. The image below demonstrates an example of an Excel template that iterates over issue components.
Issue Status TransitionsBecause it is not known in advance how many Status Transitions exist for an issue, you can iterate a section over all the Status Transitions of an issue. This allows you to create a table that dynamically grows according to the number of existing status transitions. The notation is:
The image below demonstrates an example of a Word template that iterates over status transitions. or The image below demonstrates an example of an Excel template that iterates over status transitions. or Issue Attached ImagesBecause 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:
The image below demonstrates an example of a Word template that iterates over attached images.
or
These values are in pixels and if you only define one of them the image will be rescaled.
The image below demonstrates an example of an Excel template that iterates over attached images.
or Issue AttachmentsBecause it is not known in advance how many attachments exist in an issue, you can iterate a section over all the attachments of an issue. This allows you to create a table that dynamically grows according to the number of existing attachments. The notation is:
The image below demonstrates an example of a Word template that iterates over attachments. or The image below demonstrates an example of an Excel template that iterates over attachments. or Issue LabelsBecause it is not known in advance how many labels exist in an issue, you can iterate a section over all the labels of an issue. The notation is:
The image below demonstrates an example of a Word template that iterates over labels. or The image below demonstrates an example of an Excel template that iterates over labels. or Project VersionsYou can iterate over all project versions to which the issue belong to. The notation is:
The image below demonstrates an example of a Word template that iterates over project version. or The image below demonstrates an example of an Excel template that iterates over project version. or Iterating JQL QueriesYou can iterate issues that are the result of a JQL Query. The syntax is similar to the other iterations, but there is a clause parameter that will receive the JQL Query. A few examples are provided below.
The image below demonstrates an example of a Word template that iterates over issue subtasks. For a working example of this functionality, check the template Sample Iterations in the Template Store. The image below demonstrates an example of an Excel template that iterates over issue subtasks.
|
...
Table of Content Zone | ||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Applying filters to IterationsIf 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:
The notation for applying filters to the iterations is:
Notice that as the filter is evaluated as a JavaScript expression, which provides flexibility in the definition of the conditions. You can use and (&&), or (||) and other logical operators supported by the JavaScript language. It is also possible to format fields inside iteration filters. For more information on formatters, see Native Iterations. The image below demonstrates an example of a template that iterates over issue links and comments with filters being applied. 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 documentYou can also possible to iterate values in the same line of the document. This can be useful if you want to display a list of Subtasks on Linked Issues in the same line, separated by commas or spaces.
Iterating in the same cell in an Excel documentYou can also iterate values in the same cell in an Excel document. You can achieve this by simply making your Iteration inside the same cell. You can use all the Iterations that you are used to and construct them in the exact same way, the difference being that you only use one cell to do them.
Iterating with the BREAK or CONTINUE statementYou can iterate anything, set up a Conditional expression and then utilize the BREAK and CONTINUE statements. The way to do this is by doing a normal Conditional expression and using the mapping #{break} or #{continue} inside it.
|
#{for comments|sortby=<Iteration mapping>} |
NOTE: The mapping after the "sortby" must be equal to the supported mappings for each Iteration.
Example:
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.
Code Block | ||||
---|---|---|---|---|
| ||||
&{for issues|sortby=IssueTypeName} ${Key} - ${IssueTypeName} &{end} |
Info | ||
---|---|---|
| ||
asc and desc can be defined in order to define how do you want to sort your data. The default value is asc. |