The TeamForge 20.1 release incorporates new features and enhancements that reinforce and expand the unique value of TeamForge. Read more to know what's new!

Release Information

  • Released on: May 6, 2020
  • GA Version: 20.1.502-740

Documents

Here’s a list of what’s new with the new Documents List page.

Delete Documents and Document Folders
You can either delete documents and folders one-by-one or select multiple documents and folders and delete them.
Contextual menu to delete an individual document or folder
Action menu at the top to delete multiple documents and folders

For more information, see Delete Documents and Document Folders.

Whole Word Search
The Documents List page’s search function supports whole word search for documents and document folders.
Just include the search keyword within double quotes to do a whole word search. Document and document folder title is searched for a match when you do a whole word search.
Whole word search (keywords within double quotes)
Advanced Search
Advanced documents search options

When you want to narrow down your search results with one or more documents you want, you would typically search with more than one of the advanced search parameters.

For more information, see Advanced Search.
Favorite Document Folders
In addition to documents, you can now mark document folders as favorites.
For more information, see Mark Documents and Document Folders as Favorites.
List of favorite documents and folders
The New Documents List Page Qualified for Oracle Database
The new Documents List page has been qualified to work on TeamForge sites that use the Oracle database.
Script to Fix Data Discrepancy Issues with Documents
If you have been using sigle-select, multi-select or Status flex fields in TeamForge Documents—and if you have inadvertently deleted one of the flex field values that was being used widely by existing documents—you will end up being unable to access the documents/document folders due to data discrepancy issues.
While TeamForge 20.1 has been fixed to prevent such deletions, you can run this script to fix such data discrepancy issues, if any, found with documents created in TeamForge 20.0 (or earlier).
For more information, see doc_update_fieldvalues.py.

You can enable SSO between TeamForge and TestLink. Once you enable SSO, you cannot log on to TestLink directly. TestLink becomes one of the site-wide linked applications in TeamForge and you must log on to TeamForge to access TestLink.

With SSO set up, the TeamForge Administrator and non-admin users, from a role-mapping perspective, are mapped by default to the TestLink Administrator and Leader roles in TestLink respectively.

With SSO enabled, you can access TestLink directly from the My Workspace > More TeamForge menu.

TestLink as a site-wide linked application

For more information, see SSO Between TeamForge and TestLink

TeamForge Baselines

Here’s a list of what’s new with TeamForge Baselines.

Delete Baselines
You must have the DELETE/VIEW BASELINE permission to delete Open and Rejected (meta status) baselines.
You can only delete baselines one-by-one from the View Baseline page.
Delete this baseline link

An email notification is sent to the user that created the baseline, the users that acted (update, review or reject) on the baseline and the users that monitor the baseline.

Users with the DELETE/VIEW BASELINE permission can:
  • View baselines
  • Search for baselines
  • Compare baselines
  • Delete Open and Rejected (meta status) baselines.

For more information, see Delete Baselines.

Hard-links Between Baselines and Configuration Items
Configuration items (tracker artifacts, documents, FRS, SCM repositories, and binary repositories), once included as part of a baseline, cannot be deleted.
However, with TeamForge 20.1 (and later), you can delete baselined documents and File Releases (FRS packages).
When documents and FRS are baselined, a hard-link is established between the baseline and the configuration items (documents and FRS), which lets you delete the documents and FRS packages without breaking the baselines that include them.
As hard-linking of baselines with documents and FRS is introduced in TeamForge 20.1, you cannot delete documents and FRS packages included as part of baselines created with TeamForge 20.0 or earlier.
In addition, you cannot delete a document or FRS from a project when it’s baselined. The following table illustrates how a document can or cannot be deleted, which is also true with FRS packages.
Project Document Name/Document ID Document Baselined? Delete Document?
proj1 D1/doc1 D1 in proj1 (with ID doc1) was baselined as part of baseline1 You cannot delete document D1 from proj1 as it’s part of baseline1.
proj2 (created from baseline1) D1/doc2 D1 in proj2 (with ID doc2) was not baselined You can delete D1 in proj2 as it’s not part of any baseline.
proj2 (created from baseline1) D1/doc2 D1 in proj2 (with ID doc2) is baselined as part of baseline2 You cannot delete D1 in proj2 as it’s part of baseline2

Last Status Change Date of Artifacts

A new optional column, Last Status Change, has been added to all the Tracker, Planning Folder and Team list views that shows the date when the status of artifacts were last changed.

