The following issues, including any workarounds we may have, are known to exist in the TeamForge 8.0 release.
TeamForge reports have new URLs
TeamForge 8.0 has a completely revamped reporting framework. The TeamForge reports such as the Project Activity and Task & Tracker reports have new URLs. You cannot access these reports through bookmarks that were created in TeamForge 7.2 or in earlier versions.
Average Age report is distorted with the high volume of data in the Datamart
The Average Age report may not work as expected when there is a huge volume of data in the Datamart. This issue is observed when the user tries to preview while configuring the report. The workaround is to increase the value for ADHOC_QUERY_CONNECTION_TIMEOUT.
Please note that there is no universal number to use because the timeout is largely depending on the amount of data that the selected tracker has.
Cross-project life cycle metrics reporting in TeamForge 8.0
As the new reporting framework is expected to evolve over the next few releases, unlike TeamForge 7.2 or earlier versions, TeamForge 8.0 and later have the life cycle metric reports feature (that lets you create and add cross-project life cycle metric charts to project pages) deprecated and turned off by default. While the new reporting framework makes reporting effortless, expect it to cater only to intra-project reporting needs at the moment. If you still want cross-project life cycle metrics reporting in TeamForge 8.0, you must set this REPORTS_ENABLE_LIFECYCLE_METRICS token to true. See REPORTS_ENABLE_LIFECYCLE_METRICS for more information.
CLI reports for 32-bit package with SELinux
There exists a known issue with the use of CLI reports in 32-bit environments with SELinux which will be fixed in the forthcoming patch release.
CLI branding support for RHEL 6 with SELinux
There is an issue with adding or modifying CLI reports via the branding repository on RHEL 6 with SELinux setup. This issue will be fixed in the forthcoming patch release.
New CLI package support for SUSE
New CLI package is not supported in SUSE.
An issue with the Tracker report "date range picker" widget
On sites spread across multiple time zones, the Tracker report date range picker has an issue due to which the query that generates the Tracker report, instead of using the user-selected "From" and "To" dates, uses different "From" and "To" dates. This results in the Tracker report being marginally inaccurate.
Discussions
The soap call, getForumList2 is not retrieving moderators and trusted users of moderated discussions.
You cannot browse Git repositories if you have Git on a separate server with SSL turned off, a 404 error message shows up.