Our move to Atlassian Forge — migration plan
Our move to Atlassian Forge
Atlassian is ending support for Connect — the platform our Jira apps are currently built on — on 31 January 2027. We are moving our apps to Atlassian Forge, Atlassian's current cloud app platform.
We are committed to completing this migration before Connect end of support.
What this means for you
Nothing changes about what the app does. This migration is about the platform underneath it — where the app runs and how it handles your data. You keep the same features, the same configuration, and the same data.
Your data
When your site moves to the Forge version, we bring your existing configuration with you:
Teams — team names, default capacity, working days and units
Team members and their capacity — your full roster and per-person allocations
Capacity adjustments — per-sprint adjustments, personal days off and team days off
Configured boards — the boards you have selected for the app
Custom field mapping — your story points, acceptance criteria, time tracking, business value and sprint field configuration
Velocity and sprint history are rebuilt automatically from your Jira data the first time you open a board, so your charts and metrics populate without anything being copied across.
This happens automatically the first time the Forge version of the app is used on your site. You do not need to export, re-enter or reconfigure anything.
What you need to do
For most customers: approve the app update when Jira offers it.
Depending on your installation, the update may be applied automatically, or your Jira administrator may be asked to review and approve it from Manage apps. Atlassian surfaces it the same way as any other app version.
A small number of installations are never updated automatically by Atlassian — in particular installations made with a Marketplace access token, and installations with a suspended licence. If that applies to you, your administrator will need to install the Forge version manually, and we will contact you directly.
Your licence, your subscription, and your Marketplace reviews and ratings are unaffected. The app keeps its existing Marketplace listing.
Timeline
Milestone | Date |
|---|---|
Forge version released — Backlog refinement and Sprint planning | 21 June 2026 (released) |
Forge version released — Sprint planning and capacity planning for Jira | 25 September 2026 (target) |
All customers migrated | 1 October 2026 (target) |
Connect end of support (Atlassian) | 31 January 2027 |
Dates marked target are our current plan and may shift; the Connect end-of-support date is set by Atlassian. We will keep this page up to date as the migration progresses.
Questions
If you have questions about the migration or your data, contact us at support@divim.io.
Last updated: 29 August 2026