This page contains announcements and updates for developers from various products, platforms, and programs across Atlassian. It includes filter controls to make it easier to only see updates relevant to you.
To ensure you don’t miss any updates, we also provide RSS feeds. These feeds will take on any filters you applied to the page, and are a standardized way of keeping up-to-date with Atlassian changes for developers. For example, in Slack with the RSS app installed, you can type /feed <FEED URL> in any channel, and RSS updates will appear in that channel as they are posted.
As previously announced in the https://developer.atlassian.com/platform/marketplace/changelog/#CHANGE-2623 and https://atlassianpartners.atlassian.net/wiki/spaces/resources/pages/858980395/Marketplace+Partners+Maximum+Quantity+Billing+-+Quick+Reference+Guide, we’re introducing maximum quantity billing (MQB) in a phased approach.
Maximum Quantity Billing(MQB) charges will appear in Transactions Reports and following APIs.
Transactions API: Get transactions
Export Transactions: Export transactions
Async Export Transactions Initiate Async Export transactions
To help identify MQB transactions, in the transactions API response, purchaseDetails section,
proratedDetails returns an array of objects, each with:
addedUsers: Number of additional users added during the monthly billing cycle.
date: Date when additional users were added.
This helps partners track user additions and calculate prorated charges for each user additions during the billing cycle.
In addition, to view all MQB charges, a separate filter view
showProratedTransactions returns list of all MQB charges and is labeled as sales price(prorated) in Transaction Reports.
To ensure smooth transition with the upcoming changes, we recommend partners to review the API documentation as well as the Quick Reference Guide for an example transaction.
The legacy /application/:id/compliance/memberPrivacy API route will be deprecated and removed after Sep 8, 2025. This change is part of ongoing efforts to simplify our codebase and align with current privacy practices for Trello power-ups and integrations.
Privacy compliance remains a requirement for all Power-ups and Integrations that store personal data. Developers currently using the legacy route should migrate to the supported workflow:
Create or update your Power-up or integration through the Trello Developer Portal.
Navigate to the Privacy and Compliance tab for your power-up or integration.
Link your app key as part of the Power-up setup.
Use the /plugin/:id/compliance/memberPrivacy API, which provides similar functionality and is required for ongoing compliance.
See https://developer.atlassian.com/cloud/trello/guides/compliance/personal-data-storage-gdpr/ for details.
After Sep 8, 2025, requests to the deprecated endpoint will no longer be supported. Please ensure your applications are updated to use the new compliance route to avoid disruption.
If you have any questions, please reach out via the Trello Developer Community or support channels.
We are announcing the deprecation of the following internal API endpoints:
/wiki/rest/masterdetail/1.0/detailssummary/lines
/download/thumbnails/{id}/{id}
/download/resources/{id}/icons/{id}
/download/resources/{id}/{id}
/download/resources/{id}/images/{id}
Key Dates:
Deprecation announcement: August 6, 2025
Removal date: October 6, 2025
Why is this happening?
This API is not intended public use and is not supported.
What will happen?
On and after the removal date, all requests to the listed endpoints will result in a 404 Not Found response.
Action Required
For developers using */download/thumbnails* or */download/resources/*, we recommend migrating the public Attachment API before the removal date.
For developers using /wiki/rest/masterdetail/1.0/detailssummary/lines, there is currently no public alternative.
We are announcing the deprecation of the following internal API endpoints:
/download/attachments/{id}/crash-scraper/files/{id}
/download/attachments/{id}/{id}/customer-card-payment-rest
/download/attachments/{id}/{id}
/download/attachments/{id}/{id}/{id}
/download/download/attachments/{id}/{id}
/download/attachments/{id}/{id}/{id}/{id}
/download/attachments/{id}/attachments/{id}/{id}/{id}
/download/attachments/{id}/{id}/image
/download/all_attachments
Key Dates:
Deprecation announcement: August 6, 2025
Removal date: November 6, 2025
Why is this happening?
This API is not intended public use and is not supported.
What will happen?
On and after the removal date, all requests to the listed endpoints will fail.
Action Required
We recommend migrating to the public Attachment API before the removal date.
Forge offline user impersonation was recently made available in Preview. As part of this, the ability to exchange a Forge system OAuth token on a Forge remote for a token to impersonate any user.
This was released with a rate limit of 10,000 requests per minute per app, however after carefully consideration, we need to temporarily reduce this limit to 1,000 requests per minute per app. This rate limit applies only to the exchanging of a system token for a user impersonation token using the offlineUserAuthToken GraphQL mutation. Calls from a Forge function using asUser are not affected. Calls made to APIs using these tokens are not affected and instead use the rate limit defined for each API endpoint
We will continue to work towards increasing this limit as we move towards general availability of this feature.
We have identified an issue due to which the EXPERT discount information was not provided on the Transactions API and Marketplace Transactions reports for certain entitlements from the new billing system.
As a result, solution partner discounts were not displayed for certain entitlements and their respective order IDs.
The issue has now been fixed, and transactions have been back-filled to display the accurate Discount Amount in the purchaseDetails.discounts array field and type EXPERT for 44,000 transaction line-items spread across partners.
Next Steps:
The changes will go live in production starting on Aug 5, 2025 and can be accessed via the following APIs:
Partners can fetch this data through the lastUpdated field of the API.
What’s new in Confluence 10.0?
Spring and Jakarta upgrade
Removal of deprecated components in AUI 10
End of support for LESS
Removal of Trusted apps
End of support for the Original theme
Global serialization filter
App signing is now enabled by default for app installations
Enhanced security with Content Security Policy
Basic authentication disabled by default
Monitoring and observability of the Synchrony process
Add scopes to REST endpoints to use OAuth 2.0 2LO
Control how many labels display in macros
Lots more!
To learn more, see Confluence 10.0 release notes.
This release doesn’t support Server licenses. If you have a Server license, check out your options for upgrading.
To address parity gaps between Connect webhooks and Forge product events in Confluence, the following changes have been made for various events:
Change category | Forge product events (New) | Connect webhooks (Existing) | Affected events |
|---|---|---|---|
Event Timestamps |
|
| All events |
Notification control |
|
| Events that support notification suppression |
Update triggers |
|
| All update events |
Content versioning |
|
| All content, comment and attachment events |
Creation history |
|
| All content and space events |
Creator information |
|
| All content and space events |
Ownership |
| N/A | All content events |
Container metadata |
| Various fields representing a container | Attachment, comment, custom content events |
The space.homepage field hasn’t been added to space events due to an unexpected issue. We will add it as soon as we resolve the problem on our end. However, the ID of a space homepage can still be retrieved via the https://developer.atlassian.com/cloud/confluence/rest/v2/api-group-space/#api-group-space.
For more details on the Forge product events, refer to https://developer.atlassian.com/platform/forge/events-reference/confluence/ page.
The nodejs18.x runtime available to Forge apps has reached the end of its deprecation period, and is no longer supported.
Apps using this runtime can no longer be deployed or updated, although existing deployed apps may continue to function. Such apps are provided “as-is", with no warranties or access to support. Over time, unsupported runtimes may become non-functional or vulnerable to security issues.
All app developers are strongly encouraged to update their app to a supported Node.js runtime (nodejs20.x or higher) as soon as possible.
The Teamwork Graph Smart Links module is now available in Forge, allowing developers to create custom Smart Links that enhance URLs with additional metadata, thumbnails, and status indicators.
This feature enables rich link previews and improves user experience by providing contextual information and actions for linked content from supported platforms.
For more information, see Smart Link module documentation and Teamwork Graph supported object type documentation.
The Smart Links module is currently only available for apps installed into Jira.
EAP 06 is the final EAP for Jira 11.
We’re happy to present the sixth and final Early Access Program (EAP) build of Jira Software 11.0 and Jira Service Management 11.0. To find out what’s in scope of this EAP release, refer to Preparing for Jira 11.0.
You can download the current EAP from this page. If you’re using maven.atlassian.com, the version is 11.0.0-m0015.
This EAP release isn't for production or demonstration use.
We are extending the deprecation period of the Convert content body v1 REST API in Confluence Cloud to Feb 1, 2026.
As mentioned in the original deprecation announcement, developers will be able to use the Asynchronously convert content body endpoint as an alternative. We will make sure that known load and timeout complexities with the asynchronous endpoint are resolved by the time the Convert content body v1 REST API is deprecated.
We've updated the Forge module jira:projectPage to include board.id and board.type in its extension data. This change allows developers to access board-specific information directly within the project page, enabling more tailored and context-aware apps.
We are augmenting the existing company-managed Number custom field in Jira Cloud to support unit configuration. This will include currency and percentage unit types, as well as formatting.
Apps will be able to do the following through the Atlassian GraphQL Gateway (AGG):
Retrieve and display values with correct formatting (currency, percentage, or number) by querying formatUnit, formatStyle, and formatDecimals on JiraNumberFields
Set and update the number field formatting via setting formatConfig when creating or updating custom fields
Please note that:
The underlying Number value storage will remain unchanged, meaning that this is a purely additive change and no action is needed.
JQL search will behave exactly like the number field works today. It will be unaware of the currency unit through all the access points.
This functionality has already been released in team-managed projects. See the announcement here
Rollout: will be progressively rolled out by tenant starting late August 2025
You can now name transitions that allow issues to move into a status from anywhere in the workflow.
Create Transition Modal:
Enable users to name ‘from any status’ transitions during creation.
Transition Side Panel:
Allow users to update ‘from any status’ transition names.
Status Side Panel:
Display the transition name.
Edit Status Modal:
Provide an option for users to retain the existing transition name or update it to match the new status name.
Add a transition preview card for this type of transition.
Rate this page: