The 2.10.2 hot fix release for Version & Component Sync includes the following bug fix(es):

• Improve messaging on introduction page
• Only disable manipulating versions/components of linked projects if the project is part of an active synchronisation configuration and Version & Component Sync has been enabled
• Aggregated Releases section incorrectly shows releases from projects not associated with the source project
• Version/components are not synchronised properly because of a highly unlikely ID collision that causes the link between source and target project to become corrupted

It is advised that all customers update to the latest version as soon as possible.

The 2.10.2 hot fix release for Version & Component Sync includes the following bug fix(es):

• Improve messaging on introduction page
• Only disable manipulating versions/components of linked projects if the project is part of an active synchronisation configuration and Version & Component Sync has been enabled
• Aggregated Releases section incorrectly shows releases from projects not associated with the source project
• Version/components are not synchronised properly because of a highly unlikely ID collision that causes the link between source and target project to become corrupted

It is advised that all customers update to the latest version as soon as possible.

The 2.10.1 hot fix release for Version & Component Sync includes the following bug fix(es):

• Components can be added to linked projects, even in full synchronisation mode

It is advised that all customers update to the latest version as soon as possible.

The 2.10.1 hot fix release for Version & Component Sync includes the following bug fix(es):

• Components can be added to linked projects, even in full synchronisation mode

It is advised that all customers update to the latest version as soon as possible.

This release is to provide Jira 9+ support and does not include any new features or bug fixes.

Because of breaking changes in Jira 9.0.0 that are not backwards compatible, all customers are encouraged to upgrade to Jira 9+ and Version & Component Sync for Jira 2.10+.

All previous versions of Version & Component Sync for Jira are now end-of-life as stated in our Service Level Agreement. The apps will continue to work, but will no longer receive any updates (incl. bug fixes and new features). Any subsequent release of Version & Component Sync for Jira will only support Jira 9+.

This release is to provide Jira 9+ support and does not include any new features or bug fixes.

Because of breaking changes in Jira 9.0.0 that are not backwards compatible, all customers are encouraged to upgrade to Jira 9+ and Version & Component Sync for Jira 2.10+.

All previous versions of Version & Component Sync for Jira are now end-of-life as stated in our Service Level Agreement. The apps will continue to work, but will no longer receive any updates (incl. bug fixes and new features). Any subsequent release of Version & Component Sync for Jira will only support Jira 9+.

The 2.9.8 hot fix release for Version & Component Sync includes the following bug fix(es):

• Aggregated release page is empty
• Link to settings page is broken
• Empty conflicts dialog
• Processing Move events causes performance issues

It is advised that all customers update to the latest version as soon as possible.

The 2.9.8 hot fix release for Version & Component Sync includes the following bug fix(es):

• Aggregated release page is empty
• Link to settings page is broken
• Empty conflicts dialog
• Processing Move events causes performance issues

It is advised that all customers update to the latest version as soon as possible.

The 2.9.7 hot fix release for Version & Component Sync includes the following bug fix(es):

• CVE-2022-0540 - Authentication bypass in Seraph

It is advised that all customers update to the latest version as soon as possible.

The 2.9.7 hot fix release for Version & Component Sync includes the following bug fix(es):

• CVE-2022-0540 - Authentication bypass in Seraph

It is advised that all customers update to the latest version as soon as possible.

The 2.9.6 hot fix release includes the following bug fixes:

• Failed linked project deletion attempts remain stuck in pending status and cannot be cancelled or retried
• Project link deletion can cause a foreign key constraint error when the project contains a specific type of synchronisation conflict

It is recommended for all customers to update to the latest version.

The 2.9.6 hot fix release includes the following bug fixes:

• Failed linked project deletion attempts remain stuck in pending status and cannot be cancelled or retried
• Project link deletion can cause a foreign key constraint error when the project contains a specific type of synchronisation conflict

It is recommended for all customers to update to the latest version.

The 2.9.5 hot fix release includes the following bug fixes:

• Added support for context path
• Task Manager is not automatically purged of old tasks
• Project list shows infinite spinner because of missing permissions
• Empty page is shown when trying to create project link
• Page scroll bars are increased indefinitely because of incorrect content height calculation
• Version events are still updated although project synchronisation is disabled
• Version & Component Sync cannot be used in combination with Figma for Jira
• Version & Component Sync cannot be used in combination with QMetry Test Management for Jira

It is recommended for all customers to update to the latest version.

The 2.9.5 hot fix release includes the following bug fixes:

• Added support for context path
• Task Manager is not automatically purged of old tasks
• Project list shows infinite spinner because of missing permissions
• Empty page is shown when trying to create project link
• Page scroll bars are increased indefinitely because of incorrect content height calculation
• Version events are still updated although project synchronisation is disabled
• Version & Component Sync cannot be used in combination with Figma for Jira
• Version & Component Sync cannot be used in combination with QMetry Test Management for Jira

It is recommended for all customers to update to the latest version.

The 2.9.4 hot fix release includes the following bug fixes:

