- Released on: Jan 30, 2020
- GA Version: 20.0.321-602
The New Documents
Following the beta release of the new Documents List page in TeamForge 19.3, the TeamForge 20.0 release extends the user experience enhancements to the Documents List page. You have the option to switch between the old and new Documents List pages using the The New Documents toggle button at the top right corner of the Documents List page. For more information, see The Enhanced Documents List Page.
In addition to bug fixes and performance improvements, the following new features have been added to the GA release of the Documents List page.
Tags are another means of navigating/classifying your documents. While nothing has changed with the way you create or manage tags, TeamForge 20.0 unlocks the potential of tags as a means of navigation/classification and brings tags to the forefront in the form of a Tag Cloud.
A Tag Cloud is a group of tags added to the left navigation pane of the Documents List page. You can filter documents by tags.
- The Tag Cloud shows the most recently used tags.
- Click a tag to list all the documents that are associated with that tag.
- Click All Tags to view all the tags in the Documents List page.
- A tag in the tag cloud is visually distinguishable by its size and shade.
- The font size and shade of a tag indicates the number of documents associated with a tag.
- A bigger font size and a darker shade means that more number of documents are associated with the tag.
- Tags in the Tag Cloud are sorted and listed—the tags list starts with the most recently used tags followed by the least recently used ones.
Documents Search: @user and #status
The new Documents List page’s search function supports @user and #status simple search.
- Use the @user simple search to search for documents and document folders that are last edited by a specific user. Username predictions are shown as soon as you type
@followed by at least two characters of the username in the Search text box.
- Use the #status simple search to search for documents and document folders that are in a specific status. A list of available statuses to search for are shown as you type
#in the Search text box.
Here’s a list of other noteworthy features of the new Documents List page.
- The New Left Navigation Pane
- New Action Icons
- Concatenation of the Document Name and ID
- Documents List Page Shows Both Folders and Files
- Monitor and Unmonitor Document Folders and Documents
- Add New Subfolders/Rename Documents and Folders
- Move or Copy Documents and Document Folders
- Lazy-loading of Document Folders and Documents
- Default Document Column Configuration
- Search Document Folders and Documents
- Recent Documents
Here’s what’s new with the TeamForge Baselines.
- Add Log Entries for Baseline Database Migration Issues
- Use the BASELINE_LIQUIBASE_LOGLEVEL token to add log entries for baseline database migration issues. Set this token to
debugto log the issues, if any, during baseline database migration. For more information, see BASELINE_LIQUIBASE_LOGLEVEL.
Webhooks-based Event Broker (WEBR)
Here’s a list of what’s new with WEBR.
WEBR API Documentation
Here’s the TeamForge—WEBR 20.0 REST API Documentation.
Two new WEBR tokens have been added.
- HTTP Binding
- A new
site-options.conftoken, WEBR_HTTP_BINDNAME, lets you bind the WEBR service to http and to any other port of choice. For more information, see WEBR_HTTP_BINDNAME.
- Load Initial JS File
- A new
Here’s a list of what’s new with integrations.
Traceability Between TeamForge Requirements and TestLink Test Suites
Traceability between the TeamForge requirements tracker artifacts and TestLink test suites is now possible with the new
collabnet-testlink-1.0.4.jar. The Association Viewer shows the association between the requirements tracker artifact and TestLink test suite.
For more information, see TeamForge—TestLink Integration Using the TeamForge Webhooks-based Event Broker.
Unwanted Nexus Prilvileges
TeamForge—Nexus 3.0 integration inadvertently creates unwanted Nexus privileges (seven extra privileges) per repository. Such unwanted privileges tend to pile up as the repositories grow in number. A new, TeamForge—Nexus 3 integration plugin version 3.2.52 is now available to fix this issue. For more information, see Upgrade the TeamForge—Nexus 3 Integration Plugin.
Integrate Tools Using Post-submit Webhooks
Integrating heterogeneous applications like TeamForge and Jira is often challenging as these tools have dissimilar message formats. While TeamForge delivers its event messages in a pre-defined JSON format, other applications may need the messages in a different format. This is where TeamForge WEBR’s post-submit webhooks come in handy with its message transformation capabilities. TeamForge WEBR’s message transformation capability is the key to enable webhooks-based integrations between TeamForge and other tools such as Jira. For more information, see Integrate Tools Using Post-submit Webhooks.
Manage Obsolete Single-select and Multi-select Custom Field Values
It’s not uncommon for single-select and multi-select custom field values to become obsolete over time. However, deleting a widely-used custom field value from a single-select or multi-select custom tracker field can undesirably affect existing artifacts that use that value.
To work around such a scenario, you can now hide the (obsolete) values of the single-select and multi-select custom fields from being shown on Tracker artifacts, mass artifact updates, planning folders, Planning Board, Task board, and Kanban Board.
A new check box, Visible, is now available (in the Values section) for single-select and multi-select field values (Project Admin > Tracker Settings page). Selecting and clearing this check box (while editing the tracker settings) shows and hides the values respectively.
GitAgile™—Enterprise Version Control
TeamForge—Git Integration 20.0.4-2.15.18 is based on Gerrit version 2.15.18.
- UserFilter Removal
UserFilterremoval in TeamForge—Git integration is a direct outcome of the removal of the current_user predicate from the open source Gerrit. It is not possible to implement the
UserFilterwithout this predicate, as the quality gates would have no information about the current user any longer. For more information, see UserFilter Removal.
- While existing rules with UserFilter continue to work fine with TeamForge—Git Integration 20.0.4-2.15.18, you must update them post TeamForge 20.1 when UserFilter support would no longer be available.
- The New Submodules Tab
- A new tab, Submodules, has been added to the repository settings page. The Submodules tab lets you view a list of all the submodules used in the project.
- To view the Submodules tab, go to Project Home > Source Code, select a repository and then select Settings > Submodules.
- Expose Quality Gate Rules to All Repositories
- Unlike in the past when quality gate rules that are available to all the repositories were stored only on the server’s filesystem, quality gate rules are now stored in the
ref/meta/configbranch of the TF-Project repository.
- Unlike in the past when TeamForge administrators had to restart Gerrit, they can now simply modify the
ref/meta/configbranch and push the changes to the repository to have the quality gate rules available to all the repositories.
- Configure Advanced Repository Settings During Repository Creation/Import
- The new repository Create and Import tabs let you create or import repositories by simply giving the repo a name and selecting the destination server. However, a Settings toggle button ia also available, which if selected, shows you all the advanced repository settings—thereby letting you configure the advanced repository settings at the time of repository creation or import itself.
- This toggle button is not selected by default.
- Bug Fixes
- Rework the repostiory refresh logic to better handle potential LOCK FAILURE issues.
- Remove EventQ related Gerrit integration code from TeamForge—Git integration.
- For a list of open source Gerrit bug fixes, see Bug Fixes in Gerrit 2.15.18.
To prevent complex XML creation in datamart and to avert ETL failures, text flex field contents that are stored in the
artifact_flex_fields datamart table are converted to Base64 encoding and stored inside the XML tags. If you want to extract data from the
artifact_flex_fields table for analysis, you must convert the Base64 encoded content into human readable format. For more information, see Extract Base64-Encoded Text Flex Field Contents.
Install / Upgrade
- EventQ End of Life
- EventQ as a TeamForge service is no longer supported and is completely removed from TeamForge 20.0 (and later). There are a few things to consider in case you have been using EventQ and are upgrading to TeamForge 20.0. For more information, see EventQ End of Life.
yum install teamforge-baselineCommand
yum install teamforge-baselinecommand installs both the database and baseline packages. In a distributed installation/upgrade setup, you can use this command to install both the database and baseline packages in one go. However, in case you don’t install the TeamForge Baseline service, you must use the
yum install teamforge-databasecommand to install the database packages.
- New Site Option Tokens
- A new token,
HAPROXY_HTTP_REUSE_OPTION, has been added to the
site-options.conffile for HAProxy configuration. For more information, see HAPROXY_HTTP_REUSE_OPTION.
- Call Back URLs and WEBR/TeamForge Restart
- Call back URLs registered with WEBR are lost when you restart WEBR. This means, a TeamForge/Jboss restart must follow immediately after you stop or restart WEBR.
- No Support for TLS Protocol Versions 1.0 and 1.1
- In addition to security vulnerabilities, TLS protocol versions 1.0 and 1.1 do not support modern cryptographic algorithms. The software industry (including popular browsers such as Chrome, FireFox and so on) is set to deprecate the TLS protocol versions 1.0 and 1.1 by March 2020 and so is TeamForge. Customers are therefore advised to upgrade your sites to be able to negotiate with TLS 1.2 connections. Upgrade your clients to the latest version in case you face any SSL handshake issues while connecting to TeamForge.
- Generate Self-signed SSL Certificates with Subject Alternatine Name (SAN)
- It is typical of browser clients not to trust self-signed SSL certificates that do not have the Subject Alternatine Name (SAN) configuration. Configuring the PUBLIC_FQDN token in TeamForge is necessary to have SAN/DNS entries configured in the self-signed SSL certificate you generate.