Here's a list of few noteworthy issues fixed in TeamForge
8.1.
RBAC
An
issue with the Grant Automatically on Request permission
option while creating a new project from a project template has been
fixed.
Discussions
An
issue
that prevented
creation
of
new posts
with
multiple email recipients has been fixed.
Indexing
Re-indexing
of all the versions of a document is not triggered for updates such as status change
or lock/unlock. This reduces the load on the indexer, especially on sites with
intensive document usage.
Performance
- Project
Home page has been
optimized
for better performance.
- Performance
improvement has been made to ensure faster loading of tracker pages with huge
number of artifacts.
- Dynamic
tree
structures
(Planning Folders, Teams, Documents and so on)
have
been
improved
for better performance.
Installer
- An issue
that
occurred with the dynamic IP environment
has been fixed.
- The
collabnet startup script has been optimized to handle interim requests
better.
- While recreating the runtime,
the installed add-ons
runtime
are now executed in a specific order.
Security
- Security
vulnerabilities around account harvesting have been fixed.
- Tomcat
security
vulnerability
has
been fixed
by
upgrading Apache Tomcat
to
8.0.22 in TeamForge 8.1.
- Specific security requirement
needs have been tested with TeamForge and add-ons.
SCM
- An exception that occurred at
times while browsing an SVN repository in ViewVC has been fixed.
- In the case of External
Authentication (LDAP), the synchronization between the user password and the
database now happens only if CVS is enabled.
Tracker
- On
creating a drop-down list, all the artifacts were loaded resulting in an Out of
Memory error. This has been fixed.
- The
issue with removing users from the user type flex field
has been fixed.
Event handler
The issue with the custom event handler not capturing
artifact
dependent
events has been fixed.
UI/UEX
The Home and Menu bars now appear correctly in ViewVC when SCM is on a different
server.
Error handling
An Out of Memory error occurred
while
handling
huge
number of BCC
recipients.
This has been fixed.
Reports
- A recursive looping issue with the CLI report scripts that
resulted in out of memory situations is now fixed.