Last updated May 7, 2025

Atlassian developer changelog

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.

7 May 2025

Announcement Updates to Event Type Logic in Marketplace Reporting

Marketplace Platform

Based on internal analysis and bug reports, we had identified a couple of issues in the identification of type for license events in Marketplace reports:

  • For some cases, converted events were not flowing due to being considered as non-converted and vice versa.

  • For some cases, churn events were getting tagged as renewal and vice versa.

As part of this fix, we are adding additional checks on start and end dates to find and categorise events accurately. In terms of impact to reports:

  • License events report - Counts in each metric might differ due to change in type.

  • Churn report - Based on events getting added or removed from churn type, number and percentages will change.

  • Renewal report - Based on events getting added or removed from renewal type, number and percentages will change.

  • Conversion report - Based on events getting added or removed from conversion type, number and percentages will change.

In order to facilitate a smooth transition, we are updating historical records from May 1, 2025 for now. In the coming weeks, we will be backfilling data from May 1, 2024 to give a more accurate historical view.

Note: This change only impacts the events. Licenses and Transaction are not impacted

More details

In order to help partners understand the change better, we have added examples in the below table highlighting the change and the associated reason for the change.

New Event Type

Old EventType

Reason for Change

Renewal

Churn

  • Despite the customer renewing the subscription for the next period, churn event was added instead of renewal in some cases.

Churn

Renewal

  • Despite a time gap between evaluation and start of new subscription, the license event for renewal was added instead of churn.

Converted Evaluation

Non-Converted Evaluation

  • Despite the customer starting a new subscription post evaluation completion, converted event not getting added in some cases.

Non-Converted Evaluation

Converted Evaluation

  • Despite a time gap between evaluation and start of new subscription, the license event for converted was added.

6 May 2025

Announcement Cross-context apps are available as part of an EAP

Forge - Core Platform (excludes product REST APIs)

Cross-context apps are now available through Forge’s Early Access Program (EAP). This EAP is designed to allow developers to try out the experience of creating cross-context apps.

Cross-context apps are Forge apps that can be installed in and function across various contexts. For this EAP, the supported contexts are Confluence, Jira, and Compass. This means you can create an app that uses modules and calls APIs across these contexts.

To be able to access cross-context app functionality, you must sign up to participate in this EAP. You can sign up using the Forge cross-context apps EAP form.

See https://ecosystem.atlassian.net/browse/ROADMAP-106 for more information.

5 May 2025

Announcement Updates to Marketplace revenue share rates: 2026

Marketplace Platform

Update #1: We are introducing a new revenue share incentive to help partners establish successful apps on Forge.

  • Beginning 1 January 2026, partners will pay 0% revenue share for eligible Forge earnings, up to $1 million in lifetime Forge revenue. Lifetime revenue is calculated across all Forge apps owned by a partner, from the date eligible apps begin earning revenue on the Marketplace. This is a temporary incentive, and may change in the future.

Update #2: We are also introducing new Marketplace revenue share rates that will go into effect 1 January 2026. Percentages reflect the commission amount retained by Atlassian, with remaining earnings paid out to the partner.

  • The rate for Connect apps will increase to 20% and subsequently increase to 25% on 1 July 2026.

  • The standard rate for Forge apps will increase to 16% and subsequently increase to 17% on 1 July 2026.

More details

Announcement Update on Partner Discount Amount & Discount Array Fields Rollout

Marketplace Platform

We’re currently reviewing the changes announced to the partner discount amount and discount array fields, which were originally scheduled to go live on 5 May 2025. To ensure a smooth rollout and allow time to resolve queries, we are extending this timeline by 3 weeks.

At this time, no changes will be made to the existing behavior. We will share a revised go-live date and further details once our review is complete.

Thank you for your patience and understanding.

  • Originally Announced On: 30 Apr 2025
    Original Go-Live Date: 5 May 2025

  • Related Documentation: QRG

2 May 2025

Announcement Marketplace V3 Reporting APIs are now available for review

Marketplace Platform

While version 3 of the Marketplace Reporting APIs is still under development, we’re releasing the documentation for these reporting APIs early to help you prepare for the upcoming changes. This release includes a preview of the API documentation schema and examples of API requests and responses.

To ensure smooth transition with the upcoming changes, we recommend to review the API documentation to understand and prepare for the upcoming changes.

More details

Here are some helpful suggestions for you to consider:

  • Transition planning: Based on this documentation, it may be helpful to assess the bandwidth required for these changes and incorporate them into your roadmaps. Reviewing this documentation could provide a clearer understanding of the new APIs and help you accurately estimate the efforts involved in the transition.

  • Project planning: Consider preparing your execution plans and project plans so that you’re ready to hit the ground running once the APIs become available.

  • Staying informed: Keeping an eye out for upcoming communications from the Marketplace team can help you stay updated on timelines. Look out for updates via changelogs, enhancements to the quick reference guide on the Partner Portal, DAC, and other channels.

1 May 2025

Removed Deprecated REST API V1 endpoints removed from service

REST API - Confluence Cloud

As of today May 1, 2025, the following deprecated Confluence REST API V1 endpoints have been removed from service. This means requests to these endpoints will result in a 410 error response. These endpoints have also been removed from REST API V1 documentation.

More details

Added Forge actions module can now be used by customer-created Rovo Agents

Forge - Core Platform (excludes product REST APIs)

Actions from Forge apps can be made available to customer-built Rovo agents by adding the read:chat:rovo scope to the permissions in your manifest.

This enables agents created by customers to utilize these actions.

More details

Why the new scope?

The additional scope is needed because customer-built agents may access data that your app can't otherwise reach. This data can be provided as input to your action through a Rovo chat.

