...
| Info |
|---|
In order to provide this functionality, the Xporter for JIRA plugin supports a special notation. That This notation allows defining which sections of the template will be populated for each issue, and which sections will be static. For further information please check our documentation here. |
...
You can even push this functionality to another level of control by applying filters to the iterationsiteration. This can be useful if you want to place the issues of a specific type (ex: Bug) in a section of the template and the issues of another type (ex: Story) in another section.
The notation we'll use in that instance is demonstrated below:
The following section will list the issues of the type Bug. &{for issues|filter=%{'${IssueTypeName}'.equals('Bug')}} Issue Key: ${Key} Issue Summary: ${Summary} &{end} The following section will list the issues of the type Story. &{for issues|filter=%{'${IssueTypeName}'.equals('Story')}} Issue Key: ${Key} Issue Summary: ${Summary} &{end}
This is the footer of the Bulk Export, this section will be rendered a single time. |
| Info |
|---|
Using a XLSX template however, When using XLSX templates please take note that to define an iteration for multiple columns, you need to merge a row of columns and define the &{for issues...} inside that merged cells. The same thing should be made to define the &{end} of the same iteration. All content between the &{for issues...} definition and the &{end} won't be duplicated for each iteration. For further information please check our documentation here. |
...
| Info |
|---|
If you like this exercise, please share your opinion on the page just leaving a comment or a |
...