30 April 2018
The Xporter for JIRA team proudly announces the release of Xporter 5.5.0. This point release contains several new features and bug fixes.
Highlights for this release
Multi-Action workflow post function
This feature will allow you to define a workflow post function to generate a report and, at the same time, define how the result will be handled. Currently, if you want to generate a report and send it to a Confluence page or send it by email, you need to use two post functions (Send Report and Create Document Post Functions).
This new workflow post function enables you to define multiple actions, such as:
Attach file
Save locally
Send by email
Upload to a file server
Permission Scheme: a new way to map templates
Permission Schemes are sometimes complex and users need to spend a lot of time setting them up. A good example is how to configure the Issue Type ↔ Template mapping. If there are lots of issue types being used and you have to configure a template to be used by all defined Issue types, you need to add the template to each issue type configuration, one by one.
Xporter 5.5 brings a new level of configuration: Global Template mapping. This feature enables the administrator to define which template will be used globally for all issue types selected in the current permission scheme. This makes the template available for all selected Issue types.
Xporter Reports restriction using JIRA groups
In the previous version, Xporter Reports can either be enabled or disabled. Xporter 5.5 enables you to configure it by assigning Jira user groups. See the image.
New Attributes on image handling (width and height)
Until now, it only was possible to define the max size of images using the attributes maxWidth and maxHeight. With Xporter 5.5, it's now possible to define the exact size you want to print.
To resize an image, you just need to define the Width and/or Height attributes in ${Images} and ${Images[n].Image} mappings.
//Images fields
${Images|width=200}
//Images Iteration
#{for images}
${Images[n].Image|width=200}
#{end}
Wiki markup/HTML processing on Excel files got some improvements
Several customers have requested that we address the limitations regarding WIKI markup/HTML processing on Excel files. We are happy to announce that Xporter is now capable to handle more content such as wiki tables, bullet lists and others.
See the example of a wiki table printed on an Excel file.
CheckList integration - Get checked/unchecked values
CheckList integration now allows you to determine which options are checked or unchecked. It's now possible to iterate over all defined options and get the label and status of each. You can then create a table that dynamically grows according to the number of existing values. The notation is:
#{for FieldName}
${FieldName[n].Label}
${FieldName[n].Status}
#{end}
With this new feature, Xporter will allow you to have the same output as your Jira instance and the notation is very simple. See the example.
Key field is now processed as a hyperlink
Issue key field is now processed as a hyperlink on XLSX (Current Fields) export option. This makes it simple to open the browser directly from the report and see the complete information of an Issue.
Project Category
We introduced a new mapping that allows you to print the Project Category on documents.
${Project.Category}
JQL Issues processing must respect the limit of issues to be exported
Xporter allows you to define the maximum number of issues to be exported by Xporter. This was only validated on Bulk Export and not internally. To avoid performance issues on the Jira instance, we tightened the checking. If you define a JQL issues iteration where the number of issues returned is greater than the max number of issues defined in the global settings, a warning message will be printed on document.
The image presents an example of a result with the warning message.
