Resolved issues

Artifact ID	Description
ccf423	A Null Pointer Exception was thrown when empty comments in Project Tracker artifacts were retrieved over the PT API. This is now fixed.
ccf424	Mapping rules define which artifacts get synchronized. If artifacts that should have been ignored contained attachments, there was a warning about the parent and the attachment was quarantined. This made it hard to differentiate between cases where the parent artifact was intentionally filtered out and cases where the parent artifact could not be created and was quarantined as well. The "onlyQuarantineAttachmentIfParentInHospital" property of the entity service has now been used to fix this problem. If set to true (false by default), attachments whose parent artifact cannot be found are only quarantined if the parent in is still in the hospital. In all other cases, there is a warning and the attachment is not quarantined.
ccf429	When a project mapping's conflict resolution priority was changed, but no changes were made to the repository ID, the graphical field mapping setting got changed to field mapping using an editor. This is now fixed.
ccf430	The CCF GUI switched to graphical data mapping even after you clicked Cancel when graphical editing failed. This is now fixed.
ccf433	Since CCF used the hyphen as a delimiter for its credentials, passwords could not contain a hyphen. Now, all characters after the first hyphen are treated as the password.
ccf434	If multiple TeamForge sessions timeout in a short period, it could lead to the TeamForge connector user's credentials being exposed in log files and hospital entries. While this is not a problem with CCF's current security model, it has been fixed in order to support remote administration with reduced permissions.

ccf423

A Null Pointer Exception was thrown when empty comments in Project Tracker artifacts were retrieved over the PT API. This is now fixed.

ccf424

Mapping rules define which artifacts get synchronized. If artifacts that should have been ignored contained attachments, there was a warning about the parent and the attachment was quarantined. This made it hard to differentiate between cases where the parent artifact was intentionally filtered out and cases where the parent artifact could not be created and was quarantined as well. The "onlyQuarantineAttachmentIfParentInHospital" property of the entity service has now been used to fix this problem. If set to true (false by default), attachments whose parent artifact cannot be found are only quarantined if the parent in is still in the hospital. In all other cases, there is a warning and the attachment is not quarantined.

ccf429

When a project mapping's conflict resolution priority was changed, but no changes were made to the repository ID, the graphical field mapping setting got changed to field mapping using an editor. This is now fixed.

ccf430

The CCF GUI switched to graphical data mapping even after you clicked Cancel when graphical editing failed. This is now fixed.

ccf433

Since CCF used the hyphen as a delimiter for its credentials, passwords could not contain a hyphen. Now, all characters after the first hyphen are treated as the password.

ccf434

If multiple TeamForge sessions timeout in a short period, it could lead to the TeamForge connector user's credentials being exposed in log files and hospital entries. While this is not a problem with CCF's current security model, it has been fixed in order to support remote administration with reduced permissions.