Known Issues

This section describes known issues in AccuSync:

Install after uninstall disables AccuSync Server service

If a user runs uninstall for an existing version of AccuSync and then installs AccuSync again, the AccuSync Server service does not start automatically and cannot be started manually. If you accidentally run uninstall, either delete or rename your AccuSync directory and then re-install AccuSync as a new installation.

Setting up connection to ClearQuest is showing warning message on AccuSync

While connecting to ClearQuest, a message is displayed Initialization of CLEARQUEST connection failed. Click OK to proceed.

Old issues in JIRA refer to old host name in AccuWorkKey and AccuWorkIssueLink fields

Old issues created in JIRA retain old Host Name. Even after changing the host name, old Issues in JIRA refer to old host name in AccuWorkKey and AccuWorkIssueLink fields, but the synchronization of the issue occurs in the new server. Issues created after changing the host name do not have any issue identity. So the new hostname do not update in JIRA.

JIRA issues before changing hostname will still point to old Host Name in AccuWork Key and AccuWorkIssueLink.

AccuSync.pdf first page shows rectangular with patches

Due to document template issue two unnecessary small white bars are visible on the cover page of the AccuSync .pdf file, impacting the look to a certain extent.

QC string is shown in AccuSync console & Logs instead it should be shown as ALM

The entire code base reflects the old name QC, whereas the application has a new name HP ALM.

Comment gets appended every time for AccuRev to JIRA issue synchronization, though not updated always

Customer might experience that the comment field gets appended every time a synchronization takes place between AccuRev and JIRA, even though no changes are made in the Comment field, in a very specific scenario.