Versions Compared

Old Version 25

changes.mady.by.user Rui Rodrigues

Saved on

compared with

New Version Current

changes.mady.by.user Rui Rodrigues

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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.


Table of Contents

Rollback to Xporter 6.0.x

Warning

Rollback to Xporter 6.0.x might have a big impact on your Jira instance. We strongly advise you not to do it.

This is because we changed database rules like:

  • Templates can have the same name and filename.
  • Scheduled reports can have the same name.
  • Permission schemes can have the same name.

These rules did not apply in previous versions when the fields were unique. If rollback happens, it can generate a Database error stopping Xporter from working.

Furthermore, when the user returns to Xporter 6.0.0 the migration tasks won't run again and all the data created on Xporter 5.x.x won't be correctly read on Xporter 6.0.0.



Highlights for this release

...

Panel
borderColor#F3F3F3
bgColor#FAFAFA
borderWidth1px
Section

Performance Improvements


Column
width50%

Several improvements were done in order to speed up the export process and reduce the amount of memory used during document generation.

Processing logic was updated to get better performance during:

  • Loading Fields and custom fields
  • Processing the Jira Issue data from related issues




Rollback to Xporter 6.0.x

Warning

Rollback to Xporter 6.0.x might have a big impact on your Jira instance. We strongly advise you not to do it.

This is because we changed database rules like:

  • Templates can have the same name and filename.
  • Scheduled reports can have the same name.
  • Permission schemes can have the same name.

These rules did not apply in previous versions when the fields were unique. If rollback happens, it can generate a Database error stopping Xporter from working.

Furthermore, when the user returns to Xporter 6.0.0 the migration tasks won't run again and all the data created on Xporter 5.x.x won't be correctly read on Xporter 6.0.0.


New Features and Bug Fixes

...