The following noteworthy issues, including any workarounds we may have, are known to exist in the TeamForge 16.10 release.
- Trackers and Artifacts
-
You cannot edit the "Assigned To" field of an artifact if the previous assignee's full name has an apostrophe (Example: McDonald's) in it. This is a known issue in 16.10.
As a workaround, remove the apostrophe from the previous assignee's full name. Now you are able to edit the 'Assigned To' field to re-assign the artifact to any other user. This issue will be resolved in the subsequent release.
- The following error message shows up when users that are granted
access permission to individual trackers in a project (instead of
the "All Trackers" permission) try to inline-edit artifacts from a
planning folder.
You do not have permission to edit this page
To work around this issue, such users can edit artifacts via mass update or edit artifacts one-by-one.
- When you update an artifact's title or description, the Side by Side
view of the change history shown in the Comments section of the View
Artifact page displays the Old and New values one after the other
instead of showing them side by side.
-
The search icon on the AssignedTo field has an 'X' symbol overlapping it. This issue can only be seen in IE. This will be fixed in TeamForge 17.1.
-
- Activity Stream
In a distributed TeamForge setup where TeamForge and EventQ run on separate servers, you must make sure that there are no time-synchronization issues. If you see the following error message when you click the "Activity Stream" icon, check if the servers are in sync with network's time.
Please contact your system Administrator. Something went wrong.
- TeamForge Binary
During TeamForge installation/upgrade, the TeamForge Binary service fails to start when you deploy services (/opt/collabnet/teamforge/bin/teamforge provision) and fails to initialize subsequently. However, it starts up and initializes when you run post-install.py.
- Password Control Kit
An issue with TeamForge's Password Control Kit (see PASSWORD_CONTROL_EFFECTIVE_DATE) prevents password expiry warning emails from being sent as configured to users whose passwords are due for renewal.
- Black Duck Code Sight
While the initial startup times out for the Black Duck Code Sight service, it is found to startup automatically with a few minutes delay. The following error message, if seen, can safely be ignored: Service 'bdcs' failed to start up within 240 seconds.
- License Model
- Project template creation fails when a user with "Tracker" license creates a project template from projects with moderated discussion forums.
- The Binaries tool shows up (which it should not) for users with "Trackers" or "Collaboration" license. However, it is not accessible for users with "Tracker" or "Collaboration" license (a "Permission Denied" error message is shown).
- A "Jump to ID" search for an object that's not covered by the scope of the license owned by a user is not throwing the "Permission Denied" error as expected. A "TeamForge system error..." is thrown instead.