Atlassian

Atlassian developer platform changelog updates

Atlassian API Changelog Monitoring

Atlassian ecosystem changes can affect marketplace apps, Jira and Confluence integrations, and admin workflows used across enterprise teams. This Atlassian API Changelog Monitoring page helps you review updates in a structured way before they ripple into production usage.

Better Atlassian API Changelog Monitoring helps marketplace and internal-tool teams understand changes to platform behavior, APIs, and policies before customers raise issues. It supports a cleaner release process by turning changelog review into a routine instead of a scramble.

The benefit of Atlassian API Changelog Monitoring is simple: your team gets a repeatable way to watch changes, evaluate risk, and act before small upstream updates turn into customer-facing bugs. Atlassian developer platform changelog updates

Atlassian API down?

Atlassian API down? Soon we will add direct API status monitoring alongside Atlassian API Changelog Monitoring. For now, go to the official API status page on the Atlassian website. In the future, we plan to detect downtime signals even before the public status page is updated.

Recent changes

Showing the last 10 changes from this feed.

04-16-2026

[Announcement] Compass Transition to DX

As we focus on delivering a next‑generation solution for tracking developer productivity and experience, Compass scorecards and catalog functionality will move into DX. As part of this transition, we will be ending the sale of Compass on May 13, 2026.Impact on Forge apps for CompassAfter this date, partners and developers will no longer be able to create, list, deploy, or publish new Forge apps for Compass.Developers can continue to ship patches and updates to existing Compass Forge apps.Customers can continue to install and use existing Compass Forge apps while they have access to Compass.Other types of Forge apps are unaffected.Learn more and get helpFor more details using the full announcement on the Atlassian blog. If you have questions, contact Developer Support through the Atlassian Developer Support portal.

Source

04-15-2026

[Added] Confluence performed-search event is now available

We've added a new Confluence Forge event for performed search: avi:confluence:performed:search You can use this event to invoke your Forge app function when a Confluence search is performed. For more details, see the Confluence events reference documentation.

Source

04-15-2026

[Removed] Forge Realtime: Global channels do not require ‎`read:app-global-channel:realtime` scope

Following its initial Preview release, Forge Realtime does not require the read:app-global-channel:realtime scope to use global channels.Impact: No behaviour change for apps already deployed or installed with this scope.Action required: Remove the read:app-global-channel:realtime scope from your app manifest before your next deployment.

Source

04-15-2026

[Announcement] Bitbucket 9.4.19 and 10.2.2 releases available now

Bitbucket Data Center and Server 9.4.19 and 10.2.2 bug fix releases are available now!To see the issues resolved in these bug fix releases, go to:Bitbucket Data Center and Server 9.4 release notesBitbucket Data Center and Server 10.2 release notesGet the latest LTS bug fix release

Source

04-14-2026

[Deprecation Notice] Spacing prop on @atlaskit/icon and @atlaskit/icon-lab components

The spacing prop on icon components in @atlaskit/icon and @atlaskit/icon-lab is now deprecated. The prop was introduced to ease migration from the legacy icon system by allowing icons to carry their own padding. Now that the legacy icon migration is complete, whitespace around icons should be controlled by the surrounding layout rather than the icon itself — consistent with how the rest of the Atlassian Design System handles spacing. The spacing prop will be removed in a future major release. While no immediate action is required and existing usages will continue to work for now, we recommend migrating away from spacing ahead of its removal. To migrate, replace spacing="spacious" or spacing="compact" with a Flex wrapper from @atlaskit/primitives/compiled using explicit padding tokens. A codemod and ESLint rule with IDE quick-fix are available to automate the migration. Full guidance:  https://atlassian.design/components/icon/usage 

Source

04-14-2026

[Removed] Legacy icon entry points removed from @atlaskit/icon

