Current situation
Jupyter Viewer for Confluenceis an Atlassian Marketplace app built on the Atlassian Connect Connection framework. Today, most cloud apps in the Atlassian Marketplace rely on this framework, which requires apps the app to be hosted on the Marketplace Partner’s our (Mibex Software) infrastructure.
In 2019, Atlassian announced a new framework called Atlassian Forge, which allows apps to run on Atlassian’s infrastructure instead. Since then, Atlassian has expanded Forge’s capabilities to support the migration of existing Connect-based apps.
We believe Forge offers significant benefits for customers, including improved security and performancedata residency. As a result, we are preparing Jupyter Viewer for Confluence to transition to the Forge platform.
...
| Panel | ||
|---|---|---|
| ||
What to ExpectThe app experience should remain the same—users should notice only minor differences. Starting in February March 2025, we will begin a staged migration to Forge, releasing several updates along the way. While We expect most updates will to be minor , some major updates will be required due to changes in permission scopes between the Connect and Forge platforms. We and we will strive to maintain a similar permission footprint. Confluence administrators will need to approve major updates, but they can do so at their convenience This means that during the updates no action is expected from the Administrator or from users of the app. However, we will communicate any action that may needed as we progress through the transitional stages to Forge. |
Timeline
The migration will begin in February March 2025 and continue throughout the first part of the year.
During this period, Jupyter Viewer for Confluence will run on a combination of Atlassian-hosted and our own infrastructure.
Our goal is a complete migration to Forge, though the exact timeline depends on how quickly we can progress through the transition stages.
...