Release Notes

IssueSYNC 3.0 is compatible with 2.x versions and Jira Cloud.

New Features:

• Field Mapping now supports Expose & Receive logic.

Improvements:

• Connection is a required field for synchronization scheme and can not be changer later on. You can edit connection itself.
• Field synchronization problems are more precisely described in Problems section.
• More precise problem description.
• Improved synchronization stability & reliability.
• A lot of minor improvements under the hood

Bugfixes:

• Request Type synchronization fix
• Due Date synchronization fix
• Other minior bugfixes

NOTICE:
Reverting to 2.x versions is not supported.

New Features:

• Configuration overview in project's settings summary
• Scope of synchronization scheme (global or defined project)
  • Distinguished configuration permissions for project admin and jira admin
• Configuration from project settings
• Synchronization schemes copy

Improvements:

• Banners added in configuration view containing configuration informations
• Workflow Mapping Schemes view updated
• Improved security
• Other minior imprevements

Bugfixes:

• Sometimes requests fails to close - httpClient library version upgraded
• Other minior bugfixes

New Features:

• Public REST API to get list of synchronized issues.

Improvements:

• Fields synchronization:1. Only fields with values will be sent to remote Jira instance. That can prevent from issue creation errors such us: field is not on create screen.2. Improved field mapping flexibility.3. Sprint to text custom field mapping support
• Performance improvements
• Other minior improvements

Bugfixes:

• Some field's value removal (field was set with empty value, no text, etc.) was not synchronzied and in remote Issue value was present
• Workflow synchronization fix
• Creating local connections error fix
• Field mapping synchronization issue - affects custom aliases for field mapping.
• Other minior bugfixes

Improvements:

• You can set how old your synchronization history entry to archive.
• Load time decrease.
• Synchronization error such as field update can be retried from both source and destination Jira instance.
• Improved information logging (such as connection or synchronization errors)

Bugfixes:

• Archivization turned on could cause a synchronization errors.
• Comments synchronization issues after license expiration. (after new license was applied).
• When creating context project could not be set even if it has been previously choosen on the interface.

Other minior improvements and bugfixes.

New features:

• Improved error handling of synchronzied issue creation and updating. This case applies to Jira instances, where configuration changes. Documentation can be found here.

Improvements:

• Logs are now more descriptive, so it's easier to debug the application.
• Performance.

Bugfixes:

• Case when synchronization does not work on oracle database, because unsupported BLOB type is being used has been fixed.This required IssueSYNC's database schema upgrade.

​New Features:

• Better control over what's being send and received:
  
  • ​Send only specific comments type (OFF, JIRA native, IssueSYNC's, service desk shared or service desk internal)
  • ​Choose destination comment type of received comments (OFF, JIRA native, IssueSYNC's, service desk shared or service desk internal)
  • ​Turn on/off sending attachments
  • ​Turn on/off receiving attachments
  • ​Turn on/off sending worklog
  • ​Turn on/off receiving worklog
  • ​New synchronization status "Receive disabled"

Improvements:

• Configuration panel improvements
• Performance improvements
• Synchronization process stabilization

Bugfixes:

• Customer Request type field update fix
• Transition are no longer processed in wrong order
• ​Configuration panel now supports IE11
• Remote issue link is no longer erased
• License validation shows warning on evaluation license

Improvements:

• Configuration save button activates when change is detected
• Changed colors of save button
• Configuration changes are confirmed by proper on-screen notification
• Configuration data stored in browser cache for faster page loading.
• Comments synchronization improvements
• External comments shows even when context has been deleted
• Performance improvements
• Stability improvements

Bugfixes:

• Cascading fields were not parsing to custom text field
• Service desk comment added on transition screen was not synchronizing
• All <-> All transition were causing crash of workflow mapping screen
• Technical user lack of permission to create issue in project scope was blocking any further synchronization
• Leaving project and issue type not set in context where causing configuration application break when summary page where accessed
• NPE removal
• Delete trigger was causing SQL statement exception
• Issue commented event in create trigger was preventing comments from synchronizing

Bugfixes:

• Technical User is being cleared what prevents issues from updating (no authorization)
• External comments tab shows contexts, which has not been configured to synchronzie IssueSYNC comments
• NPE removal
• Upgrading dialog does not disappear when JIRA runs on MSSQL

Improvements:

• Minor UI improvements
• On issue view only for contexts, which are active and fulfils JQL:
  • Create Remote button is shown
  • Synchronization History Tab is shown
• Comments addition no longer triggers UPDATE message to be sent to remote JIRA instance
• If CREATE message is in CANCELLED status, Retry Create Remote button is shown
• better performance
• less calls to database

Stabilization:

• Better synchronization handling
• Better queues handling

Improvements:

• Technical user permissions check
• Synchronziation scheme summary
• Synchronization scheme name editable in schemes list
• Minior design improvements
• Technical user credentials are overriden by browser autofill
• Check for duplicated connection authorization keys

Bugfixes:

• Synchronization schemes are not created, when plugin is upgraded from pre 2.0 version
• No response message is sent to JIRA Cloud
• HealthBoard view is not visible
• Old, irrelevant configuration cleanup

Stabilization:

• Comments option storage unified
• Performance improvements
• Other minior changes