We are pleased to announce the upcoming release of Xporter v5.5, which brings several new features and improvements requested by our customers.
Highlights include:
- Multi-action workflow post function
- Permission Scheme: A new way to map templates
- New “Xporter Reports” restriction using Jira groups
- New attributes on image handling (width and height)
- Wiki markup/HTML processing on Excel files got some improvements
- CheckList integration: Get checked/unchecked values
- Key field is now processed as a hyperlink
- Project Category
- JQL Issues processing must respect the limit of issues to be exported
- General improvements and bug fixes
- Learn More
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
This action will attach the generated document to the issue that performed the transition.
Save locally
Once the file is created, it will be placed on the server where Jira is running.
Send by email
This action allows sending the generated report via email.
Upload to a file server
The generated file will be placed on the specified file server (e.g., FTP/S and SFTP Server or even a Confluence page). You will be able to create multiple actions of this type.
Furthermore, Xporter will give you an overview of the defined actions and you will have the option to edit or delete existing actions. The table will contain the action, a brief description and the filename of the report that will be generated.
You just need to select the template, output format and the provide the name of the attached report.
Xporter also supports the evaluation of JavaScript conditions to check if the workflow post function should be executed on that specific Jira workflow transition.
The other two workflow post functions are now deprecated and will be removed from the product on next major release (Xporter 6.0).
We highly recommend that you change your configuration and start using the new multi-action workflow post function.
Permission Scheme: A new way to map templates
Permission Schemes are sometimes complex and users need to spend a lot of time setting up 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.
As you can see, there are two templates defined globally: Issues Details Excel and Sample Bulk Export With Cover. These templates will be available to be used on either or both issue types. Each issue type has its own template mapping configuration.
The “old way” of setting up templates is still possible.
New “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.
The configuration field provides a helper to find Jira groups.
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 am 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}
Improved Wiki markup/HTML processing on Excel files
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.
Below is an 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 allows you to have the same output as your Jira instance and the notation is very simple.
For this example, we will export both checked and unchecked elements from the CheckList plugin.
The output is as follows:
Note that if you want to export only the checked elements, you can use the notation available in previous versions:
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.
Below is an example of a result with the warning message:
General improvements and bug fixes
Enhancements and minor bugs were also solved.
Learn More
To see the complete list of requests being addressed by Xporter v5.5, please check out our Jira project here.
