Known issues in TeamForge 17.8

The following noteworthy issues, including any workarounds we may have, are known to exist in the TeamForge 17.8 release.

• A restricted file type, if entered with upper case characters in the Configure Application page (for example: ZIP,BAT,XSLX), is allowed to be attached in artifacts, which is a known bug. It is recommended to always use lower case while listing the restricted file types in the Configure Application page.
• When a user tries to filter documents in the List Documents page, the table filter function fails to show the filter keyword that's used to filter the list in the column header.
• Restricted file types, if attached to private discussion forum email posts, are prevented from being uploaded as expected. However, email notifications from the private discussion forum contains no information about the files that are prevented from being uploaded.
• When you update artifacts with file attachments and if the update operation fails for some reason (say you have not filled in a mandatory field), the attached list of files are not persisted when the user is returned to the View Artifact page.
• Post upgrade to TeamForge 17.8, even if the ETL Server is connected, the My Workspace > Admin > Projects > System Tools > Server Status page shows the status as "Unable to connect". You can safely ignore this.
• For certain time zone settings such as MST and EST, the Comments and Artifact Description sections show different time zones in the View Artifact page.
• The Tracker Search Results component (that links the results from saved tracker searches into your project page), instead of showing actual search results of the saved tracker search, shows all the available artifacts.
• The following warning message, which shows up during TeamForge install/upgrade (while installing CN-eventq rpm) can be safely ignored.

  Don't run Bundler as root. Bundler can ask for sudo if it is needed, and
  installing your bundle as root will break this application for all non-root
  users on this machine.
  ...
  ...
  Errno::ENOENT: No such file or directory - git
  ...
  ...

• The teamforge script's apply-selinux command is non-functional. Expect this to be fully functional with TeamForge 17.8 Update 1.