Atlassian ends support for Atlassian Connect apps on 31 January 2027. Every JiBrok Cloud app that runs on Connect today moves to Atlassian Forge before that date - except one, which is withdrawn. This page names the target platform, the quarter, and the administrator action for each app.
You are a Jira Cloud administrator with at least one JiBrok Connect app installed. Atlassian's Connect end-of-support announcement tells you the platform is going away; this page tells you what happens to your apps and when.
If every JiBrok app on your site is already a Forge build, there is nothing on this page for you to do. Use the Network Allowlist to tell the two builds apart: a Connect build serves its user interface from a *.jibrok.com host, a Forge build does not.
A published calendar date becomes a promise the moment a customer plans a change window around it. Release dates inside a quarter move for reasons that have nothing to do with the migration - a platform change, a security fix taking priority, an Atlassian API deprecation landing early. Committing to the quarter is a commitment we can keep, and it is precise enough to plan a change window against.
The only fixed date on this page is 31 January 2027, and it is not ours - it is Atlassian's end-of-support date for the Connect platform.
One row per JiBrok Connect app. If an app is not in this table, it is not a Connect app and it is not affected.
| App | Target platform | Forge build lands | What you do |
|---|---|---|---|
| Time in status | SLA | Timer | Stopwatch Connect build, time-in-status-cloud.jibrok.com |
Target: Time in Status (Forge), same Marketplace listing | Lands: Q3 2026 Available now |
You do: Export your configuration from the Connect Migration to Forge tab before updating, then update in Manage apps. Full protocol: Migration from Connect to Forge. |
Timer field / SLA for Jira Cloudtimer-cloud.jibrok.com |
Target: Forge build on the same listing, sharing its engine with Time in Status (Forge) | Lands: Q4 2026 Available now |
You do: Update the app in Manage apps. Health Check → Settings from Connect imports your settings - or, if none were found, takes them from a settings file. Create the Forge fields yourself, bind each to its imported setting (Health Check offers Bind next to each setting without a field and preselects the field when the pair is unambiguous), then run a recalculation on the Recalculation tab. Nothing to reinstall, nothing to re-license. Guide: Moving from the Connect app. |
Stopwatch for Jira Cloudstopwatch-cloud.jibrok.com |
Target: Forge build on the same listing, sharing its engine with Time in Status (Forge) | Lands: Q4 2026 Available now |
You do: Update the app in Manage apps. Health Check → Settings from Connect imports your settings - or, if none were found, takes them from a settings file. Create the Forge fields yourself, bind each to its imported setting (Health Check offers Bind next to each setting without a field and preselects the field when the pair is unambiguous), then run a recalculation on the Recalculation tab. Nothing to reinstall, nothing to re-license. Guide: Moving from the Connect app. |
Time between dates for Jira Cloudtime-between-dates-cloud.jibrok.com |
Target: Forge build on the same listing, sharing its engine with Time in Status (Forge) | Lands: Q4 2026 Available now |
You do: Update the app in Manage apps. Health Check → Settings from Connect imports your settings - or, if none were found, takes them from a settings file. Create the Forge fields yourself, bind each to its imported setting (Health Check offers Bind next to each setting without a field and preselects the field when the pair is unambiguous), then run a recalculation on the Recalculation tab. Nothing to reinstall, nothing to re-license. Guide: Moving from the Connect app. |
| Calculated and other custom fields (JBCF) Connect build, jbcf-cloud.jibrok.com |
Target: JBCF Forge, same Marketplace listing | Lands: Q4 2026 Available now |
You do: Update the app in Manage apps, then create the fields by the Fields to create checklist on the Migration from Connect tab and select Run again. If the tab finds no Connect settings, use a settings file. Guide: Migrate from JBCF Connect to JBCF Forge. |
Display Linked Issueslinked-issues-cloud.jibrok.com |
Target: Forge build on the same listing, delivered by the same Forge app family as Message Field | Lands: Q4 2026 Available now |
You do: Update the app in Manage apps. Your panel configurations come with it when the Connect app has saved them on your site; otherwise import them with Import from Connect file - see settings file. Guide: Moving from the Connect edition. |
Fields panel for Jira Service Managementjsm-fields-panel-cloud.jibrok.com |
Target: Customer Portal Fields Panel, the Forge build on the same listing, delivered by the same Forge app family as Message Field | Lands: Q4 2026 Available now |
You do: Update the app in Manage apps. Your portal panels and their request-type mappings carry over the first time you open the app settings, when the Connect app has saved them on your site; otherwise import them with Import from Connect file - see settings file. An option with no Forge counterpart, and the actor selection, are listed there as warnings to review. Guide: Moving from the Connect edition. |
| User helper for JiBrok cloud apps Free companion app |
Target: Withdrawn - there will be no Forge version | Lands: 31 January 2027 Withdrawn from the Marketplace |
You do: Uninstall it at your convenience before that date. See what replaces it. |
From the day an app's Forge build is published, a new installation from its Marketplace listing installs the Forge build, and the Connect build is no longer sold to new customers. Sites that already run the Connect build move by pressing Update, as described below.
The host names are shown so you can match a row to what is actually installed on your site. They are the same hosts listed on the Network Allowlist page.
Every app in the table above except User helper moves to Forge as an in-place upgrade. No JiBrok product requires you to install a second app and re-enter your configuration by hand.
app.connect.keyA Forge app can declare the key of an existing Connect app in its manifest, under app.connect.key. Every JiBrok Forge build in the plan table declares the key of the Connect app it replaces. Atlassian then treats the Forge build as the successor of that Connect app rather than as a different product: one Marketplace listing, one app key, one installation record on your site.
What you see in Jira administration → Apps → Manage apps is an ordinary app update. Press Update - or let your site's automatic updates apply it - and the Forge build replaces the Connect backend on the same site. There is no second app entry, no moment when the app is uninstalled, and no site-to-site transfer.
This is deliberately not how a Data Center migration works. There is no Jira Cloud Migration Assistant step here, no source and destination pair, and nothing to schedule with Atlassian.
| What | On an in-place upgrade | Your part |
|---|---|---|
| Marketplace listing | Upgrade: Unchanged. The Forge build is published as a new version of the listing you already own. | Your part: Nothing. |
| Licence and subscription | Upgrade: Carried over. Same subscription, same user tier, same renewal date. Billing is not interrupted and nothing is re-purchased. | Your part: Nothing. |
| App installation | Upgrade: The same installation is updated. One entry in Manage apps before and after. | Your part: Press Update, or let automatic updates apply it. |
| App configuration calendars, field settings, panels, project and request-type mappings |
Upgrade: Carried into the Forge build when the Connect build has saved its settings on your site; if it has not, the settings move with a settings file. Timer, Stopwatch, and Time between dates read the settings the Connect build left on your site the first time you open the app's admin, or when you press Import again in Health Check → Settings from Connect; a setting that already exists in the Forge build under the same name is not overwritten. Fields panel for JSM brings its portal panels and request-type mappings across the first time you open its settings. | Your part: Review the warnings after the update. Anything that did not carry over is listed as a warning in Health Check → Settings from Connect (Fields panel: in its settings) - for example, the Timer and Stopwatch events "updated", "reopened", and "moved" have no Forge counterpart. Time in Status is the exception - its hand-off runs through an export in the Connect admin. Do it before you update; see its guide. |
| Jira custom fields | Upgrade: Field types belong to the app, so the Forge build brings its own field types rather than converting the Connect fields in place. The upgrade does not create the new fields: a Jira administrator creates them and links each one to its carried-over setting. | Your part: Create the fields. Timer, Stopwatch, and Time between dates: create the Forge fields yourself and bind each to its imported setting - Health Check offers Bind next to each setting without a field and preselects the field when the pair is unambiguous - then run a recalculation on the Recalculation tab. JBCF lists the fields to create in the Fields to create checklist on its Migration from Connect tab; once they exist, Run again links them. Time in Status generates a script that creates the fields, contexts, and screen attachments for you. |
| Per-issue values | Upgrade: Recalculated by the Forge build from the issue history that already exists in Jira, rather than copied across as a data dump. | Your part: Run a recalculation if the app offers one, then spot-check a few issues. |
| Where app data is stored | Upgrade: This is the change you are making. Connect builds store app data in a JiBrok-operated database; Forge builds store it in Atlassian-managed Forge storage, inside Atlassian's perimeter. | Your part: If your organisation keeps a vendor register, update it - see the next section. |
| Rollback | Upgrade: Not automatic. Once the Forge build replaces the Connect backend, the Connect admin UI is no longer reachable; recovering Connect-side data afterwards goes through support rather than through a button in the app. | Your part: Read the product's migration guide before you press Update, and save any export it asks for. |
The automatic hand-off of Timer, Stopwatch, Time between dates, JBCF, Display Linked Issues, and Fields panel for JSM reads the settings that the Connect app has saved on your site. It works when the Connect app managed to save them there before the update. If it did not - or the Connect app was already removed - the Forge build finds nothing to import, and the settings move with a file instead:
The import from a file follows the same rules as the automatic one: a setting that already exists under the same name is not overwritten. Tip: download the file before you press Update - after the update the admin page of the Connect app is gone. If you no longer have it, ask support for the file. Each product's migration guide in the plan table has the details.
Time in Status has its own path: a JSON export from the Connect admin, made before the update - see Migration from Connect to Forge.
The move to Forge changes who processes your data and where, so the paperwork changes with it. If you keep a vendor register or a processing record, these are the entries to update once an app is on Forge:
*.jibrok.com host stops being used. See the Network Allowlist for what a Forge build still contacts - module icons, and nothing else.The architecture behind the Forge side of that is described on the Forge Architecture page.
User helper for JiBrok cloud apps is withdrawn from the Atlassian Marketplace on 31 January 2027 and there will be no Forge version of it. This is a decision, not a schedule slip - the app is not being ported later.
User helper was a free companion app: it added a JQL helper page listing example queries for the JiBrok fields on your site, and a dashboard gadget carrying JiBrok release news. Both were built around the Connect apps it accompanied.
What replaces it:
If you have it installed, you can uninstall it at any time - no other JiBrok app depends on it, and removing it does not affect any field, panel, or configuration.
Every Forge build in the table is available now, so a change window can be planned at any point before 31 January 2027.
Until 31 January 2027 the Connect builds remain fully supported and receive fixes. After that date the Atlassian Connect platform is no longer supported, and a Connect app left installed is outside both Atlassian's support and ours: we cannot fix a Connect build once the platform it runs on is unsupported, and we will not be shipping Connect releases past that point.
Nothing on your site breaks on the morning of 1 February 2027 as a matter of course - but from that day the app is running on a platform nobody maintains, and the next Jira Cloud change that affects it will not be fixed. Every JiBrok Connect app except User helper already has its Forge successor on the same listing, and for most of them the upgrade is a Marketplace update; for Timer, Stopwatch and Time between dates you then create the Forge fields and bind them in Health Check. There is no reason to be on the wrong side of that date.
If you are blocked - a feature you depend on is scheduled for a later Forge release, a change window will not fit, an assessment has to be redone - tell us early rather than late.
The plan says what and when. These say how, step by step.
The JBCF Forge build is available on the same Marketplace listing. The upgrade itself is the Update button in Manage apps; after it, a Jira administrator creates the fields by the checklist on the Migration from Connect tab (Fields to create) and selects Run again; the app links them to the Connect settings and recalculates the values.
Tell us which apps you have installed and when you are planning the move. If a Forge build is missing something your team depends on, we would rather hear it now than in January 2027.