• Re-enable support for context path (2nd attempt)

It is recommended for all customers to update to the latest version.

The 2.9.4 hot fix release includes the following bug fixes:

• Re-enable support for context path (2nd attempt)

It is recommended for all customers to update to the latest version.

The 2.9.3 hot fix release includes the following bug fixes:

• Re-enable support for context path

It is recommended for all customers to update to the latest version.

The 2.9.3 hot fix release includes the following bug fixes:

• Re-enable support for context path

It is recommended for all customers to update to the latest version.

The 2.9.2 hot fix release includes the following bug fixes:

• Configure link on Manage Apps page is a dead link
• Fixed column width of Aggregated releases page results in version names not being completely visible

It is recommended for all customers to update to the latest version.

The 2.9.2 hot fix release includes the following bug fixes:

• Configure link on Manage Apps page is a dead link
• Fixed column width of Aggregated releases page results in version names not being completely visible

It is recommended for all customers to update to the latest version.

The 2.9.1 hot fix release addresses several performance issues:

• Improve caching of stale data to limit database requests
• Improve loading of Task Manager
• Introducing database indexes to improve query performance
• Limit number of database calls during synchronisation

It is recommended for all customers to update to the latest version, as these improvements can resolve database CPU/Memory resource consumption issues.

Jira instances with enterprise data sets (2000+ versions per project, synchronisation to 100+ projects) can see significant improvements (from ~70 minutes per project to 5 seconds).

Please make sure to monitor CPU/Memory consumption of Jira Data Center nodes after upgrading as more aggressive caching may require additional memory allocation.

After successfully upgrading, it is recommended to review the thread count (Jira Administration > Manage Apps > Version & Component Sync > Settings) and incrementally increase to further improve synchronisation time.

The 2.9.1 hot fix release addresses several performance issues:

• Improve caching of stale data to limit database requests
• Improve loading of Task Manager
• Introducing database indexes to improve query performance
• Limit number of database calls during synchronisation

It is recommended for all customers to update to the latest version, as these improvements can resolve database CPU/Memory resource consumption issues.

Jira instances with enterprise data sets (2000+ versions per project, synchronisation to 100+ projects) can see significant improvements (from ~70 minutes per project to 5 seconds).

Please make sure to monitor CPU/Memory consumption of Jira Data Center nodes after upgrading as more aggressive caching may require additional memory allocation.

After successfully upgrading, it is recommended to review the thread count (Jira Administration > Manage Apps > Version & Component Sync > Settings) and incrementally increase to further improve synchronisation time.

This release includes an improved UI for project link management and introduces more granular control over the project synchronisation process. In addition, it includes several bug fixes:

• Issues are being double counted in the overall aggregated release
• Task Manager page crashes when there are too many tasks

All customers are advised to upgrade to the latest version as this is an important preparation for the next major release (3.0.0). Upgrade to 3.0.0 will not be available unless 2.9.0 has been previously installed.

This release includes an improved UI for project link management and introduces more granular control over the project synchronisation process. In addition, it includes several bug fixes:

• Issues are being double counted in the overall aggregated release
• Task Manager page crashes when there are too many tasks

All customers are advised to upgrade to the latest version as this is an important preparation for the next major release (3.0.0). Upgrade to 3.0.0 will not be available unless 2.9.0 has been previously installed.

The 2.8.2 hot fix release addresses the following issue:

• org.postgresql.util.PSQLException: ERROR: relation "public.AO_687793_VCSLOG_ENTRY" does not exist

It is recommended for all customers to update to the latest version.

The 2.8.2 hot fix release addresses the following issue:

• org.postgresql.util.PSQLException: ERROR: relation "public.AO_687793_VCSLOG_ENTRY" does not exist

It is recommended for all customers to update to the latest version.

The 2.8.1 hot fix release addresses the following issue:

• Prevent duplication of AO_687793_VCSENTITY table rows

It is recommended for all customers to immediately update to version 2.8.1 as there are situations in which this issue can cause the AO_687793_VCSENTITY to grow exponentially and consume database CPU, memory and storage resources.

Customers are also advices to check for duplications of rows in the AO_687793_VCSENTITY table. If duplicate rows exist, it is advised to clean the database table. Please contact CollabSoft support if you need assistance.

The 2.8.1 hot fix release addresses the following issue:

• Prevent duplication of AO_687793_VCSENTITY table rows

It is recommended for all customers to immediately update to version 2.8.1 as there are situations in which this issue can cause the AO_687793_VCSENTITY to grow exponentially and consume database CPU, memory and storage resources.

Customers are also advices to check for duplications of rows in the AO_687793_VCSENTITY table. If duplicate rows exist, it is advised to clean the database table. Please contact CollabSoft support if you need assistance.

This release includes fixes in preparation of the upcoming VCS 3.0 and VCS Cloud release.

