When migrating from Jira Server or Data Center to Jira Cloud, TeamTime for Cloud (Forge version 2.0.0 and higher) does not reuse TeamTime custom fields created by the Server/Data Center app.
Although the Cloud version also uses custom fields, it works differently: instead of relying on the old TeamTime fields, it calculates values again in its own Cloud fields.
What needs to be migrated
For TeamTime Cloud, it is enough that the standard Jira fields below are transferred correctly during migration:
-
Original Estimate
-
Time Tracking / logged time
The Cloud app uses these Jira values to recalculate its own data after installation.
How the Cloud app works after migration
After the app is installed in Jira Cloud, TeamTime recalculates data based on the migrated Jira issues and their standard time tracking fields. The recalculated values are then stored in the Cloud app’s own fields and properties.
In other words, the migration to Teamtime Cloud should be treated as a move to a new app version with its own calculation model, not as a direct reuse of the old Server/Data Center app data.
Important note for distributive mode
If a project uses distributive mode, then after moving to TeamTime Cloud (version 2.0.0 and higher) you must manually select the container work type for that project.
This step is required for distributive mode to work correctly in Cloud: unlike previous versions of the app, where Epic was the highest level possible, Cloud version (from 2.0.0 and higher) can use any issue type of any level as a container.
Cloud version compared to Server/Data Center
The Cloud version of TeamTime is significantly more advanced than the Server/Data Center version.
For example, the Cloud version includes functionality that is not available in the older Server/Data Center app, such as reports.
Because of this, some parts of the Cloud app work differently and require their own configuration after migration.