Known issues

The following issues are known to exist in CollabNet Tracker Connector for HP Quality Center 4.1 .

Artifact ID Description
ccf118 When a mass update is performed on CollabNet SourceForge Tracker artifacts, some artifact changes are not reflected in the corresponding Quality Center defects.
ccf188 If a Project Tracker artifact mapped to a Quality Center defect is moved , a second Quality Center defect is not created. Instead, the existing Quality Center defect is updated with a comment that the mapped artifact was moved.
ccf211 Fields of type "Text, Long", "Text,Short" and "Date" should not be shipped with empty values. Shipping them as empty values in new artifacts will result in exceptions thrown by the Project Tracker web service and the new artifact will not be created. In artifact updates, shipping an empty value will not alter the existing value. To work around this problem, the CCF administrator can either choose not to send the field to the Project Tracker writer, or send a default value. See this comment in the issue for XSLT templates showing the workarounds.
ccf214 For the Quality Center-to-Project Tracker direction, the connector does not ship a null value entered for the "Detected on Date" field.
ccf223 When a new user is added in Project Tracker without removing the user already mapped in Quality Center, the new user's details are not shipped to Quality Center.
ccf226 When multiple users are added to a Project Tracker artifact in a single transaction, the Project Tracker web service does not always return the last user assigned to a user field. Due to this, the connector ships one of the users involved in the transaction, but it is not possible to determine which one.
ccf228 When a Project Tracker artifact is created with an attachment, the PT_ID attribute is not shipped to Quality Center.
ccf229 The connector does not ship attachment descriptions in Project Tracker.
ccf233 When a field that is mandatory in Project Tracker or CollabNet SourceForge Tracker is not updated in a defect created in Quality Center, an attachment to that Quality Center defect is not shipped.
ccf235 Except for the "Assigned to" field, other multi-select user attributes in SourceForge tracker are mapped to single-select user fields in Quality Center. When a user is deleted in Quality Center, other existing users are also removed in the SourceForge tracker because removal of the user from the Quality Center user fields causes the the corresponding fields in the SourceForge tracker to be cleared of all users.
ccf248 If the last updated source artifact fails to ship to the target system, its transfer is repeated until the newer artifact becomes available.
ccf250 When the filename of an attachment contains special characters (for example, !, #, @ ) the connector may not ship the attachment correctly. In the Quality Center-to-Project Tracker direction, exceptions have sometimes been observed. In the Project Tracker-to-Quality Center direction, the attachment is shipped, but the filename may be incorrect.
ccf251 Editing comments in Quality Center defects is not supported by the connector. If an existing comment is edited, further comments may be rendered garbled or unreadable.
ccf268 When the CollabNet Connector Framework shuts down or restarts, Java Service Wrapper logs the error message "JVM exited unexpectedly". This message does not indicate any problem and is caused because the CCF disabled Service Wrapper's Shutdown Hooks to have better control over the termination phase.
ccf269 When a Project Tracker artifact having an attachment is copied, the connector creates a corresponding Quality Center defect, but does not ship the attachment.
ccf276 When comment and reason fields are provided in a Project Tracker artifact, the connector ships the comment with the user's username and the reason with the user's full name.
ccf278 The connector does not ship link attachments from Project Tracker to Quality Center.
ccf281 When multiple attachments with the same filename are shipped from Project Tracker-to-Quality Center, and then deleted in Project Tracker, they are not all deleted in Quality Center.
ccf282 If an initial import of Project Tracker artifacts is not completed, and the connector is started, it might miss the artifacts that are not yet created. This problem may also occur if dozens of artifacts are added in a short period of time and the connector shuts down at some point within that timeframe. Occasionally, the connector might re-read artifacts that have been already synchronized - this causes a warning message of the entity service.
ccf283 Uninstalling the connector removes the bin folder, and license.txt file and uninst.exe files. Other files remain.