• Remove source project entity and only use database entities for linked projects
• Create sync task per linked project
• Create cleanup tasks for orphaned projects, stale conflicts, logs
• Use task manager for cleanup tasks with logs per task
• As a SysAdmin I want to see the logs per Task
• As a SysAdmin I want to be able to set the number of threads for sync

In addition, it includes a few bug fixes:

• Infinite spinner when deleting orphaned projects
• NullPointerException prevention
• Manage Versions screen misses header in table
• Disabling “Release” or “Archive” events does not work
• Removed Conflicts error message in projects that are not part of VCS config

All customers are advised to upgrade to the latest version as this is an important preparation for the next major release (3.0.0). Upgrade to 3.0.0 will not be available unless 2.8.0 has been previously installed.

This release includes fixes in preparation of the upcoming VCS 3.0 and VCS Cloud release.

• Remove source project entity and only use database entities for linked projects
• Create sync task per linked project
• Create cleanup tasks for orphaned projects, stale conflicts, logs
• Use task manager for cleanup tasks with logs per task
• As a SysAdmin I want to see the logs per Task
• As a SysAdmin I want to be able to set the number of threads for sync

In addition, it includes a few bug fixes:

• Infinite spinner when deleting orphaned projects
• NullPointerException prevention
• Manage Versions screen misses header in table
• Disabling “Release” or “Archive” events does not work
• Removed Conflicts error message in projects that are not part of VCS config

All customers are advised to upgrade to the latest version as this is an important preparation for the next major release (3.0.0). Upgrade to 3.0.0 will not be available unless 2.8.0 has been previously installed.

The 2.7.7 release of Version & Component Sync for Jira includes the following new features:

• Introduces "Aggregated Releases" panel showing version progress spanning multiple projects

The release als includes the following bug fixes:

• Infinite spinner is shown for projects that have been deleted or archived (only Jira 7.x or below)
• Jira interface is frozen in IE11
• Linked projects disappear from Component Sync project panel after refresh
• Component sync conflicts do not show, or are labelled as "version"
• Version Sync panel and Version page show conflicts warning even though there are only Component Sync conflicts
• Conflicts table becomes flooded with duplicate conflicts
• Marking conflicts as resolved/ignored is not persisted

It is recommended to all customers to purge / truncate the contents of the AO_687793_VCSCONFLICT table in their database after installing the 2.7.7 release.

The 2.7.7 release of Version & Component Sync for Jira includes the following new features:

• Introduces "Aggregated Releases" panel showing version progress spanning multiple projects

The release als includes the following bug fixes:

• Infinite spinner is shown for projects that have been deleted or archived (only Jira 7.x or below)
• Jira interface is frozen in IE11
• Linked projects disappear from Component Sync project panel after refresh
• Component sync conflicts do not show, or are labelled as "version"
• Version Sync panel and Version page show conflicts warning even though there are only Component Sync conflicts
• Conflicts table becomes flooded with duplicate conflicts
• Marking conflicts as resolved/ignored is not persisted

It is recommended to all customers to purge / truncate the contents of the AO_687793_VCSCONFLICT table in their database after installing the 2.7.7 release.

The 2.7.6 hotfix release includes the following bug fix in Version & Component Sync for Jira:

• Running tasks becoming stale and blocking synchronisation.

All customers who are using Version & Component Sync for Jira are advised to upgrade to the latest version

The 2.7.6 hotfix release includes the following bug fix in Version & Component Sync for Jira:

• Running tasks becoming stale and blocking synchronisation.

All customers who are using Version & Component Sync for Jira are advised to upgrade to the latest version

The 2.7.5 hotfix release includes the following bug fix in Version & Component Sync for Jira:

• Resolves NullPointerException thrown when retrieving orphaned linked projects

All customers who are using Version & Component Sync for Jira are advised to upgrade to the latest version.

The 2.7.5 hotfix release includes the following bug fix in Version & Component Sync for Jira:

• Resolves NullPointerException thrown when retrieving orphaned linked projects

All customers who are using Version & Component Sync for Jira are advised to upgrade to the latest version.

The 2.7.4 hotfix release includes the following bug fix in Version & Component Sync for Jira:

• Resolves infinite loading when bulk creating project links
• Updated conformation modal when creating project links
• Improved performance by only retrieving a single version to determine of project already has versions

All customers who are using Version & Component Sync for Jira are advised to upgrade to the latest version.

The 2.7.4 hotfix release includes the following bug fix in Version & Component Sync for Jira:

• Resolves infinite loading when bulk creating project links
• Updated conformation modal when creating project links
• Improved performance by only retrieving a single version to determine of project already has versions

All customers who are using Version & Component Sync for Jira are advised to upgrade to the latest version.

The 2.7.3 hotfix release includes the following bug fix in Version & Component Sync for Jira:

• Resolves infinite loading off the conflicts page by adding pagination.

All customers who are using Version & Component Sync for Jira are advised to upgrade to the latest version.

The 2.7.3 hotfix release includes the following bug fix in Version & Component Sync for Jira:

• Resolves infinite loading off the conflicts page by adding pagination.