When you create an artifact, the Last Status Change date is set to the date when you create the artifact. Any subsequent updates to the Status of the artifact updates the Last Status Change date as well.

You can add this column to your list view by configuring the columns as usual. You can also export this column when you export tracker artifacts.

A column that shows the date when the status last changed

In addition, the View Artifact page shows the date and time when the artifact’s status was last changed.

Last status change date and time on the View Artifact page

TeamForge SCM—Enterprise Version Control

Highlights of TeamForge—Git Integration 20.1.9-2.16.18.

For more information, see release notes of vanilla Gerrit version v2.16.18

Repository Consumers
A new tab, Consumed by, has been added that lists all the repositories that reference the given repository as a submodule.
Manage Submodules
You can now create and delete submodules that point to repositories on the same Gerrit integration through web UI directly from the Submodules tab.
Add a Submodule
Remove a Submodule
Submodules Tab Improvements
  • The Submodules tab has been moved out of the Settings tab to become a top level tab of Repository browser.
  • You can now view Submodules at various branches.
  • A branch selector has been added to the Submodules list view. This lets you view Submodules for any branch—not just for master branch.
  • Display the Submodules’ distance to HEAD—You can now view how far behind its HEAD is the commit that the Submodule is pointing to.
Improvements to the Internal Code Browser
  • Changing the quality gates xml file at refs/meta/config directory of TF-Projects updates all the affected repositories correspondingly.
  • Ability to delete the source branch after successful pull request merge as long as the source branch is not the default branch.
  • Improvements to the workspace widgets ‘Recent repositories’ and ‘Recent projects’.
  • Limit width of images in code review comment based on screen space.
  • Open code review comment image in a new tab.
  • Improve handling of rules from a custom rules.pl file in TeamForge UI.
  • Show first visible file in code review diff file selector.
  • Support code review line comments on a text block/range.
  • The tab selected on the repository Branches page is now a part of the URL.
UserFilter Removed from QualityGates
The UserFilter quality gate, which was deprecated in TeamForge 20.0, has been removed completely in TeamForge 20.1. For more information, see UserFilter Removal.

Tasks Removal

Tasks, as a component, is no longer supported and was completely removed from TeamForge 20.1 (and later). However, if you have been using Tasks, you can use the task-data-export.py script to export the Tasks data to Excel files, which you can later mass import into a new Tasks TeamForge tracker.

For more information, see task-data-export.py script.

TeamForge Tracker Associations Data in Datamart

TeamForge ETL jobs can extract transform and load the TeamForge tracker association data to the datamart for reporting purposes.

The tracker artifact association data is extracted from the TeamForge’s operational database and loaded into the datamart’s staging area. The staged data is then transformed to store association as a dimension in the datamart. A view of the dimension table (association_vw) is then created in de-normalized form for querying purposes.

For more information, see Tracker Associations Data in Datamart.

WEBR Orchestration

WEBR Orchestration is a webhook integration capability that lets you integrate tools using orchestration scripts.

The TeamForge Webhooks-based Event Broker (WEBR) provides a webhooks-based orchestration framework (for TOPIC type events) that lets you build integrations using an orchestration script, which otherwise would take creation of multiple subscriptions for the tools being integrated.

In addition, the WEBR orchestration framework lets you create orchestration endpoints that abstract the subscription URL, username, password (encrypted), header and so on. Once you create an endpoint you can use it in your orchestration scripts (with calls such as webGet, webPost, webPatch, webPut and webDelete).

For more information, see Integrate Tools Using WEBR Orchestration Scripts.

REST API Updates

See TeamForge API Change Log.

Install / Upgrade

Software Upgrades
TeamForge 20.1 runs on:
  • Wildfly 18.0.1
  • PostgreSQL 11.6
Review Board Deploy Fails—Remove the verify Parameter and Deploy Again
Review Board deployment fails on sites that use a self-signed certificate. Remove the verify=platform_default parameter from the [https] section of the /etc/python/cert-verification.cfg file and then try deploying the Review Board again.
PGSQL_LOG_MIN_DURATION site-options.conf token
The PGSQL_LOG_MIN_DURATION token specifies the maximum number of seconds after which queries are logged as long running queries to the log file.
The default value, which was -1 earlier, has been changed to 10 seconds (10s). Setting this token to 0 or a negative value can adversely impact the TeamForge application’s performance.
For more information, see PGSQL_LOG_MIN_DURATION.

[]:

[]:

Tags for this page: getting_started