The following noteworthy issues, including any workarounds we may have, are known to exist in the TeamForge 18.2 release. These issues would be resolved in an upcoming release.
  • A saved tracker search, if consists of flex fields that are later deleted from the tracker, returned all the tracker artifacts when executed. It should return “No results found” instead.
  • Users with the SCM license, when added to the list of users monitoring a discussion, are not shown in the users monitoring list.
  • A saved tracker search, if consists of tags that are modified or deleted, shows no message regarding the tags that are either updated or deleted.
  • If SOAP services are not completely up and running during service startup, binary initialization fails during teamforge provision. As a workaround, reinitialize the binary service:

    teamforge reinitialize -s binary
  • When creating the Collabnet Agile 2.0 project template in TeamForge 18.2 on RHEL/CentOS 6.x, the template gets created with no data in it. In addition, the template is not listed in the Project Templates drop-down list. As this is not yet fixed for RHEL/CentOS 6.x, you may consider upgrading to RHEL/CentOS 7.x.

  • The LOG_QUERY_TIME_THRESHOLD token settings, if configured, are not applied in TeamForge 18.2. This will be fixed in the upcoming TeamForge release.
  • CLI reports are not showing up on sites with Oracle database.
Tags for this page: release_notes