All customers who are using Version & Component Sync for Jira are advised to upgrade to the latest version.

The 2.7.2 hotfix release includes bug fixes in Version & Component Sync for Jira:

• A conflicting dependency on different versions of arrive.js by Version & Component Sync and Jira Service Desk results in an error while loading any of the Version & Component Sync pages

All customers who are using Version & Component Sync for Jira (version 2.5.0 and above) in a Jira instance that also has Jira Service Desk installed are advised to upgrade to the latest version.

The 2.7.2 hotfix release includes bug fixes in Version & Component Sync for Jira:

• A conflicting dependency on different versions of arrive.js by Version & Component Sync and Jira Service Desk results in an error while loading any of the Version & Component Sync pages

All customers who are using Version & Component Sync for Jira (version 2.5.0 and above) in a Jira instance that also has Jira Service Desk installed are advised to upgrade to the latest version.

The 2.7.0 release includes bug fixes in Version & Component Sync for Jira:

• Incorrect link to the app configuration & settings page
• The client-side code might break apps from other vendors

All customers are recommended to upgrade to the latest version of VCS, especially if they are using apps from other vendors in their instance.

The 2.7.1 release includes bug fixes in Version & Component Sync for Jira:

• Incorrect link to the app configuration & settings page
• The client-side code might break apps from other vendors

All customers are recommended to upgrade to the latest version of VCS, especially if they are using apps from other vendors in their instance.

The 2.7.0 release includes several performance & bug fixes in Version & Component Sync for Jira:

• Fixed loading issue on “Add project link” page
• Fixed "getvcstype] type of class is neither a version nor projectcomponent" error. Caused by updating empty release & start date
• Fixed move issue caused by deletion of version(s)
• Introducing new Task Manager to improve visibility of the background synchronisation process

The 2.7.0 release includes several performance & bug fixes in Version & Component Sync for Jira:

• Fixed loading issue on “Add project link” page
• Fixed "getvcstype] type of class is neither a version nor projectcomponent" error. Caused by updating empty release & start date
• Fixed move issue caused by deletion of version(s)
• Introducing new Task Manager to improve visibility of the background synchronisation process

The 2.6.0 release includes the following fixes for Version & Component Sync for Jira:

• Fixed NullPointerException when retrieving configuration of orphaned projects
• Fixed race condition when renaming versions/components during synchronisation
• Improved log messages for licensing errors and/or disabled synchronisation
• Improved database result caching for performance- VCS will now create a synchronisation conflict when removing versions/components that are in used in linked projects

The 2.6.0 release includes the following fixes for Version & Component Sync for Jira:

• Fixed NullPointerException when retrieving configuration of orphaned projects
• Fixed race condition when renaming versions/components during synchronisation
• Improved log messages for licensing errors and/or disabled synchronisation
• Improved database result caching for performance
• VCS will now create a synchronisation conflict when removing versions/components that are in used in linked projects

The 2.5.8 release includes several performance fixes in Version & Component Sync for Jira:

• Added pagination to project selection to avoid UI freeze
• Improved caching of versions/components during synchronisation
• DEBUG log level is redirected to log4j for more granular control over log output

All customers are advised to upgrade to the latest version of Version & Component Sync. Data Center customers on version 2.5.0 and greater are advised to upgrade at their earliest convenience to avoid possible performance issues.

The 2.5.8 release includes several performance fixes in Version & Component Sync for Jira:

• Added pagination to project selection to avoid UI freeze
• Improved caching of versions/components during synchronisation
• DEBUG log level is redirected to log4j for more granular control over log output

All customers are advised to upgrade to the latest version of Version & Component Sync. Data Center customers on version 2.5.0 and greater are advised to upgrade at their earliest convenience to avoid possible performance issues.

This release is meant to mitigate three known issues in Version & Component Sync for Jira:

• A bug in the Jira VersionManager class (confirmed by Atlassian Support) which might cause duplicate versions to be created within a project. An additional check has been introduced to prevent this event from occurring during synchronisation, while awaiting a permanent fix from Atlassian.
• In an effort to reduce the possibility of data loss, Version & Component Sync will now no longer delete versions from linked projects which have issues attached to them. A synchronisation conflict will be created instead, which will allow for manual intervention (re-assigning the fix/affected version).
• The Jira VersionManager implementation to retrieve versions by name is very inefficient. Version & Component Sync has been optimised for performance by using other means (incl. caching) to avoid costly database calls.

All customers are advised to upgrade to the latest version of Version & Component Sync.

This release is meant to mitigate three known issues in Version & Component Sync for Jira:

• A bug in the Jira VersionManager class (confirmed by Atlassian Support) which might cause duplicate versions to be created within a project. An additional check has been introduced to prevent this event from occurring during synchronisation, while awaiting a permanent fix from Atlassian.
• In an effort to reduce the possibility of data loss, Version & Component Sync will now no longer delete versions from linked projects which have issues attached to them. A synchronisation conflict will be created instead, which will allow for manual intervention (re-assigning the fix/affected version).
• The Jira VersionManager implementation to retrieve versions by name is very inefficient. Version & Component Sync has been optimised for performance by using other means (incl. caching) to avoid costly database calls.

