Issues resolved in TeamForge 17.8

Here's a list of few noteworthy issues fixed in TeamForge 17.8.

• EventQ pipeline permissions (PIPELINE CREATE, PIPELINE READ, and so on) are now assigned to the Founder Project Admin role on projects created and approved by a non-admin user and a Site Administrator respectively.
• The Attach Another File button is now shown only after you have attached one file at the least.
• Fixed an issue with the Admin > User Group page. You can now create, filter and delete users as usual without any issues.
• The Any option of the Reported in Release(s) multi-select field, which always remain selected when you create a Tracker Report, can now be cleared without any issues.
• With tracker workflow, when a field is marked as a Required Field for one of the status transitions, users were not able to change to other statuses as well (that have no status transition rules) in the Planning Board view. This is now fixed.
• The Last Edited By and Last Edited On fields of the Tracker Settings page were not updated properly when tracker and document workflows were modified. This is now fixed.
• Fixed a formatting issue to properly display the tooltip, if configured for certain tracker fields.
• Fixed an issue with permission checks when you add users to monitor an object. Both the TeamForge Web application and SOAP APIs now function the same way.
• XSS based security vulnerabilities found across the application are fixed.
• The Actual Effort field, if disabled for a tracker, is no longer included in artifact update notification emails.
• Toeing the line of moveArtifact() and moveRepository() APIs, TeamForge Web application too checks if a user has “Delete” permission on the source "Tracker" and "Source Code" components when you cut/paste artifacts and repositories respectively.
• The Planning Folder Burndown chart shows the correct Velocity Trend line for the artifacts with P1 priority and "Actual Efforts" values.
• The connection issue between TeamForge and EventQ (RabbitMQ) that blocked updates from being sent to the Activity Stream has been fixed.
• Fixed the issue that prevented users from being added to a Wiki page’s monitoring list.
• Fixed an issue with the TeamForge Password Control Kit (PCK). Users are no longer deleted without warning emails.
• A proper success message is now being displayed when you click the Monitor and Stop Monitoring buttons on the View Artifact page.
• Consistent with the moveArtifact API, you must have tracker view, submit, edit and delete permissions to move (cut and paste) artifacts between trackers.