The Forge edition of Calculated fields (JBCF) is an update of this app’s Marketplace listing: an installed Connect app updates to Forge in place, with Update in Manage apps. You do not buy the app again. Atlassian ends support for Connect apps on 31 January 2027.
The full guide is in the Forge documentation: Migrate from JBCF Connect to JBCF Forge.
What happens to your fields
- Forge fields are new fields with new ids. The app does not create fields itself: a Jira administrator creates them by the checklist on the Migration from Connect tab of the Forge edition, then selects Run again, and the app links each one to its Connect settings.
- Values are not copied: the Forge edition recalculates them from issue history. Progress is shown on its Service Info tab.
- The app looks for the Connect settings by itself every hour, so nothing has to be exported by hand.
Download the settings file before you update
If the Forge edition does not find the Connect settings by itself, you move them with a file. Get the file while the Connect edition is still installed:
- In this app’s admin page, open the Calculated custom fields(JBCF) tab and select Download for Forge. Only a Jira administrator can download it; the file is
jbcf-forge-migration.json. - After the update, on Migration from Connect in the Forge edition, select Upload file from Connect and choose that file.
See If settings did not move automatically for what the upload reports.
Saved filters
Saved filters that use cf[id] of an old Connect field stop matching after the move. The Show filter audit report on the Migration from Connect tab suggests the new JQL for each filter. The four Is author of first / last comment assignee / reporter fields store true / false in Connect and Yes / No in Forge, so the suggestion changes = true to = "Yes" and = false to = "No". See Filters after the move.
Moving from Jira Server or Data Center instead? See Migration from Server/Data Center.

