10 August 2021
The Xporter for Jira team proudly announces the release of Xporter 6.8.0. This point release contains several new features and bug fixes.
| Info |
|---|
If installing manually from the Atlassian Marketplace, please make sure you install the correct asset for your Jira version (i.e. 7.x, 8.x, datacenter) from the releases page. |
| Panel |
|---|
| borderColor | #F3F3F3 |
|---|
| bgColor | #FAFAFA |
|---|
| borderWidth | 1px |
|---|
|
Migrate Xporter Workflow Post-Functions| Column |
|---|
| Now in Xporter, it is possible to migrate Workflow Post-functions. Please, have special attention to the following cases: - If it is not the first migration, all the post functions that are migrated will have to be edited to update the template and file server if you are using it.
- If you have any of the actions to send an email and in the fields To, Cc and Bcc there is the name of a user or a group, this data is not supported by Xporter Cloud.
- If the action is Save on Jira host, this action will be deleted and if it is unique post action, the post function will also be deleted.
- Server Post functions can have project Templates, but in the Cloud that is not possible, which means that every Post function with Templates at the project level, will be migrated without a template.
- If we are migrating an Action to upload a file into a File Server Confluence, this action will be migrated. However, the confluence should be added manually on current action on the cloud side.
|
|
Bug Fixes in this release
| Jira |
|---|
| server | Xpand IT Issue Tracker |
|---|
| columns | key,type,summary,fixversions,resolution |
|---|
| maximumIssues | 20 |
|---|
| jqlQuery | project = XPORTER AND issuetype in (Bug, Improvement, Story) AND fixVersion = "6.8.0" and resolution not in (Duplicate, "Won't fix", "Won't do")order by issuetype desc |
|---|
| serverId | b6309ad5-5416-33d6-9a09-a3e02f20d3e6 |
|---|
|