Known issues in CollabNet TeamForge

The following known issues in CollabNet TeamForge 6.1.1 will be addressed in upcoming patches or releases. Some of them have workarounds.

• For an Integrated Application variable, when you specify an ID in upper case, for example, an id_pattern BCA[0-9]+, there is a problem because TeamForge converts the ID to lower case.

  Workaround: Specify any case for id_pattern. For the example, this is [bB][cC][aA][0-9]+.

• Global search and discussion search display posts awaiting authorization for users with the “Discussion – View" permission.
• For MS Excel documents created using MS Office 2007 or 2010 (in xlsx format), wikis fail to convert the content to HTML. The error "Unable to recognize OLE stream" occurs when the content is rendered in a wiki.

  Workaround: Save MS Excel documents created using Office 2007 or Office 2010 with the file type "Excel 97 -2003 workbook" to fix the problem.

• JavaScript is not supported in news posts.
• A Project Tracker user with Assignable permission should also have the Query permission to be able to "Refresh" the list of users in a pop-up for a user attribute.
• In Project Tracker’s user picker pop-ups, any available user group's name always appears as "$user.Name".
• While installing TeamForge on Oracle or Postgres, you might see a warning message such as "Connection problem occurred with Postgres...". If you see this message while recreating the runtime, you can safely ignore it.
• When you run the fix-data_permissions.sh script on a BTF site (where the SAAS_ENABLED token is set to false), a "unary operator expected" error appears.

  Workaround: In BTF mode, run the script with options: ./fix_data_permissions.sh 5 5

  When the script runs, its output indicates that the permissions of bdb_log, bdb_env and bdb_data directories - which are not yet present in the system - are being fixed.

  Also, the script displays the message "cannot access `/svnroot/*/*': No such file or directory" in these situations:

  • On a fresh box, if the site was started before running the script
  • On a migrated box, when the svnroot directory has no repository directories
• When you install or upgrade to TeamForge 6.1.1 without replacing the HOST_localhost token (in site-options.conf) with the hostname, ViewVC pages for Subversion and CVS repositories created after the site is up, are rendered with a CSS error.
• Tracker search does not always return consistent results when you click the pagination link or change the number of items displayed per page.
• On all installs and upgrades, dedicated or advanced, it is mandatory to include the token "SCM_DEFAULT_SHARED_SECRET" in the site-options.conf file of the primary TeamForge server and give it a value of 16-24 characters for. You need to use that same key in the external SCM integration server also.