All customers are advised to upgrade to the latest version of Version & Component Sync.

This hot fix release is intended to fix three issues:

• Increase column length of VCS_CONFLICT `message` field in the database to ensure the error message of the a synchronisation conflict can be stored properly
• "java.lang.IllegalArgumentException: [getVCSType] Type of entity is neither Version nor ProjectComponent" is thrown when synchronising deleted versions/components
• Increase logging of the background synchronisation task

It is recommended for all customers to update to the latest version of Version & Component Sync if they are experiencing problems during synchronisation, as the first two issues can result in the untimely and uncontrolled end of the versions/components synchronisation process.

This hot fix release is intended to fix three issues:

• Increase column length of VCS_CONFLICT `message` field in the database to ensure the error message of the a synchronisation conflict can be stored properly
• "java.lang.IllegalArgumentException: [getVCSType] Type of entity is neither Version nor ProjectComponent" is thrown when synchronising deleted versions/components
• Increase logging of the background synchronisation task

It is recommended for all customers to update to the latest version of Version & Component Sync if they are experiencing problems during synchronisation, as the first two issues can result in the untimely and uncontrolled end of the versions/components synchronisation process.

This release fixes an issue with Out Of Memory / Garbage Collection exceptions that may occur when Version & Component Sync for Jira tries to purge the audit logs database table.This issue should only occur for customers who have their log level set to DEBUG and are experiencing excessive amount of log entries in their AO_687793_VCSLOG_ENTRY database table.

It is recommended to set the Version & Component Sync for Jira log level to INFO unless you are experiencing issues and are requested to provide DEBUG log information by our support staff.

This release fixes an issue with Out Of Memory / Garbage Collection exceptions that may occur when Version & Component Sync for Jira tries to purge the audit logs database table.This issue should only occur for customers who have their log level set to DEBUG and are experiencing excessive amount of log entries in their AO_687793_VCSLOG_ENTRY database table.

It is recommended to set the Version & Component Sync for Jira log level to INFO unless you are experiencing issues and are requested to provide DEBUG log information by our support staff.

This release fixes an issue with the audit logs database table not being purged properly. The audit log database tables should be purged automatically with a retention of log entries for max. 7 days.

Some customers have reported that the background service responsible for purging the log files did not register correctly, causing database tables to be flooded.

All customers using version 2.5.0 or higher are recommended to upgrade to this latest version.

In addition, please check the size of the AO_687793_VCSLOG_ENTRY table in your database. Once you've installed this version, the background process should register correctly. You can verify this by going to Jira Administration > System > Scheduler details. This page should have a "net.collabsoft.plugins.jira.jira-version-sync.VCSLogManager" group. The background task will run every day 4am (default timezone).You may need to reclaim space from your database once the purge has completed successfully.

This release fixes an issue with the audit logs database table not being purged properly. The audit log database tables should be purged automatically with a retention of log entries for max. 7 days.

Some customers have reported that the background service responsible for purging the log files did not register correctly, causing database tables to be flooded.

All customers using version 2.5.0 or higher are recommended to upgrade to this latest version.

In addition, please check the size of the AO_687793_VCSLOG_ENTRY table in your database. Once you've installed this version, the background process should register correctly. You can verify this by going to Jira Administration > System > Scheduler details. This page should have a "net.collabsoft.plugins.jira.jira-version-sync.VCSLogManager" group. The background task will run every day 4am (default timezone).You may need to reclaim space from your database once the purge has completed successfully.

This release fixes a minor issue with synchronising components between projects, in which a new project link is created between two existing projects that have identical components with different component name casing. This would result in an error during synchronisation.

The Version & Component Sync matching algorithm is now case-insensitive and will be able to identify that these components are actually the same (as per Jira specification).

This release fixes a minor issue with synchronising components between projects, in which a new project link is created between two existing projects that have identical components with different component name casing. This would result in an error during synchronisation.

The Version & Component Sync matching algorithm is now case-insensitive and will be able to identify that these components are actually the same (as per Jira specification).

This release fixes a specific issue for customers using Microsoft SQL database server (MSSQL), have a large number of versions (2500+) and are upgrading to Version & Component Sync 2.5.x

This release fixes a specific issue for customers using Microsoft SQL database server (MSSQL), have a large number of versions (2500+) and are upgrading to Version & Component Sync 2.5.x

This release is only meant to provide backwards compatibility of version 2.5.0 for all currently supported Jira installations. It has no additional features or fixes. Customers who have already installed 2.5.0 do not need to upgrade.

---Version & Component Sync for Jira 2.5.0 has been released.

This is a minor release and includes an updated UI, improved synchronisation conflict resolution, Jira 8.4+ compatibility and bug fixes.

