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.

07-16-2026

[Added] Forge LLMs (Preview) now supports Claude Sonnet 5

Support for Claude Sonnet 5 model is now available in Forge LLMs. For the exhaustive list of supported models, refer to our documentation here

Source

07-15-2026

[Announcement] Commerce Pricing APIs blocked

Commerce Pricing APIs are currently unavailable.Access to the Commerce Pricing APIs (both update and fetch operations) has been temporarily blocked while we carry out maintenance and validation work. Please do not use these APIs until further notice. Any requests made during this period will fail and return an API block message. We'll update this page and publish a changelog entry once the APIs are available again. Thank you for your patience. https://developer.atlassian.com/platform/marketplace/marketplace-app-pricing-api/ 

Source

07-14-2026

[Early Access] Point-to-Point Logs Export (EAP)

Point-to-Point logs export is now available in Early Access (EAP). This feature allows Atlassian to push Forge app logs directly to your preferred logging tool across all environments, including production.During this EAP, we support the following tools:DatadogSumo LogicAmazon CloudWatch (US region only)SplunkWhat you need to doSign up for the EAP here.Review the setup guide to understand how to share your tool details with us in the EAP form.

Source

07-14-2026

[Announcement] Bitbucket 9.4.22 and 10.2.5 releases available now

Bitbucket Data Center and Server 9.4.22 and 10.2.5 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

07-14-2026

[Announcement] IconTile - `shape` prop and circular tile support removed in `@atlaskit/icon`

The deprecated shape prop and UNSAFE_circleReplacementComponent prop have been removed from IconTile in @atlaskit/icon. Circular icon tiles are no longer supported. This follows the deprecation notice issued 6+ months ago.What’s removedshape prop - shape="circle" and shape="square" are no longer accepted. Square is the only shape and is now the default with no prop needed.UNSAFE_circleReplacementComponent prop - the escape hatch introduced during the deprecation period has been removed.Related resourcesIconTile documentation on atlassian.designPrevious announcement: CHANGE-3273 - Icon Tile design language improvements

Source

07-13-2026

[Removed] Removal of the Workflow transition properties APIs

As per the notice of the deprecation of the workflow transition properties APIs on March 30, 2025, the Workflow transition properties API set has been removed from our public API. This API is no longer supported.If you were using the Workflow transition properties APIs, you must transition to the Bulk get workflows and the Bulk update workflows APIs to manage transition properties on workflows.

Source

07-13-2026

[Added] Forge custom field search aliases now support app-provided search suggestions

What's changingForge apps can now provide custom search suggestions for searchAlias properties of Forge object custom fields.If your app already uses searchSuggestions, you can enable it for a specific alias by setting searchSuggestionsEnabled: true on the object schema property that defines that searchAlias. When users write JQL against that alias, Jira will show app-provided suggestions instead of default indexed values. What you need to doIf your Forge object custom field already uses searchSuggestions and you want those suggestions to apply to a searchAlias:Update your app's manifest to set searchSuggestionsEnabled: true on the schema property that defines the alias.Ensure your searchSuggestions function is configured to handle requests for the alias.No action is needed if your app doesn’t use search aliases, or if you want aliases to keep using Jira’s default autocomplete.For more information, consult the  https://developer.atlassian.com/platform/forge/manifest-reference/modules/jira-custom-field  reference documentation.

Source

07-10-2026

[Added] Increased Limits for Concurrent Tasks

Callers can now have up to 10 unfinished tasks queued up, increasing the limit from the existing 5.

Source

07-09-2026

[Announcement] Jackson 3 upgrade in Data Center

We are upgrading Jackson from version 2 to 3 in Jira 12, Confluence 11, Bitbucket 11, Bamboo 13 and Crowd 8.The goal of this work is to keep DC products secure and compliant with our dependency policy while allowing upgrades during each major product version's supported period.Areas affected by this upgrade:The product system bundle provides Jackson 3 but not Jackson 2Plugins using the system bundle's Jackson must migrate to Jackson 3. See the official Jackson 3 migration guide.We shared the detailed migration steps in atlassian-rest UPGRADE_9_1_0.md.If you have any comments, feel free to leave your feedback on the developer community announcement.

Source

07-09-2026

[Announcement] [2-week notice] Connect EOS customer messaging to go live to production instances for select cohort of apps

As per our previous announcement, we will be progressing admin-facing migration messaging on the Connected Apps page from the Developer Canary Program to production instances. This rollout will begin in approximately two weeks.Apps affected in this initial rolloutThe following app categories will receive admin-facing messaging:Apps that have declared connectToForgeMigration with a migration intent of "no"Apps that have declared connectToForgeMigration with a migration intent of "unsure"Apps that have not adopted the connectToForgeMigration moduleApps without a Forge manifest (i.e., Connect apps)Apps that have declared connectToForgeMigration with an intent of "yes" are estimated to begin receiving admin messaging in mid-August. We will provide another changelog entry at least 2 weeks before that change proceeds. End-user (in-product) messagingEnd-user messaging will not be included in this initial rollout. When ready, we'll follow the same approach:Release to Developer Canary tenants first for early testingRoll out in staggered cohortsProvide at least 2 weeks advance notice via the Forge changelog before each rollout stage goes liveWhat you need to doAdopt the connectToForgeMigration module in your Forge manifest for each major version of your app ( https://developer.atlassian.com/platform/adopting-forge-from-connect/connect-to-forge-migration-module/ ).Declare your migration intent as this determines which cohort your app falls into and when messaging appears.Provide a migration URL. This URL will be surfaced directly in customer-facing notices, replacing the default Atlassian messaging with your app-specific guidance.Preview the experience now using the Developer Canary Program. Customer messaging is already live on canary tenants. Install your app on a canary instance, navigate to the Connected Apps page, and confirm your migration URL renders as expected before the production rollout reaches your cohort.

Source