These changes apply to AccuSync for JIRA only.
The AccuWork Issue, AccuWorkIssueLink, AccuWorkChangePackage, and AccuWorkChangePackageHistory fields required to synchronize AccuWork issues with JIRA were not created in JIRA for copied configurations. This problem has been corrected in the current release.
Support for JIRA 4.x is deprecated in AccuSync 2014.3 and will be dropped in a future release.
In previous releases, AccuSync used to add an ID to every component field name when it was downloaded from JIRA. A component named apptest in JIRA would be named apptest-10234 by AccuSync, for example. This problem has been corrected in the current release, and AccuSync now respects the JIRA component name.
In previous releases, the test connection credentials were hard-coded to admin/admin, which caused most JIRA test connections to throw an error. This problem has been corrected in the current release.
In previous releases, JIRA Fix Version and Affected Version fields were not synced with AccuWork. This problem has been corrected in the current release.
In previous releases, if JIRA was stopped and restarted, AccuSync would not log in automatically, causing subsequent synchronizations to fail. This problem has been corrected in the current release, and AccuSync now logs in after the underlying JIRA system has been stopped and restarted, allowing scheduled synchronizations to continue without manual intervention.