Here's a list of few noteworthy issues fixed in TeamForge 18.1.
  • Artifact comments that are two or more lines long were not wrapped properly; instead, a horizontal scrollbar was added. This is fixed.
  • Fixed the TeamForge system error that occured when you clone an artifact (that has no attachments) with the Include Attachment(s) check box selected.
  • Fixed an issue that prevented wiki pages with JPEG/JPG or PNG images from being exported as PDF.
  • Fixed an issue with Oracle CLOB data handling that prevented the TrackerIncrementalJob from running post TeamForge upgrade.
  • Fixed an issue with the parent-child field value mapping (using which a child field’s value is auto-selected based on the parent field’s value) when a pair of parent-child fields are made mandatory by a tracker workflow.
  • An issue that prevented sorting the list by the Apply Date column on the Users Awaiting Approval page has been fixed.
  • When you clone an artifact with the Sum effort from children field selected, the newly created artifact inherits the effort value from the artifact that it was cloned from. This is fixed.
  • Fixed an issue that resets the user-selected parent field’s value to None when the user tries to save the artifact without filling in one or more mandatory fields.
  • Fixed an issue with the artifact dependency table, which was not updated when you change the parent of a child artifact.
  • Document icons were not bound with the documents when you sort documents by document id or document name, which is now fixed.
  • Using certain keywords such as tracker, docman, planning, frs, taskmgr, scm, wiki, and discussion in planning folder names (for example, “Metric tracker”) caused an error. In addition, the planning folder ID was not shown in the Jump to ID field. This is fixed.
  • Changes made to the subject element of the HTML artifact update email notification template (/branding/templates/mail/artifact_monitoring_template_html.vm) were ignored. This is fixed.
  • A role with Tracker View permission was working inconsistently. Such a role, when assigned to an individual user and a user group (which the user is a member of), lets the user view the list of teams in a project and prevents the user from viewing the list of teams in a project respectively. This is fixed.
  • A user that is monitoring applications such as (Trackers, Documents, Source Code, Discussions, File Releases and Wiki) continues to monitor objects even after the user was selectively removed from monitoring one of the objects such as an artifact or a document. This is fixed.
  • When a document is added to or deleted from a restricted folder, notification emails were sent to users that do not have view permission to the restricted document folder, which is now fixed.
  • When you open a document (to view its details) from a multi-page document list and when you click Return on the Document Details page, you are taken to the first page of the documents list instead of the document list page from where you opened the document earlier. This is fixed.
  • Creating global project roles and assigning permission to these roles had a few performance issues, which are now fixed.
  • Removed the legacy CSRF token from TeamForge.
  • Fixed an issue that allowed users to upload restricted file types on the Project Home page.
  • Fixed the 403 (Forbidden) error that occured when a user tries to log on to TeamForge with valid credentials immediately after a failed login attempt (due to incorrect password).
  • When user accounts are created by the TeamForge site administrator, users may get an email with a link to set their password. The link, by default, expires in 72 hours. Using an expired link was taking the user to a blank page instead of letting the user use the Forgot Password functionality, which is now fixed.
  • Filtering columns with keywords containing leading and/or trailing spaces showed no results, which is now fixed.
  • Custom web page (configured using the Publishing repository) was not shown even if the Show custom web page option (under Project Admin > Project Settings) was selected for the project. Instead, the default project home page was shown. This is now fixed.
  • If you were using service-specific FQDN for Subversion, post installation of TeamForge, you had to delete the /opt/collabnet/teamforge/var/home/apache/.subversion directory and login once using the Subversion-specific FQDN to prevent authentication requests from Review Board from failing. This is fixed.
Tags for this page: release_notes