Xporter 5.5.0 Release Notes

Xporter is proud to announce the new Multi-action Workflow Post Function. This feature will allow you to define a workflow post function to generate a report and 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 e-mail, you need to use two post functions (Send Report and Create Document Post Functions). The great advantage the new workflow post function is the way how you are able to define multiple actions.

Permission Schemes are sometimes complex and users need to spend a lot of time setting up them up. A good example is the way how to configure the Issue Type ↔ Template mapping, if there are lots of issue types being used and we have to configure a template to be used on all defined Issues type, we need to add the template to each issue type configuration, one by one.

Xporter 5.5 brings a new level of configuration regarding to template mapping, the Global Template mapping. This feature turns the template configuration easier when the template is available for all selected Issues types. The global configuration means that the selected template will be available for all selected issues types on the current permission scheme. 

The administrator can define which template will be used globally (for all issue types selected in the current permission scheme). Nevertheless, setting up templates by issue types is also possible as it was before.

Xporter Reports can be now configured by assigning Jira user groups. In the previous version, Xporter Reports cloud just be enabled or disabled. Xporter 5.5 brings you the capability of configuring it per groups as you can see in the image below.

Resizing images is now possible using Xporter. Until now, it only was possible to define the max size by using the attribute maxWidthandmaxheight, but with Xporter 5.5 it's possible to define exactly the size you want to get printed.

To resize the image, you just need to define the Width and/or Height attributes in ${Images}  and ${Images[n].Image} mappings.

We have been receiving some feedback about the wiki markup/HTML processing on Excel files. We did some improvements to address these limitations and get better results on this.

Xporter is now capable to handle more content based on wiki markup and HTML, such as wiki table, bullet lists and more content.

Below there is an example of a wiki table printed on an Excel file.

CheckList integration got some improvements in order to allow users get which options are checked or uncheck. Now, it's possible to iterate over all option defined and get the label and the status of each option. This allows you to 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}

Issue key field is now processed as a hyperlink on XLSX(Current Fields) export option. This turns it simple to open the browser directly from the report and see the complete information of an Issue.

A new mapping was introduced in order to allow you getting the Project Category printed on documents.

As you know, Xporter allows users to define the maximum number of issues allowed to be exporter by Xporter. This was only validated on Bulk Export and not internally when processing JQL issues iterations where it was possible to use a JQL that returns a number of issues great than the maximum defined. To avoid performance issue on the Jira instance we did some improvement in order to avoid these possible situations. On Xporter 5.5, if you define an JQL issues iteration where the number of issues returned is great than the max number of issues defined on global settings, a warning message will be printed on the document.

Below there are examples of the result with the warning message, as we mentioned above.