We recommend all customers with Jira 8.4+ to upgrade to this version, as this is the final release prior to, and only available upgrade path for, the upcoming major release (3.0.0, or V3).

Read the Version & Component Sync announcements - Oct '19 update for a sneak preview of the new features in the V3 release.

This release is only meant to provide backwards compatibility of version 2.5.0 for all currently supported Jira installations. It has no additional features or fixes. Customers who have already installed 2.5.0 do not need to upgrade.

---

Version & Component Sync for Jira 2.5.0 has been released.

This is a minor release and includes an updated UI, improved synchronisation conflict resolution, Jira 8.4+ compatibility and bug fixes.

We recommend all customers with Jira 8.4+ to upgrade to this version, as this is the final release prior to, and only available upgrade path for, the upcoming major release (3.0.0, or V3).

Read the Version & Component Sync announcements - Oct '19 update for a sneak preview of the new features in the V3 release.

Version & Component Sync for Jira 2.5.0 has been released.This is a minor release and includes an updated UI, improved synchronisation conflict resolution, Jira 8.4+ compatibility and bug fixes.

We recommend all customers with Jira 8.4+ to upgrade to this version, as this is the final release prior to, and only available upgrade path for, the upcoming major release (3.0.0, or V3).

Read the Version & Component Sync announcements - Oct '19 update for a sneak preview of the new features in the V3 release.

Version & Component Sync for Jira 2.5.0 has been released.

This is a minor release and includes an updated UI, improved synchronisation conflict resolution, Jira 8.4+ compatibility and bug fixes.

We recommend all customers with Jira 8.4+ to upgrade to this version, as this is the final release prior to, and only available upgrade path for, the upcoming major release (3.0.0, or V3).

Read the Version & Component Sync announcements - Oct '19 update for a sneak preview of the new features in the V3 release.

This release only adds support for Jira Data Center. It does not include additional features or bug fixes. Customers who are not planning to upgrade to Jira Data Center do not need to install this version of the add-on. Customers with Jira Data Center are advised to upgrade prior to September 2019.

This release only adds support for Jira Data Center. It does not include additional features or bug fixes. Customers who are not planning to upgrade to Jira Data Center do not need to install this version of the add-on. Customers with Jira Data Center are advised to upgrade prior to September 2019.

This release only adds support for Jira 8.2+. It does not include additional features or bug fixes. Customers who are not planning to upgrade to Jira 8.2+ do not need to upgrade to this version of the add-on.

This release only adds support for Jira 8.1+. It does not include additional features or bug fixes. Customers who are not planning to upgrade to Jira 8.1+ do not need to upgrade to this version of the add-on.

This hotfix release is aimed at resolving the following issues that occurred as result of the 2.2.0 release:

• Background process no longer attached to Jira Scheduler API
• Scheduler not started when (re)installing/updating the add-on
• Multithreading option limits synchronisation to a single project
• UI elements are not updated on lazy loading of version/component table
• Add ability to remove all types of orphaned projects from the VCS settings page

All customers are recommended to update to the latest release of the add-on available for their Jira version.

The release includes the following bug fixes:

• Multithreading option limits synchronisation to a single project
• Versions/Components should not be editable in linked projects when "Full Synchronisation" is enabled
• Version Sync incorrectly says there are no suitable projects
• Version fields are no longer updated (name, description, start date, release date)
• moveToStartVersionSequence() throws java.lang.IllegalArgumentException: Object not contained in Collection
• VSVersion description field length to small (PostgreSQL ERROR: value too long for type character varying(255))

All customers are recommended to update to the latest release of the add-on available for their Jira version.

In addition, compatibility with Jira 8 BETA has been confirmed.

The 2.1.11 release contains the following fixes:

• Compatibility support for Jira 7.10.x
• java.lang.IllegalArgumentException: Component name X is not unique

This release only adds support for Jira 7.4+. It does not include additional features or bug fixes. Customers who are not planning to upgrade to Jira 7.4+ do not need to upgrade to this version of the add-on.

This release does not include any changes compared to 2.0.9, it is only a code-base alignment support release for adding Jira 7.4+ compatibility in the 2.1.10 version of the add-on. Customers using Jira 7.0.2 - 7.1.10 do not require to upgrade to this release.

This release includes two minor bug fixes:

• Possible NullPointerExceptions when retrieving Version Sync Conflicts
• Ability to create versions/components for child projects in Jira even though synchronisation mode has been set to 'Full Synchronisation'

This release introduces the Sync Conflicts overview to the project administration screen. If the add-on detects any errors during synchronisation it will now report those errors to the user, allowing them to manually resolve any synchronisation issues. The Sync Conflicts overview is available on the project administration page of the 'master' project from which the versions are replicated to other Jira projects.

This release also includes a permissions fix which limits the synchronisation project links a user can create to Jira projects for which the user is an administrator. In previous releases, users could create project links to all eligible Jira projects.

This bug fix release resolves an issue with project links not being properly deleted from the Version & Component Sync add-on configuration when the linked Jira project no longer exists. The Version & Component Sync add-on would continuously try to synchronise to the deleted project. In addition, the project link would also be incorrectly shown in the add-on settings 'Overview' page.

