Migrating tools from
Enterprise Edition to
TeamForge16.10
As you move onto CTF 16.10, you may want to know how the CollabNetEnterprise Edition (CEE) project information is brought
over to CollabNetTeamForge16.10 (CTF 16.10).
Migration Assumptions
As you move onto CTF 16.10, you may want to know the assumptions that were made while migrating CollabNetEnterprise Edition (CEE) project information to CollabNetTeamForge16.10 (CTF 16.10).
Mapping functionality between Enterprise Edition and TeamForge 16.10
Most of the tools and their functionality are similar between CEE and CTF 16.10. However, within each tool, some work-arounds might have been done to bring over the CEE project information and resources.
How is global data handled during migration?
Global (or "framework") data is validated for integrity, correctness and completeness after migration from Enterprise Edition (CEE) to TeamForge16.10 (CTF 16.10). Here are the detailed assumptions behind the validation process.
Migrating Issue Tracker
When Issue Tracker data is migrated from CollabNet Enterprise Edition to TeamForge, you will see these changes.
User permissions on a CEE and CTF 16.10 site
Each permission a user can have on a CollabNet Enterprise Edition site has an equivalent permission on a CollabNetTeamForge site, with a few exceptions.