The Xporter for Jira team proudly announces the release of Xporter 5.7.0.
This point release contains several new features, improvements and bug fixes.
Highlights for this release
Mappings related with Template information
This feature will allow you to use mappings related with Template information.
//available mappings
//The Template name
${XporterTemplate.Name}
//The Template description
${XporterTemplate.Description}
//The Template type (Word, Excel, RTF...)
${XporterTemplate.Type}
//The filename
${XporterTemplate.Filename}
//The installation source
${XporterTemplate.Source}
//The creator of template
${XporterTemplate.Creator}
//Who has modified the template
${XporterTemplate.ModifiedBy}
//Created date
${XporterTemplate.Created}
//Updated date
${XporterTemplate.Updated}
Audit Log with all events related to document generation
This new feature will allow JIRA administrators see all export events related to Xporter. All information will be listed on a table, as you can see on the right side.
This table provides the following actions:
- Input text to filter by keyword
- Filter by source
- Date range
- Audit log settings
- Retention Time
- Disable/Enable Audit log
Audit log screen
Define final report name for Single and Bulk export
This feature will allow you to define a final report name for Single and Bulk export and are available on Xporter issue detail panel and bulk export screen.
The file name can resolve mappings as it is being made on workflow post functions (Date, Key...).
Issue detail panel
Bulk export screen
Jira Service Desk integration is now better than ever
This release will allow exporting more information related to the SLA.
Each SLA has information when started, stopped and whether it breached the SLA goal.
SLA notation is:
${<SLA custom field>.<Field>} |
Fields available
SLA fields | Description |
|---|---|
elapsedTime | Returns the total time the SLA has been running |
startTime | Returns the date when the SLA started |
stopTime | Returns the date when the SLA stopped |
goalDuration | Returns the date with the SLA duration |
breached | Returns a boolean if the SLA is breached |
paused | Returns a boolean if the SLA is paused |
withinCalendarHours | Returns a boolean if the SLA is within calendar hours |
Bulk Export and Xporter Reports screen improved
After getting some feedback from some customer we've decided to improve our Bulk/Xporter Reports screen. We added a button to download the generated document instead of having a link inside of the success message.
See how does it look like.
Xray integration is now faster than ever
Some changes were done on Test Status, Test Plan Overall Execution Status and Test Execution Overal Execution Status due to some performance problems reported by customers.
Here is the new notation to get the status printed:
# Test Plan and Test Execution
#Overall Execution Status (percentage + total of testes per status)
Todo: ${Overall Execution Status.TODO.Percentage}% (Overall Execution Status.TODO.Count})
Fail: ${Overall Execution Status.FAIL.Percentage}% (Overall Execution Status.FAIL.Count})
Pass: ${Overall Execution Status.PASS.Percentage}% (Overall Execution Status.PASS.Count})
Executing: ${Overall Execution Status.EXECUTING.Percentage}% (Overall Execution Status.EXECUTING.Count})
Aborted: ${Overall Execution Status.ABORTED.Percentage}% (Overall Execution Status.ABORTED.Count})
#Test Set
#Test Set Status (percentage + total of tests per status)
Todo: ${Test Set Status.TODO.Percentage}% (Test Set Status.TODO.Count})
Fail: ${Test Set Status.FAIL.Percentage}% (Test Set Status.FAIL.Count})
Pass: ${Test Set Status.PASS.Percentage}% (Test Set Status.PASS.Count})
Executing: ${Test Set Status.EXECUTING.Percentage}% (Test Set Status.EXECUTING.Count})
Aborted: ${Test Set Status.ABORTED.Percentage}% (Test Set Status.ABORTED.Count})
Now, with this new notation, you are able to get the percentage and the number of tests per status.
Some improvements were done in order to reduce the document generation time and to avoid affecting Jira performance.
Tempo timesheet integration improved
Tempo Timesheets allows the customer to configure custom attributes on the worklog level. In that way, this new Xporter version will allow those attributes from Tempo Timesheets.
Here is the new notation to get the worklog attributes printed:
#{for worklogs}
Author: ${Worklogs[n].Author}
Comment: ${Worklogs[n].Comment}
Time Spent: ${Worklogs[n].TimeSpentFormatted}
Attribute: ${Worklogs[n].<My Attribute Name>}
2nd Attribute: ${Worklogs[n].<My Seconde Attribute Name>}
Billed hours: ${Worklogs[n].BilledHoursFormatted}
#{end}