A request for JIRA Data Center support was raised in the earlier release. This release provides Data Center (JIRA 6and JIRA 7)Support.
While synchronizing fields that contain backslash characters, AccuSync inserts double the character into the AccuWork issue. The issue has been resolved in the current release.
AccuSync version upgrade from version 2015.1 to version 2016.1 resulted into the following problems:
All these problems have been collectively solved, while addressing this issue in the current release.
When there is a multi line description in JIRA, it gets displayed in AccuWork with a blank line above the third line. This issue has been resolved in the current release, AccuSync now handles line breaks correctly.
he alphabet “u” with the umlaut (<alt>+0225 or <alt>+0220) is not synchronizing into AccuWork correctly. For example, the word "büg" appears as "b\u00FCg" in AccuWork. This issue has been resolved in the current release.
The tabs Hide Change Package and Change Package History can now be hidden until an AccuSync synchronization is performed.
After starting up the new synchronization, the issues created in the new depot from the synchronization have the JIRA KEY and JIRA LINK fields pointing to the correct new JIRA project in this release, instead of the old project as was the case in the earlier release.
After upgrading synchronization pattern, the old issues are no longer getting synchronized in this release.
JIRA issues are not synchronizing with AccuSync when two instances of JIRA run on the same server. This issue has been resolved in this release.
AccuSync handles JIRA custom fields correctly in this release.
The custom fields AccuWork Key, Link, CPK and CPK history would not get on a fresh installation of JIRA. This issue has been resolved in the current release.