What's New in TeamForge 18.1?

Release Information

• Released on: April 27, 2018
• GA Version: 18.1.446

Site Administration

Support for Multiple LDAP Servers

You can now configure multiple LDAP servers for LDAP authentication.

For more information, see Use LDAP for TeamForge User Authentication.

Enhancement to LDAP Configuration: Base Filter

A new search field, BASE FILTER, has been added to the LDAP configuration page in TeamForge to filter users belonging to a specific domain (organizational unit). For example: _(&(sAMAccountName={0})(objectCategory=account)(objectClass=user)_. For more information, see Use LDAP for TeamForge User Authentication.

One E-mail Address–Multiple User Accounts: Intermediate Login Page

In SAML and SAML+LDAP environments, if you have multiple user accounts mapped to one email address, you will be redirected to an intermediate login page before the third party IdP for authentication. In this intermediate login page, you can see the list of accounts associated with your email address.

For more information, see:

• Use SAML for TeamForge User Authentication
• Use Both SAML and LDAP for TeamForge User Authentication

Local Users

On sites with LDAP/SAML/SAML+LDAP integrations, site administrators can designate select users that do not have a SAML or LDAP account as local users. Local users can log on to TeamForge using just the TeamForge credentials, bypassing the SAML/LDAP/SAML+LDAP authentication realm.

When you select this ALLOW LOCAL USER site setting, the Create User and Edit User Information pages let site administrators to select the Local User check box while creating or editing user accounts.

Browser Caching in TeamForge

Unlike in the past where TeamForge data was not cached in the browser, you can now enable or disable caching in TeamForge for a better application performance. A new site-options token, BROWSER_NO_CACHE=false, has been added to the runtime-options.conf file. This means, browser caching is enabled by default. Set this token to true to turn off browser caching.

Project Administration

Set up Webhooks for Tracker Artifacts

You can now create webhooks to generate events whenever an artifact is created, updated, moved, cloned, and deleted. For more information, see Set up Webhooks for Tracker Artifacts.

Planning Folder Enhancements

• A New Planning Folder Status, Freeze

  You can now change the status of a planning folder to “Freeze”. A new status “Freeze” has been included in the Active/Inactive drop-down list in Project Admin > Planning Folder Settings page.

  

  

  For more information, see Manage Statuses for a Planning Folder.

• Filter Columns in Planning Folder View

  Starting from TeamForge 18.1, the Filter Columns function is implemented for all the system-defined fields within the Planning Folder view.

Performance Improvement–Project Template Creation in the Background

Project template creation can, at times, be time consuming. Not any more! With TeamForge 18.1 and later, once you initiate the project template creation process, it is handled as a backend process and you can move on with your other activities. Once the template is created, you would get an email notification and the template would get listed in the Project Templates page and in the Templates drop-down list for creating new projects.

Trackers

Strip Original Email Content from Reply Email

You must be aware that whenever you reply to an email that you receive after an artifact is updated, the original email content was also carried over along with your reply as a comment to the artifact in the Web UI. Now it is just your reply that is sent without the original email content. This enhances the user experience with the UI.

Edit Comments in Tracker Artifacts

You can now edit all the comments (only the most recent comment was editable earlier) that you have added to a tracker artifact. For more information, see Edit Your Comments section in Edit a Tracker Artifact.

Markdown Editor for Description and Comments of Tracker Artifacts

A new Markdown editor has been introduced for the Description and the Comments fields of tracker artifacts. Format your content with the wiki-like markdown syntax. TeamForge uses Showdown—a bidirectional Markdown to HTML to Markdown converter written in Javascript. For more information, see the official Showdown Documentation. Here’s an abridged version of the Markdown syntax documentation.

Enhancements to Search Tracker Page

When searching the tracker, you can now select one or more planning folders or teams from the respective fields on the Search Tracker page.

Documents

You can now associate TeamForge objects such as artifacts, documents, and so on with the desired version of a document. For more information, see the section Change the Active Document Version in Work with Your Documents.

Enhancements to HTML Notification Email Templates

Avatars are added for the Assigned To field in the HTML emails that you receive when a tracker artifact is created or updated and the Created By, Updated By and Locked By fields in the HTML emails that you receive when a document is created or updated.

Reports–Auto Healing Process for Handling Invalid XML Records

Earlier, if any corrupted XML records were found being stored during the XML to Non-XML conversion, the administrators need to manually correct them and store the corrected data into the new flex field bridge tables. To save this manual effort, an automated healing approach is now available, which replaces the invalid XML records with the correct data and makes them available for the next ETL run.

SCM/Git/Gerrit

Highlights of TeamForge-Git Integration 18.1.7-2.14.8

This section provides the highlights of TeamForge-Git Integration 18.1.7-2.14.8 released on Apr 23, 2018. For more information and bug fixes, see release notes of vanilla Gerrit version 2.14.8-1-g6ca0726997.

Enhancements to the Code Browser UI

• The coauthor name is also included as part of the author avatar and Authored by information on the changes list, whenever a change is done to the “Co-authored-by” footer text. More information can be seen in change details view.

  

  

• The @mentions logic used in the review comments and description fields has been improved to include users that are added as reviewers already, which earlier was not the case.

• Whenever a review is opened, the recommended reviewers list is shown immediately when the Add a New Reviewer field gets the focus.

• When a pull request merge was done on different commits of the same submodule on different branches, the merge contained the commits of an older version of the submodule.

• Better handling of customer repository review rules.

• Performance has been improved when viewing reviews and tags on repositories having large number of tags.

• Deleted or rewritten branches are sorted in descending order to bring the most recent branches to the top of the list.

Installer Enhancements

• A new token GERRIT_USER_EMAIL is added to the site-options.conf file to set the email account for sending Gerrit emails. This refers to all Gerrit servers specified in site-option.conf file or through cluster/server specific parameters. For example, the “clusterId/serverId” in [clusterId/serverId]:gerrit:user.email refers to the cluster or server that is used.

• HTTP requests in JavaMelody statistics are grouped to identify issues quickly.

• Supports Java 9.

Bug Fixes in TeamForge-Git Integration 18.1.7-2.14.8

• Fixed the security vulnerability found during the URL redirection to prevent phishing.

• Associations were not created when HTTP connection to EventQ was not established due a Java HTTP client issue. This is fixed.

• An error was thrown, if the destination branches in the Code Browser UI had the URL encoded character “+” in their pull requests. This is resolved.

• Fixed the issue in which the Delete Permanently button was not shown on the Deleted/Rewritten branches tab in the Code Browser UI for non-site administrators.

• A browsing error was thrown in the Code Browser UI for the file that was tagged incorrectly as LFS file. This is fixed.

• The maxRetries configuration parameter was ignored by TeamForge-Git integration resulting in indefinite updates to disconnected remote replica servers. This issue is fixed.

• Gerrit’s internal log rotation and compression feature is disabled as it is handled automatically by the TeamForge runtime environment.

• During an upgrade, TeamForge provision failed due to the issue found in the Gerrit database backup directory creation for subsequent provisions. This is fixed.

• An exception was thrown when a SSH key that is not supported by the ssh-keygen command in CentOS 6 was generated during the SSH key generation process. This is fixed.

Install/Upgrade

• The following are the latest software versions supported by TeamForge.

  • Java 9

    TeamForge 18.1 (and later) supports Java 9. As a result of changes to the logging framework in Java 9, the PrintGCDetails and PrintGCTimeStamps logging options are no longer supported. Remove these options from the following tokens before upgrading to TeamForge 18.1.

    • JBOSS_JAVA_OPTS
    • PHOENIX_JAVA_OPTS
    • INTEGRATION_JAVA_OPTS
    • ETL_JAVA_OPTS

    TeamForge provision fails on sites that use these options post upgrade to TeamForge 18.1.

  • Wildfly 11
  • Tomcat 8.0.50
• The following Review Board scripts have been moved to /opt/collabnet/teamforge/runtime/scripts/ directory:
  • backup-rb-data.py
  • restore-rb-data.py
  • domain_change_rb.py
  • reviewboard-psql-wrapper
  • svn-auth.py
  • svn_cache.sh
• Review Board installation and upgrade is no longer a separate process. Review Board is installed automatically when you install/upgrade TeamForge. In other words, you do not have to do a yum install CN-reviewboard separately.
  Note: TeamForge 18.1 has no support for having service-specific FQDN for Review Board.
• Tasks component is no longer supported from TeamForge 18.1 and later. For more information, see CollabNet’s Product End-of-Life Policy.

Back up and Restore TeamForge Data Using the teamforge.py Script

You can now use the teamforge.py scripts’s backup and restore commands to back up and restore TeamForge data. For more information, see Back up and Restore TeamForge Data Using the teamforge.py Script.

DLM End of Life

TeamForge 18.1 and later versions no longer support the DevOps Lifecycle Management (DLM) product. As a result, an error occurs when projects that include Applications and Environments are imported via Simbel. To work around this, delete the Applications and Environments via REST APIs (the Delete button in the user interface (Project Home > Project Admin > Application Settings) is disabled in TeamForge 18.1 and later) and then try importing the project again.