...
Code Block | ||||
---|---|---|---|---|
| ||||
&{for issues|filter=%{'${IssueTypeName}'.equals('Sub-task')}} ${Parent.Key} ${Parent.Summary} ${Parent.Description} ${wiki:Parent.Description} ${html:Parent.Description} ${dateformat(“dd-MM-yyyy HH:mm:ss”):Parent.date} ${emailaddress:Parent.userpicker} &{end} This example only has a few fields, but this new feature allows you to get all information from a parent issue. |
Iterating Issues In Epic
All fields listed here are available on IssuesInEpic[n] because they represent an issue.
Because it is not known in advance how many issues exist for an epic, you can iterate a section over all the issues of an epic issue. This allows you to create a table that dynamically grows according to the number of existing issues. The notation is:
Code Block | ||||
---|---|---|---|---|
| ||||
#{for IssuesInEpic}
${IssuesInEpic[n].Key}
${IssuesInEpic[n].Summary}
${IssuesInEpic[n].Description}
${IssuesInEpic[n].Epic Link.Key}
#{end}
or
#{for <VariableName>=IssuesInEpicCount}
Content and Issue Mappings. Example: ${IssuesInEpic[VariableName].Field}
#{end} |
Sorting iterations
Imagine that you have an iteration and want to sort it by any field that it can export normally. This will be the header for such an iteration:
...