The release includes the following bug fixes:

• Due to a race condition in the client-side code execution, project administrators were still able to create/update/delete versions and components from linked projects, even though Full Synchronisation was enabled.
• Some customers experienced issues with the Version & Component Sync add-on settings overview page due to a NullPointerException when calling the Jira AvatarService.
• One of the confirmation dialogs showed an unresolved variable in the text.

All customers are recommended to update to the latest release of the add-on available for their Jira version.

This release fixes two major issues with the Version & Component Sync add-on:

• Due to a circular dependency while serialising Jira Project objects, a StackOverflow error is thrown when trying to add a new project link from the Version Sync or Component Sync panel. This prevents users from creating project links.
• The Jira application log contains IllegalArgumentExceptions stating that "Start date must be before the version release date". This is due to an incorrect version update order in which the start date was updated before updating the release date. If both dates have been adjusted, updating the start date first can trigger this error.

All current customers of Version & Component Sync for Jira are advised to upgrade to the latest version of the add-on.

The 2.0.4 release is a minor hotfix release which includes a solution to the following issues:

• Jira application logs show "java.lang.IllegalArgumentException:Object * not contained in Collection " errors. This error is thrown by the Jira VersionManager API and is not within scope of the Version & Component Sync add-on. The fix includes removing the error message from the Jira application log and providing a more meaningful description in the Version & Component Sync audit log.
• Jira application logs show "java.lang.IllegalArgumentException: A version with this name already exists in this project." errors. This exception has been moved from the Jira application log to the Version & Component Sync add-on audit log with a more detailed description of the problem and how to resolve it.
• In certain circumstances, inline editing of Versions & Components is still possible even if "Full Synchronisation" mode is enabled. This issue has been resolved.

The 2.1.3 hotfix release is a major bug fix release that resolves an issue that caused an excessive amount of VersionUpdateEvents in the Jira application log and read/write operations on the Jira database.

In addition, the hotfix release includes a new feature which allows add-on administrators to set the log level of the Version Sync audit log and confirmed compatibility with Jira 7.3.x.

This release fixes a the confusing message displayed on the project management screen when the Version or Component synchronisation has been disabled on the add-on settings page. It now contains a more clear text and a direct link to the settings page. Additionally, this release fixes the incorrect add-on configuration button link in the Universal Plugin Manager.

This release includes a long overdue update of the Version & Component sync add-on. It combines the previously separate Version Sync and Component Sync add-ons in a single product which is essential to Jira project administrators.

In addition to merging the two add-ons, the release contains the following fixes & improvements:

• Compatibility with Jira 7.2.x and Jira Data Center
• Major bug fixes, including the ability to rename versions / components
• Updated Component Sync to match features that already existed in Version Sync
• Updated UI to match the Atlassian design guidelines
• Improved performance for large Jira instances with multiple project link configurations
• Created 500+ unit and UI tests for improved quality assurance
• Created EULA, Service Level Agreement and support policy for improved customer experience

This release includes two minor bug fixes:

• Possible NullPointerExceptions when retrieving Version Sync Conflicts
• Ability to create versions/components for child projects in Jira even though synchronisation mode has been set to 'Full Synchronisation'

This release introduces the Sync Conflicts overview to the project administration screen. If the add-on detects any errors during synchronisation it will now report those errors to the user, allowing them to manually resolve any synchronisation issues. The Sync Conflicts overview is available on the project administration page of the 'master' project from which the versions are replicated to other Jira projects.

This release also includes a permissions fix which limits the synchronisation project links a user can create to Jira projects for which the user is an administrator. In previous releases, users could create project links to all eligible Jira projects.

This bug fix release resolves an issue with project links not being properly deleted from the Version & Component Sync add-on configuration when the linked Jira project no longer exists. The Version & Component Sync add-on would continuously try to synchronise to the deleted project. In addition, the project link would also be incorrectly shown in the add-on settings 'Overview' page.

The release includes the following bug fixes:

• Due to a race condition in the client-side code execution, project administrators were still able to create/update/delete versions and components from linked projects, even though Full Synchronisation was enabled.
• Some customers experienced issues with the Version & Component Sync add-on settings overview page due to a NullPointerException when calling the Jira AvatarService.
• One of the confirmation dialogs showed an unresolved variable in the text.

All customers are recommended to update to the latest release of the add-on available for their Jira version.

This release fixes two major issues with the Version & Component Sync add-on:

• Due to a circular dependency while serialising Jira Project objects, a StackOverflow error is thrown when trying to add a new project link from the Version Sync or Component Sync panel. This prevents users from creating project links.
• The Jira application log contains IllegalArgumentExceptions stating that "Start date must be before the version release date". This is due to an incorrect version update order in which the start date was updated before updating the release date. If both dates have been adjusted, updating the start date first can trigger this error.

