draw.io for confluence cloud migration to full forge app #5270
Replies: 3 comments 2 replies
-
|
Because draw.io now uses forge functionality to embed from Google Drive, OneDrive and Github, the app will prompt for every user to allow access to these OAuth endpoints. Unfortunately, there is no way to avoid this currently until Atlassian provide some technical means to do so. Dynamic modules might help in this regard. If having every single user approve the app after upgrade is a problem, please contact Atlassian support. This is what all users will see after updating:
|
Beta Was this translation helpful? Give feedback.
-
|
https://jira.atlassian.com/browse/ECO-1091 is currently causing problems and has been since we migrated. The error rate is lower, but we don't yet believe this fully fixed. |
Beta Was this translation helpful? Give feedback.
-
|
Hi
Is the full-screen option available by now? Many thanks for an update on that. |
Beta Was this translation helpful? Give feedback.


Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
As part of upcoming changes in the Atlassian Marketplace, all apps must move to Forge or face a staged revenue penalty (4% at year-end, rising to 8% six months later). In order to avoid this we are completing the migration away from Connect to a fully Forge-based app.
Most functionality will remain unchanged. The main difference is that Forge currently does not provide a full-screen custom macro option. We first requested this in November 2021 (FRGE-557) , but it is still unavailable and won’t be ready before the first migration deadline.
Migration will begin in the second half of September 2025. Depending on Atlassian’s rollout rules, administrators may need to manually update, though in some cases updates could occur automatically. If possible, we recommend delaying the update until the full-screen option becomes available.
Migrating right up against the deadline is too risky for us, plus there is no indication that the full screen editor will be available in 3 months, so the result will be the same.
We regret the impact the reduced editor size may have on productivity. If this affects your team, we encourage you to provide feedback directly on FRGE-557.
Beta Was this translation helpful? Give feedback.
All reactions