While waiting for Atlassian to respond here (?), I wanted to highlight some posts I saw recently on other threads. It seems like the revenue share change is forcing a number of partners to ship crappier software to customers before it is ready, simply to avoid having to take a financial hit.
I believe DFTC is still considered a core Atlassian value, but the end result here feels a lot like FTC.
It would be nice if the revenue penalty could be deferred until (say) six months after the platform is ready for 99% of common use cases, to give vendors time to actually build stuff after Atlassian finishes its core platform work.
From RFC-94: Configurable Egress and Remotes - #17 by daviddrawio
Our main will have to be a RoA app, going down the route of a second, zero egress, app isn’t cutting it, the macro name change is unworkable. However, the revenue change is forcing us to jump.
We embed draw.io diagrams from cloud storage, GDrive, OneDrive, etc. The auth has to be through a known domain server. Currently, the ideal is to create another forge app that does have optional egress that all 60k installs of the main app have to install and then ask them all to migrate those embedded diagrams.
We have diagram generation via OpenAI, that’ll have to go, it can’t be done within Forge.
There’s no web socket support, so we lose real-time collaboration, falling back to a slowly, polling update. I can continue the list.
Our only way to avoid a support meltdown when this is launched is to ensure it’s a manual admin update and write “DO NOT PRESS UPDATE” in the release notes.
And on this thread: Confluence DC -> Cloud Migration & Forge: Broken Macros
Atlassian encourages migrating customers to from DC to Cloud and developers to Forge.
However, for Confluence macros the migration from DC->Cloud with Forge is harder / breaks the migration, at least as far as we can tell.
There are 3 issues I’ve noticed: Missing hidden macros, the missing legacy editor support and strange layout behaviors.
Missing ‘hidden’ macros: We used a ‘hidden’ macro in the Connect app to support migrated pages. The idea is to still show migrated content, but disallow creating new content with the in the ‘DC style/configuration’.
Have some alias functionality, to support the old ‘DC macro’ key and use the same macro.
Or Still have a way to mark a macro as hidden. To avoid confusion an dissallow creating ‘old DC style’ macros.documentation .
When migrating a page from Confluence DC → Cloud, it starts of in the ‘legacy’ editor. In the legacy editor, the Forge macro is not shown! So, it does look like the migration failed / the macro is broken. Only converting the page to the new editor will reveal the macro.
14 Likes