All current customers of Version & Component Sync for Jira are advised to upgrade to the latest version of the add-on.

The 2.0.4 release is a minor hotfix release which includes a solution to the following issues:

• Jira application logs show "java.lang.IllegalArgumentException:Object * not contained in Collection" errors. This error is thrown by the Jira VersionManager API and is not within scope of the Version & Component Sync add-on. The fix includes removing the error message from the Jira application log and providing a more meaningful description in the Version & Component Sync audit log.
• Jira application logs show "java.lang.IllegalArgumentException: A version with this name already exists in this project." errors. This exception has been moved from the Jira application log to the Version & Component Sync add-on audit log with a more detailed description of the problem and how to resolve it.
• In certain circumstances, inline editing of Versions & Components is still possible even if "Full Synchronisation" mode is enabled. This issue has been resolved.

The 2.0.3 hotfix release is a major bug fix release that resolves an issue that caused an excessive amount of VersionUpdateEvents in the Jira application log and read/write operations on the Jira database.

In addition, the hotfix release includes a new feature which allows add-on administrators to set the log level of the Version Sync audit log.

This release fixes a the confusing message displayed on the project management screen when the Version or Component synchronisation has been disabled on the add-on settings page. It now contains a more clear text and a direct link to the settings page. Additionally, this release fixes the incorrect add-on configuration button link in the Universal Plugin Manager.

This release includes a long overdue update of the Version & Component sync add-on. It combines the previously separate Version Sync and Component Sync add-ons in a single product which is essential to Jira project administrators.

In addition to merging the two add-ons, the release contains the following fixes & improvements:

• Compatibility with Jira 7.0.x to 7.1.x and Jira Data Center
• Major bug fixes, including the ability to rename versions / components
• Updated Component Sync to match features that already existed in Version Sync
• Updated UI to match the Atlassian design guidelines
• Improved performance for large Jira instances with multiple project link configurations
• Created 500+ unit and UI tests for improved quality assurance
• Created EULA, Service Level Agreement and support policy for improved customer experience

This is the last release of Version & Component Sync for Jira that supports Jira 6.4, after it has reached End of Life (EOL) in March 2017.

The release includes the following bug fixes:

• Due to a race condition in the client-side code execution, project administrators were still able to create/update/delete versions and components from linked projects, even though Full Synchronisation was enabled.
• Some customers experienced issues with the Version & Component Sync add-on settings overview page due to a NullPointerException when calling the Jira AvatarService.
• One of the confirmation dialogs showed an unresolved variable in the text.

All customers are recommended to update to the latest release of the add-on available for their Jira version.

This release fixes two major issues with the Version & Component Sync add-on:

• Due to a circular dependency while serialising Jira Project objects, a StackOverflow error is thrown when trying to add a new project link from the Version Sync or Component Sync panel. This prevents users from creating project links.
• The Jira application log contains IllegalArgumentExceptions stating that "Start date must be before the version release date". This is due to an incorrect version update order in which the start date was updated before updating the release date. If both dates have been adjusted, updating the start date first can trigger this error.

All current customers of Version & Component Sync for Jira are advised to upgrade to the latest version of the add-on.

The 2.0.4 release is a minor hotfix release which includes a solution to the following issues:

• Jira application logs show "java.lang.IllegalArgumentException:Object * not contained in Collection " errors. This error is thrown by the Jira VersionManager API and is not within scope of the Version & Component Sync add-on. The fix includes removing the error message from the Jira application log and providing a more meaningful description in the Version & Component Sync audit log.
• Jira application logs show "java.lang.IllegalArgumentException: A version with this name already exists in this project." errors. This exception has been moved from the Jira application log to the Version & Component Sync add-on audit log with a more detailed description of the problem and how to resolve it.
• In certain circumstances, inline editing of Versions & Components is still possible even if "Full Synchronisation" mode is enabled. This issue has been resolved.

The 1.4.2 hotfix release is a major bug fix release that resolves an issue that caused an excessive amount of VersionUpdateEvents in the Jira application log and read/write operations on the Jira database.

In addition, the hotfix release includes a new feature which allows add-on administrators to set the log level of the Version Sync audit log.

This release fixes a the confusing message displayed on the project management screen when the Version or Component synchronisation has been disabled on the add-on settings page. It now contains a more clear text and a direct link to the settings page. Additionally, this release fixes the incorrect add-on configuration button link in the Universal Plugin Manager.

This release includes a long overdue update of the Version & Component sync add-on. It combines the previously separate Version Sync and Component Sync add-ons in a single product which is essential to Jira project administrators.

In addition to merging the two add-ons, the release contains the following fixes & improvements:

• Compatibility with Jira Data Center
• Major bug fixes, including the ability to rename versions / components
• Updated Component Sync to match features that already existed in Version Sync
• Updated UI to match the Atlassian design guidelines
• Improved performance for large Jira instances with multiple project link configurations
• Created 500+ unit and UI tests for improved quality assurance
• Created EULA, Service Level Agreement and support policy for improved customer experience