30 April 2025

Removed Removed a subset of Confluence page extension points

Connect - Confluence Cloud (excludes Confluence REST APIs)

As of today Apr 30, 2025, the following Connect extension points will be removed from Confluence Cloud (see our deprecation notice from six months ago here):

  • page.metadata.banner

  • atl.page.metadata.banner

  • system.content.button

  • atl.editor.savebar

  • system.editor.precursor.buttons

  • system.content.metadata

Also, the following Connect extension point will no longer render a UI component on Confluence pages, but can still be used for running background scripts only.

  • atl.footer

Note that we are gradually rolling out this removal to customers. That means, in some instances you may still see the above extension points in Confluence Cloud. Understand that they may be removed at any point.

Developers using any of the removed Connect extension points should actively consider (if not already) transitioning to the following available extension points. This move is crucial to ensure app and experience continuity for end-users.

  • Forge

    • confluence:contentBylineItem

    • confluence:contentAction

    • confluence:contextMenu

  • Connect

    • system.content.action/secondary

    • contentBylineItem

    • system.content.action

    • system.content.action/primary

    • atl.general

    • system.content.action/modify

    • page.view.selection/action-panel

    • system.content.action/marker

Note that these changes only apply to extension points available when interacting with Confluence pages and live docs. Any extension points beyond the context of a Confluence page or live doc are not impacted.

More details

For more details on this deprecation and migration guidance, see our deprecation notice from six months ago here.

Removed Upcoming Change to /rest/2/addons API - User Count Field

Marketplace Platform

Starting May 12, 2025, we will update the /rest/2/addons Get apps API to improve data privacy practices on the Atlassian Marketplace.

Today, this API shares the total number of users for all apps, even for apps you do not own. To prevent unintended exposure of app metrics, we will be masking this value.

What’s changing?

  • The "user count" field will no longer return actual numbers.

  • Instead, it will always return -1.

Important Dates

  • Change Effective: May 12, 2025

Action Required
No action is needed if your systems can handle a -1 value.

Announcement User-based billing for Forge apps

Forge - Core Platform (excludes product REST APIs)

User-based billing is now available as part of its first milestone release. This new billing model enables app developers to build, deploy, and test an app via Forge CLI on non-production environments. Customers can license and pay for apps based on a specific subset of users within a product instance rather than for all users.

Details:

  • This feature is exclusive to Forge apps, including Forge apps with the Connect module.

  • Marketplace Partners can choose between user-based or instance-based billing, allowing them to adopt a billing model that best suits their app's requirements and business strategy.

  • This flexibility supports a more tailored pricing strategy.

To adopt the user-based billing model for your new or existing app, implement the necessary code changes as detailed in the developer documentation.

The milestone releases to follow for user-based billing will enable app publishing, pricing setup, app revision, and app approval to be available on Atlassian Marketplace.

Announcement UI experience Changes to "Edit Version" Flow

Marketplace Platform

We are updating the look and feel of the "Edit Version" flows in the partner portal. Edit version flow is essential to update version information for an app version on the Atlassian Marketplace.

The functionality of the different components of the edit version flow will remain the same; and the updates are limited to visual changes only.

Initially, a small percentage of partners will gain access to these updates, starting May 5, 2025, with a phased rollout, planned for all partners to completed by May 13, 2025. For more information, please refer to the Quick Reference Guide(QRG) here.

Announcement Upcoming changes to the Partner Discount Amount Field in Marketplace Reporting

Marketplace Platform

The following changes are to the discounts field on Marketplace Transactions reporting UI and API.
Effective May 5, 2025, for all transactions created on or after Jun 1, 2021, the partnerDiscountAmount field will be removed and replaced from the Marketplace transactions APIs and UI.

The Discount Array (available on API) values will now be available on the UI for Marketplace Transactions reporting for all paid and refund transactions with a sale date on or after Jun 1, 2021.

The partnerDiscountAmount will provide the discount amount for paid transactions before Jun 1, 2021.

For more information on these changes and visual examples, please refer to the QRG here.

Added Background scripts is now GA

Forge - Core Platform (excludes product REST APIs)
Forge - Confluence Cloud (excludes Confluence REST APIs)

We’ve released a new Background Scripts module, which enables apps to run in the background of a Confluence page. See Confluence Background script for more information.

You can use background scripts to replace the atl.footer extension point in Connect.

More details

To use the new modules, you must first update the Forge CLI:
npm install -g @forge/cli@latest

Added Async webhooks are now default in Jira Data Center

Jira Data Center
Jira Service Management Data Center

Starting from Jira Data Center 10.0.0, asynchronous webhooks are now the default and only option. This update significantly improves the user experience by processing webhooks through a dedicated thread pool, rather than tying them to the user request. Previously, in Jira 9 and earlier, webhooks were processed synchronously, with the most computationally intensive work performed during the HTTP request.

Environments with exceptional webhook usage in both Jira 9 and 10 might exceed the guardrails set by the default parameters. You can customize these limits to better suit your organization’s needs. We recommend testing the asynchronous webhooks within your staging environments before a final upgrade. If you experience any issues, check our list of known problems or reach out to our support team.

Explore how to tune webhook performance parameters in Jira

Early Access Custom Metrics are now in EAP

Forge - Core Platform (excludes product REST APIs)

Forge custom metrics are now available in EAP.

With custom metrics, you can track specific events, actions, and measurements within your Forge app. This enables you to monitor business-specific KPIs and instrument critical paths within your app code.

To participate, sign up using the EAP form.

For more information about the metrics, refer to Monitor custom metrics (EAP).

Rate this page:

OSZAR »