Preparing for Confluence 9.3
This documentation is intended for Confluence developers who want to ensure that their existing plugins and apps are compatible with Confluence 9.3.
Watch this page to find out when a new milestone is available and what’s changed. We will publish formal release notes once we release a beta.
Latest milestones
20 January 2025 | 9.3.0-m179 |
Issues with this milestone?
Hit the Feedback button on the Confluence EAP header or raise an issue to tell us about it.
On this page:
Planned changes
In this section we'll provide an overview of the changes we intend to make, so you can start thinking how it might impact your app. We'll indicate when a change has been implemented, and in which milestone.
This release only supports Data Center licenses. If you have a Server license, check out your options for upgrading.
Templates in blog posts
Status: IN PROGRESS
We’re excited to bring you the ability to use templates in blog posts. Similarly to how this works in Confluence Cloud, you’ll be able to create Confluence pages using templates, and convert these pages to blog posts.
Gadgets app available in beta
Status: BETA AVAILABLE
To enable integration between Confluence and Jira, we’re bringing back Gadgets, which were removed in Confluence 9.0, as an Atlassian Marketplace app.
For more information about this change, read Gadgets moved to a Marketplace app from Confluence 9.2 onwards.
App available in beta
We’ve made the beta version of the External gadgets for Confluence app available for testing and feedback. The app is still under development and its functionality may be limited.
Download and install the app for testing
If you try the new app, share your comments in the ticket linked above.
Deprecation of OpenSymphony PropertySet
Status: ADVANCE NOTICE
In Confluence 9.3, all APIs that use PropertySet are deprecated. Mutative operations will be blocked from Confluence 10.0, and the APIs will be removed entirely in Confluence 11.0.
This change affects the following APIs based on PropertySet for Users:
com.atlassian.confluence.user.ConfluenceUserPropertySetFactorycom.atlassian.confluence.user.UserAccessor#getPropertySetcom.atlassian.confluence.user.UserAccessor#getConfluenceUserPreferences
The supported data types will remain accessible using the following replacement API:
com.atlassian.confluence.user.UserAccessor#getUserPreferences(ConfluenceUser)
Supported data types are:
BooleanString(andText)LongInteger
Migrate all other data types to a suitable replacement as soon as possible because they will become read-only from Confluence 10.0 and completely inaccessible from Confluence 11.0.
The following APIs based on PropertySet for Content are also affected:
com.atlassian.confluence.core.ConfluencePropertySetManager
Migrate any required data in your apps to one of the following alternatives as soon as possible because it will become read-only from Confluence 10.0 and completely inaccessible from Confluence 11.0.
- (Spaces)
com.atlassian.confluence.api.service.content.SpacePropertyService - (Content)
com.atlassian.confluence.api.service.content.ContentPropertyService
To migrate data, you may choose to implement the com.atlassian.sal.api.upgrade.PluginUpgradeTask API in your apps and export it as an OSGi service. For details, see Writing a plugin upgrade task to migrate user data to new user keys.
Deprecation of Bandana
Status: ADVANCE NOTICE
In Confluence 9.3, the com.atlassian.bandana.BandanaManager API has been deprecated. Mutative operations will be blocked from Confluence 10.0, and the APIs will be deleted entirely in Confluence 11.0.
Migrate any required data in your apps as soon as possible to one of the following alternatives.
com.atlassian.sal.api.pluginsettings.PluginSettingsFactorycom.atlassian.confluence.api.service.content.SpacePropertyServicecom.atlassian.activeobjects.external.ActiveObjects(For details, see Active objects)
Note that com.atlassian.confluence.setup.xstream.ConfluenceXStreamManager will remain available for manual serialization and deserialization needs if needed.
To migrate data, you may choose to implement the com.atlassian.sal.api.upgrade.PluginUpgradeTask API in your apps and export it as an OSGi service. For details, see Writing a plugin upgrade task to migrate user data to new user keys.
Implemented changes
In this section we'll provide details of changes we have implemented, organised by the milestone they are first available in. This will help you decide which milestone to use when testing.
EAP 3 – 20 January 2025
Milestone 9.3.0-m179
Contains:
Minor bug fixes
EAP 2 – 13 January 2025
Milestone 9.3.0-m146
Contains:
- Minor bug fixes
EAP 1 – 7 January 2025
Milestone 9.3.0-m129
Contains:
- Minor bug fixes
Looking for updated documentation? Check out the Confluence EAP space for the latest docs.
Did you know we’ve got a new developer community? Head to community.developer.atlassian.com/ to check it out! We’ll be posting in the announcements category if when new EAP releases are available.