Each permission a user can have in a CollabNet Enterprise Edition project has an
equivalent permission in a CollabNetTeamForge project, with a few
exceptions.
TeamForge 16.3 Permissions for Announcements
The news application in TeamForge does not have its own permissions. Users' ability to view project news depends on their level of access to the project itself. The permissions for the CollabNetEnterprise Edition Announcements tool are mapped to the closest possible project permissions in the TeamForge.
TeamForge 16.3 Permissions for Issue Tracker/Project Tracker CollabNetEnterprise Edition uses the same set of permissions for Issue Tracker and Project Tracker. There are some permissions for individual tools too. The CollabNetEnterprise Edition project tracker permissions are appropriately transferred to Project Tracker (integrated application in TeamForge16.3) or Issue Tracker, based on the tool that the project uses or the inherited tool permissions in child projects or the permissions that are a part of a global or site-wide role.
TeamForge 16.3 Permissions for Project Dashboard and Tasks
Permissions are mapped to TeamForge16.3's Tasks application. As there are several gaps between CollabNetEnterprise Edition and TeamForge16.3's Task tracking application, it is difficult to come up with an exact role mapping. The role played by the user having the permission is used as the baseline for the mapping.
TeamForge 16.3 Permissions for Projects TeamForge16.3 does not have fine level controls with regard to project functions as a project-level role. However, project operations are a part of a site-wide role. Hence the mapping is done to site-wide roles, except for project administrator.
TeamForge 16.3 Permissions for Role TeamForge16.3 does not have fine level controls with regard to roles functions at project-level. However, role operations are a part of a site-wide role. Hence the mapping is done only in the case of domain roles. For project level roles, project administrator has these capabilities.
TeamForge 16.3 Permissions for Version Control
Permissions are mapped to TeamForge16.3's Source Code application. Resource pattern association with the permissions are not handled and will appear in the exception report. The "Change in Behavior" column ignores the regex aspect.
TeamForge 16.3 Permissions for Wiki
Wiki will come in as an integrated application post TeamForge16.3. At that time, these permissions will be transferred to the integrated application. As of now, the permissions are mapped to TeamForge16.3 wiki permissions and hence users will get the same permission in TeamForge16.3's wiki.