Moving from the Connect app


What changes when you move to Forge

Timer Field for Jira Cloud on Forge replaces the Connect app of the same name on the Atlassian Marketplace. The Forge app declares the Connect app key com.jibrok.jira.plugins.timer-field, so a site with the Connect app is offered the upgrade to the Forge version as a Marketplace update on the same site. The Jira Cloud Migration Assistant (JCMA) is not involved.

What What happens
Settings The settings that the Connect app saved for the move are imported once, automatically, when the admin page of the Forge app is opened for the first time.
Custom fields Jira creates new custom fields for the Forge app. The old Connect fields keep their data but are no longer updated, and their IDs are different.
Saved filters, JQL, dashboard gadgets They keep pointing at the old Connect fields and are updated by hand. The migration audit lists them.
Field values Not copied. The Forge app calculates them once its fields are bound to the imported settings.

A setting that already exists in the Forge app with the same name is never overwritten.

How the automatic import works

  • The Connect app saves the settings on a schedule. While it is installed, the Connect app saves its settings for the move to Forge every few minutes - on a schedule, not at the moment of the update.
  • The Forge app imports them once. The import runs automatically, a single time, when a Jira administrator opens the admin page of the Forge app for the first time after the update. If it cannot run at that moment, it starts automatically the next time the admin page is opened.
  • Nothing is overwritten. A setting that already exists with the same name is skipped, both by the automatic import and by every later one.
  • Import again in Health Check > Settings from Connect repeats the import on demand - see Step 1.
  • Upload file from Connect is the same import, taken from a file instead of the settings the Connect app saved - see Step 2.

Moving from Jira Data Center instead? That route goes through the Time in Status Forge listing, not through Timer Field.


The order of the move

  1. Before the update, download the settings file in the Connect app (see Before you update). After the update the admin page of the Connect app is gone.
  2. Update the app to the Forge version on the Marketplace.
  3. Open the admin page of the Forge app - the import starts - and check Health Check > Settings from Connect (Step 1).
  4. If nothing was imported, upload the file (Step 2).
  5. Create the Forge fields, bind them to the imported settings and recalculate (Step 3). In team-managed projects, add each new field to the project.
  6. Update saved filters and dashboards (Step 4).

Before you update: download the settings file

The Download for Forge button is on the Migration to Forge tab of the admin page of the Connect app. The tab appears together with the banner Forge edition is available, and only a Jira administrator sees it. Download the file before you click Update: after the update the admin page of the Connect app no longer exists. Keep the file in case the automatic import finds nothing (Step 2).


What moves and what does not

Moves: work calendars, Custom Events, Timer field settings and Timer web panels.

  • Each calendar keeps its name, time zone and working schedule. If a calendar could not be imported, the settings that used it count with the default calendar, and Not carried over lists it.
  • Timer goals keep their time exactly: a goal of 8h in the Connect app is 8h in the Forge app, and a short goal such as 15m is imported too. A goal that used a calendar in the Connect app uses the same calendar in the Forge app.
  • Custom events appear on the Custom Events tab, and the events of the moved settings and panels use them.
  • A Connect web panel that showed N fields becomes N Forge panels, one per setting.
  • Field values are not copied: the Forge app calculates them after you create and bind its fields (Step 3).

Does not move - each case is listed under Not carried over in Settings from Connect:

  • the Connect events updated, reopened and moved;
  • an additional goal without a JQL condition - the Forge app applies additional goals only by JQL, and a goal for all issues is the Default goal;
  • additional goals over 10;
  • the Connect option recalculateHistory = false;
  • display modes with the icon on the left;
  • a setting that had no field contexts in the Connect app.

Open such settings in the Forge app and complete them by hand.


Step 1: Check the settings that came from Connect

Open the admin page of Timer Field (Jira Settings ⚙ → Apps → Manage apps → Timer Field → Configure). The first opening starts the import. Then open Health Check and scroll to Settings from Connect at the bottom of the tab.

The block says what the app found:

Message Meaning
Connect settings were found and have not been imported yet. The import has not run yet - it starts the next time the admin page is opened.
Settings from Connect were imported. The import is done. The line below gives the result: Imported on …: N created, N already existed, N failed.
No settings from the Connect app were found. There is nothing to import automatically - for example, the Connect app was already removed. Use a file, see Step 2.
Jira did not answer: the Connect settings could not be read. Try again later. A temporary error. Open the tab again later.
The Connect settings are incomplete or in an unknown format. The Connect app rewrites its settings every few minutes - try again later.
The app is not allowed to read the settings saved by the Connect app. The automatic import cannot run. Take the settings from a file, see Step 2.

Not carried over lists, per setting, what the Forge app could not take over and why, with the columns Section, Item and What was not carried over. Open these settings in the Forge app and complete them by hand.

Import again repeats the import. Settings that already exist with the same name are skipped, so repeating the import does not create duplicates.

What the import brings over and what it leaves out - see What moves and what does not.


Step 2: Upload the settings from a file, if needed

When Settings from Connect says No settings from the Connect app were found, or when our support sends you a file, take the settings from a file:

  1. In the admin page of the Connect app, open the Migration to Forge tab, click Download for Forge and save the file - or take the file from our support. If the Connect app is already updated, its admin page is gone - ask our support for the file.
  2. In the Forge app, open Health Check > Settings from Connect and click Upload file from Connect. Choose the file.
  3. The block shows the result in the same words as the automatic import: Imported on …: N created, N already existed, N failed.

The upload is the same import as the automatic one, with the same rules: settings that already exist with the same name are skipped. A file that is too large is refused with The file is too large.

A file is accepted only by the app it was made for: a file of another app is refused with This file is for another app. Download the file in the Connect edition of this app. A damaged or edited file is refused too - download it again. Uploading the same file again is safe: settings that already exist with the same name are skipped.


Step 3: Create the Forge fields and bind them

The Forge app gives no checklist of fields to create: you create the Forge fields and bind them yourself. Field values are not copied from the Connect fields.

  1. Create the Timer fields of the Forge app in Jira - see Create a Timer field.
  2. Bind each field context to an imported setting - see Field context configuration. Health Check lists the settings that wait for a field context; the ones from the upgrade are marked Came from the Connect version upgrade. You can also bind from Health Check: in the Action column choose a field and its free context and press Bind.
  3. In a team-managed project, add each new field to the project: Space settings > Fields > Add field. Until the field is added, Jira does not show it in that project: the issue view, the REST API, exports and Automation return no value and a strict JQL check reports that the field does not exist, even though the values are already written and a JQL search finds them. Values appear as soon as the field is added - no recalculation is needed. In a company-managed project the field must be on the project’s screens instead.
  4. Run a recalculation for the bound contexts on the Recalculation tab, so that existing issues get values.

Step 4: Update filters and dashboards

At the bottom of the Health Check tab, open Connect to Forge migration audit and click Run audit. The report lists:

  • Custom fields - the old Connect fields and their Forge counterparts, matched by name. A field without a counterpart has to be rebound by hand.
  • Saved filters - filters whose JQL mentions an app field by ID or by name, with a suggested JQL (Copy JQL). Jira lets only the filter owner edit a filter, so hand the suggestion to the owner shown in the table. Only filters shared with the app are listed: private filters of other users are invisible to any app and have to be checked by their owners.
  • Dashboard gadgets - gadgets of the Connect app. They disappear with it and cannot be converted: remove them and add the Forge equivalent to the same dashboard.

Then update the filters and re-create the gadgets. The audit only reads: it never edits a filter, a dashboard or a field.