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.
This is a reminder about the changelog announcement regarding the deprecation of the Forge sandbox runtime on Aug 28, 2024.
The retirement of the sandbox runtime will take effect on Feb 28, 2025, upon which any apps using the sandbox runtime will stop working.
Please ensure you update your app before the Feb 28, 2025 using this guide.
To increase awareness of the impending deadline, apps using the sandbox runtime will be blocked from executing in all development environments beginning Feb 19, 2025.
If you have questions or concerns about this deprecation, please visit this community thread.
We have identified an issue within our system that resulted in the absence of customer feedback on churn events via the Feedback APIs between January to February 2025.
This issue has now been resolved, and consequently, 167,332 customer feedback records will be made available across all partners. These customer feedbacks were generated during the period from August 2020 to the present date. Effective Feb 20, 2025, partners will gain access to customer feedback regarding churn events from both historical and current feedback through reporting, as well as via the following APIs:
All the Forge Bitbucket UI modules extension data now include a location property, which is available by calling the useProductContext hook. It provides the full URL of the host page where the module is displayed in. For more details, see the https://developer.atlassian.com/platform/forge/manifest-reference/modules/index-bitbucket/.
We have recently noticed an unusual increase in API usage. In order to maintain reliable services for both Atlassian customers and partners, we will begin enforcing more granular rate limits for Confluence and Jira APIs.
We will begin enforcing REST API (Quota and Burst based) rate limits for all free apps on or after August 18, 2025. We have added additional headers to provide further transparency. Please monitor header responses to see where you are at with regard to limits.
In some circumstances where apps are highly impacting the stability of our platform, we reserve the right to enforce the limits at an earlier date. We will notify your listed contact via email if you are impacted. Additionally, we are planning to bring clarity to rate limits across our platform infrastructure over the next year, including paid apps.
We recommend all customers and partners ensure they're not exceeding the rate limits so that they do not get impacted at a later date.
Learn more about the header responses and read relevant FAQs about rate limiting adjustments for Jira here and Confluence here.
We're excited to announce that we’re expanding the early access program (EAP) for App Editions to more partners. Our goal this time is to engage additional partners who have previously expressed interest and those who have recently shown enthusiasm for developing editions.
This approach will ensure readiness when we activate the customer General Availability (GA) switch, also known as Milestone 3, in Q2 of calendar year 2025. We have a quick but involved path from EAP to General Availability and are looking for our early adopters to work with us along the way.
Learn more about the EAP participation criteria and requirements here. If you’re interested in participating in the early access program Round 2, please complete the attached form by Mar 3, 2025.
The following Forge Bitbucket modules now support view.createHistory() via @forge/bridge:
bitbucket:repoMainMenuPage
bitbucket:repoSettingsMenuPage
bitbucket:workspaceSettingsMenuPage
App developers can now utilize a path segment at the end of the page URL to maintain page history within their app. For more details, see https://developer.atlassian.com/platform/forge/apis-reference/ui-api-bridge/view/#createhistory.
Starting Feb 18, 2025 , we are introducing two updates:
New Billing System Field (newBillingSystem) in Marketplace reporting Licensing API
This field indicates whether a customer entitlement is on the new or old billing system.
Yes = Entitlement is on the new billing system
No = Entitlement is still on the old billing system
If case of free apps data this fields is not available
This is particularly important for Marketplace partners participating in App Editions, as it helps identify which cloud customers are on the new vs. old billing system.
The field will be maintained when a customer transitions between billing systems.
Dual Licensing Discount Reason Code in Marketplace reporting Transactions API
We have backfilled data for 62,000 transactions across various partner accounts to correctly display dual licensing discounts for records that were not displaying it earlier. These records were originally not displayed as DUAL_LICENSING but are now correctly labeled. To improve accuracy, we have enhanced our pipeline to map a specific internal reason code(which previously was a free text field) to dual licensing.
Partners can access these discounts via the Transactions API and read the following fields:
Discount Type: Manual
Reason Code: DUAL_LICENSING
This endpoint will be deprecated in 6months per our developer communications guidelines (August 18, 2025). For any third-party scripts that rely on this endpoint, use the PUT labels/:id endpoint instead (documentation here).
This endpoint is not referenced in our API documents or guides.
We’ve added two new Bitbucket Forge product events: avi:bitbucket:resolved:pullrequest-comment and avi:bitbucket:reopened:pullrequest-comment. You can use these events to invoke your Forge app function when a pull request comment is resolved or reopened. For more details see https://developer.atlassian.com/platform/forge/events-reference/bitbucket/.
Starting 15 Feb 2025, we will no longer accept a request body for the GET Issue Limit Report API. Any API calls made with a request body will result in a 403 error. If you are using a request body with this API, you will need to modify requests to avoid errors.
The API can still be used without a request body. By default, issues approaching the limit will be returned at the 80% threshold of the limit.
Option to relink data after app reinstallation is now being considered as a future improvement to the developer platform. If this is of interest watch this roadmap item for updates. See https://ecosystem.atlassian.net/browse/ROADMAP-107 for more information.
Multi-instance licensing will soon be available. This licensing model will enable Cloud Enterprise customers to be charged based on the number of unique users of the app across multiple instances, regardless of the number of product instances. We are aiming for Customer GA in May 2025. However, the capability to set multi-instance pricing for apps will be available on Feb 20, 2025.
To facilitate a seamless rollout of multi-instance licensing (MIL), we will block set pricing updates for three days (February 17th to 19th, 2025) prior to the multi-instance partner release on Feb 20, 2025. This pause will allow us to run migration and validate APIs effectively.
Important: During the three-day pricing freeze, new app submissions for approval will be blocked if they require pricing changes. However, apps with pre-set pricing can still be submitted for approval.
The @forge/api package has historically used node-fetch as the underlying HTTP client for making network requests. As of version 5.0.0, @forge/api will start using undici as the underlying HTTP client.
This change should fix the occasional occurrences of ECONNRESET errors (bug report).
Previous versions of @forge/api suffered from occasional ECONNRESET errors due to a bug in the way in-built https (which node-fetch depends on) manages keep-alive connections.
Moving to undici will also allow @forge/api to drop its node-fetch dependency (which has been requested here). However, in this version, node-fetch is still a dependency as we require it for a fallback mechanism. It will be removed shortly once the undici implementation is stable.
Note that this is a major version bump. The API interface has been slightly adjusted to support undici as the underlying client. For most use cases, this will not change anything, but if you depend on specific node-fetch types (e.g - you construct a node-fetch Request object which you pass in as the request) then this will no longer work.
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 have resolved several data inconsistencies in the Marketplace Reporting Licenses API caused by edge cases/scenarios supported on our new billing system.
As part of these corrections, we have updated key fields like maintenanceEndDate, licenseType, and status for approximately 10,000 active license records created or migrated to the new billing system across all Marketplace partners' data. Additionally, about 500 licenses have been corrected for fields such as hostEntitlementNumber, hostEntitlementId, parentProductBillingCycle, parentProductEdition, partnerDetails, unit_count, and tier
These changes will be deployed to production on Wednesday, February 12, 2025. You can retrieve updated records based on timestamp changes.
When a customer moved from annual to monthly billing, the maintenanceEndDate previously retained the annual end date. This has now been corrected to reflect the current billing period's end date.
In cases where customers canceled a paid period and created a new one, license records were not correctly updated.
Some inactive licenses were impacted, for which the data is also fixed. If needed, you can pull inactive license data to refresh your pipelines and ensure your records reflect these corrections.
Rate this page: