If you are upgrading from TeamTime Connect (versions below 2.0.0) to TeamTime Forge (version 2.0.0 and higher), there are a few important differences to be aware of.
Why custom fields are not migrated
During the migration design, we initially planned to reuse the existing custom fields from the Connect version. However, this was not possible because the Connect and Forge versions use different calculation models.
In the Connect version, custom fields stored aggregated values from the container issue and repeated those values across child issues. These values were then mainly used for display at the level of the parent container.
In the Forge version, custom fields are structured differently: each issue stores and displays its own issue-related values. Because of this difference, the old Connect custom fields cannot be reused safely or accurately in Forge.
As a result, the Forge version introduces a new set of custom fields.
What this means for existing configurations
If you previously used TeamTime custom fields from the Connect version in any of the following places, they will need to be reconfigured after migration:
-
issue view
-
gadgets
-
filters
-
boards or dashboards
-
any other Jira configuration that referenced the old TeamTime fields
The old Connect fields are not used by the Forge version.
How the new Forge fields are populated
After migration, the new Forge custom fields are populated automatically when one of the following happens:
-
a user opens the TeamTime section in an issue
-
a report is created for issues included in the report scope
When this happens, TeamTime recalculates data for the relevant issue hierarchy and fills the new Forge fields and properties accordingly.
In the case of opening an issue, the recalculation is performed for the visible tree related to that issue, including parent and child issues as needed.
Important note for distributive mode
If a project uses distributive mode, an additional manual step is required after migration.
Until a container issue is selected for the project, TeamTime will show an error for that project and related functionality will not work correctly.
To complete the migration for distributive projects:
-
Open the project
-
Go to Project settings → Apps → TeamTime
-
Select the appropriate container issue
Once the container issue is configured, TeamTime will be able to recalculate and display data correctly.
Please note that recalculation may take some time for spaces with a lot of work items.
Summary
When migrating from Connect to Forge:
-
old TeamTime custom fields are not reused
-
Forge uses a new set of custom fields
-
existing Jira configurations that reference old TeamTime fields must be updated
-
new Forge fields are populated automatically during issue view or report generation
-
distributive projects require manual container issue selection after migration
This migration should be treated as a move to a new application model, rather than a direct continuation of the old Connect field structure.