Changelog

We are upgrading from jQuery 3 to 4 in Jira 12, Confluence 11, Bitbucket 11, Bamboo 13, and Crowd 8. jQuery migrate will also be removed. Much frontend code depends on jQuery and we expect this will require upgrade work in apps (e.g. P2 plugins) and custom integrations with a frontend.

We consider this a breaking change and thus do not plan to backport to existing LTS releases.

This is to continue to meet customers' demands for secure & compliant products. We must be proactive in this upgrade because of how much our products and apps depend on it. We had many requests in the past to upgrade from jQuery 2 to 3, especially when there were vulnerabilities found in jQuery.

As we learn more and refine developer tooling to assist with the work, we will update the developer documentation

Many of the changes can be prepared for in a way that's backwards compatible with v3 so as many (compatible) changes as possible will also be backported to the LTS versions of Jira (11.3), Confluence (10.2), Bamboo (12.1) and to the latest versions of Bitbucket 10 and Crowd 7. The intention is to make it easier to test your app without having to worry about unrelated breaking changes.

Similarly, AUI 10.1 adds support for jQuery 4.

We will continue to provide jQuery web-resources and we ask developers to use them so that if needed we can roll out security patches as quickly as possible.

We are still early on in upgrading the Data Center products themselves. Future EAP versions will come with jQuery 4, but this might not arrive in the first few versions.

We have not currently noticed any JS behaviour nor signature changes that would affect apps. Please let us know if you spot something, and we will document it.

See the developer community announcement topic for more information and to leave feedback

Data Center products support React 18 starting with the following versions:

• Bamboo 12.0

• Bitbucket 10.1

• Confluence 10.1

• Crowd 7.1

• Jira Software 11.2

• Jira Service Management does not bundle on its own copy

React 18.3.1 is provided by a bundled com.atlassian.plugins.react cross-product app that supersedes previous product specific React web-resources. React dependencies are exposed as AMD modules via the following web-resources:

• com.atlassian.plugins.react:react-core-amd provides the atlassian/libs/react AMD module

• com.atlassian.plugins.react:react-dom-amd provides the atlassian/libs/react-dom and atlassian/libs/react-dom/client AMD modules

• com.atlassian.plugins.react:react-amd is a convenience bundle of React and ReactDOM above

Where applicable, existing React 16 web-resources are considered deprecated and will be removed in the next platform releases.

Additionally, we plan to upgrade to React 19 following the Atlaskit support as announced in https://community.developer.atlassian.com/t/rfc-78-dropping-support-for-react-16-and-rendering-in-a-react-18-concurrent-root-in-jira-and-confluence/87026/23

Starting with the following versions, major product releases will no longer support installing plugins that require transformation:

• Confluence 11.0

• Jira Software 12.0

• Jira Service Management 12.0

• Bamboo 13.0

• Bitbucket 11.0

• Crowd 8.0

For details, explore Transformed to transformerless plugin conversion.

Context:

Any P2 plugin development using modern versions of Atlaskit will end up compiled-css.css files inside target/classes. We’ve been upgrading React & Atlaskit in the DC products and so many of the P2 plugins that make up our products now have a compiled-css.css file.

This made a long-standing bug with local development more obvious. The first compiled-css.css file found by the plugin system was used for all P2 plugins (instead of using the specific file from the respective plugin). https://compiledcssinjs.com/ compiles equivalent styles to the same CSS classname and there is decent, but not perfect overlap in styles. The result was that often just one Atlaskit component wouldn’t render correctly or any plugin-specific styles would be missing. This can be quite hard to debug because in the browser development tools it looks like the compiled-css.css file doesn’t change no matter what you do, this is of course because it’s using another plugins'.

Action:

We have fixed this long-standing underlying bug, but remained backwards compatible. To use the new, fixed local development system instead of the existing, buggy implementation you will need to use the upcoming post-2025-LTS product versions for local development (e.g. Confluence 10.3, e.g. Jira 11.4), and also upgrade QuickReload to 6.2.0+ (included in AMPS 9.7.2). If everything goes smoothly we will consider backporting to LTS releases of the products. Note: Crowd doesn’t have LTS releases, but it’s looking to be in Crowd 7.3

For more details read the original bug report: https://ecosystem.atlassian.net/browse/PLUG-981.

If you have any issues or questions, feel free to ask us on developer community.

Cheers,
Michael Kemp

We’re pleased to announce that Crowd 7.1.0 is now available. We have made some security enhancements and some changes to the supported platform. Explore Crowd 7.1.0 to see the full list of updates.

As part of the Crowd 7.0 release, we've introduced a new method for creating service accounts. Service accounts are specialized, non-user accounts created for secure and efficient management of automated processes and external integrations.

You can now create service accounts in Crowd using REST APIs with OAuth 2.0 authentication.

We're also working to provide a new user interface to make it even easier to create service accounts across products.

Please let us know if you have any feedback or questions.

We’re pleased to announce that Crowd 7.0.0 is now available. We have made some security enhancements and some changes to the supported platform. Explore Crowd 7.0.0 to see the full list of updates.

Crowd 7.0 EAP03 milestone is available now for testing.

To find out what else changed, check out Preparing for Crowd 7.0 or download the latest EAP

We’re pleased to announce that Crowd 6.3.0 is now available. We have made some security enhancements and some changes to the supported platform. Explore Crowd 6.3.0 to see the full list of updates.

To maintain high security standards, we're making the following changes to the upcoming major versions of all the Data Center products:

• Spring and Jakarta upgrade

• JQuery upgrade

• Removal of deprecated components in AUI 10

• Removal of Trusted apps

• End of support for LESS

• End of support for the Original theme

• Supported platform updates

Visit the https://developer.atlassian.com/platform/marketplace/dc-apps-platform-8/#prepare-your-data-center-app-for-2025-security-and-usability-updates page to learn more about these updates, find resources, useful dates, and links.

We’re pleased to announce that Crowd 6.2.0 is now available. Explore Crowd 6.2.0

We're updating source access of the atlassian-jwt, atlassian-security, and atlassian-seraph repositories to available by request only.

Crowd 6.2 EAP milestone is available now for testing.

To find out what else changed, check out Preparing for Crowd 6.2.

Do you have feedback or want to discuss the latest EAP? Chat with us in this Atlassian Developer Community thread The earlier we know about potential problems, the more time we'll have to fix them before the final release.

Download the latest EAP

We are removing mirrors of third-party packages such as maven-central from packages.atlassian.com

We’re proud to present Crowd 6.0. With this release, we’ve introduced the upgrade to Atlassian Platform 7 and removed support for JDK 8 and 11. Check out the release notes for the full list of updates

Upgrade to Crowd 6.0