The legacy icon entry points in @atlaskit/icon have been permanently removed following the deprecation notice published in 2024. The removed entry points are: @atlaskit/icon/glyph/, @atlaskit/icon/core/migration/, @atlaskit/icon/utility/, @atlaskit/icon/base, @atlaskit/icon/svg, and @atlaskit/icon/migration-map.The no-legacy-icons ESLint rule has also been removed from @atlaskit/eslint-plugin-design-system as it is no longer needed.Apps using Forge Custom UI or Atlassian Connect that import from any of the above entry points must update their imports to use @atlaskit/icon/core/ instead. Migration guidance, codemods, and the full list of icon replacements were published in the original deprecation notice:  https://developer.atlassian.com/changelog/#CHANGE-2773 

Source

04-13-2026

[Announcement] Forge CLI now supports listing developer spaces

The Forge CLI now supports listing developer spaces using a new command, forge developer-spaces list. This command will display a table of your developer spaces including their IDs and names. It also supports JSON output using the --json option, similar to other list commands in the Forge CLI.This command is included in the latest version of @forge/cli. Run npm install -g @forge/cli@latest to install this version.

Source

04-12-2026

[Fixed] Forge Storage DATETIME values at midnight will always include the time component

We're updating the behavior of DATETIME values returned by Forge Storage's SQL layer.Previously, DATETIME values set to midnight (00:00:00) were returned without the time component — for example, 2026-01-15 instead of 2026-01-15 00:00:00. After this change, the time component will always be included.What's changingDATETIME values at midnight will now return the full timestamp, including 00:00:00.Previously, the time component was omitted for midnight values, returning only the date.This change will be rolled out on October 6, 2026.This change is not backward-compatible. Apps that parse or compare DATETIME values and rely on the absence of the time component for midnight values may see unexpected results.What you need to doReview any code that reads DATETIME values from Forge Storage.Ensure your app handles DATETIME values with a time component, including 00:00:00.Test your app before October 6, 2026 to verify compatibility.For more information, see Forge Storage.

Source

04-09-2026

[Announcement] Extension of temporary upgrade behaviour for Forge apps over 50,000 users

We are still rolling out a small number of critical back-end fixes that help maintain the stability of the upgrade path for large apps. Extending by two weeks gives us the confidence that these changes are fully deployed and verified before we re-enable minor version updates.We are extending the period during which all updates to Forge apps with over 50,000 users are classified as major version updates. The new end date is 27 Apr 2026.During this time, you can continue to use the forge version bulk-upgrade command to roll out updates to customer sites. For detailed information on how to use forge version bulk-upgrade, see  https://developer.atlassian.com/platform/forge/cli-reference/version-bulk-upgrade/. This change continues to have no effect on how apps qualify for the Forge revenue share rate. Your latest deployed app version determines revenue share eligibility.

Source

04-08-2026

[Deprecation Notice] Brownout Notice: OAuth 2.0 and API authentication changes for Bitbucket Cloud

As shared in our  https://developer.atlassian.com/cloud/bitbucket/changelog/#CHANGE-3052 , Bitbucket Cloud will fully deprecate / change behaviour for a small set of OAuth2 features on 04 May 2026. To help teams identify and migrate any remaining usage ahead of the enforcement date, we will run a series of controlled brownouts starting 20 Apr 2026, for two weeks, after which the functionality will be fully removed on 04 May 2026.During each brownout window:All OAuth authenticated requests directed at www.bitbucket.org will fail with an HTTP 401 error codeAll OAuth authenticated requests which provide the OAuth access token in the access_token query parameters / POST body will fail with an HTTP 401 error codeThe Client credentials grant flow will not issue refresh tokens in their token response.OAuth token response payloads will return “scope" instead of “scopes" (See notes)Notes:The minting of OAuth2 access tokens should always be made to https://bitbucket.org/site/oauth2/access_token. Bitbucket’s API does not mount these urls under the api subdomain.In the week beginning 12 Apr 2026 the scope property will be returned alongside the scopes property, allowing time to onboard prior to the start of the brownout.

Source