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.
We recently introduced two new Users and Groups REST APIs that are available to all customers. These APIs replace two existing REST APIs, which we’re removing in June 2027.
The following APIs will stop working after June 30, 2027:
Users
Get users in an organization: GET/v2/orgs/{orgId}/directories/{directoryId}/users
Groups
Get groups in an organization: GET/v2/orgs/{orgId}/directories/{directoryId}/groups
We recommend you update your workflows to the new APIs as soon as possible to avoid any disruption.
What’s changing?
As previously announced in CHANGE-3120, usage of asynchronous Forge functions is now billed in line with Forge platform pricing.
Billing will be enabled progressively for all apps commencing Jul 2, 2026, with charges commencing in invoices issued from Aug 1, 2026 onwards.
Roll-out in progress
This is a progressive roll-out that is currently in progress. This changelog entry will be updated once the roll-out is complete.
What do I need to do?
No action is required. However, you should review your forecast usage in the Usage and Charges section of the Forge developer console.
We’re introducing two new Users and Groups APIs available to all customers:
Search for users in an organization (v2)
Return a page of users in an organization that match the supplied parameters.
Search for groups in an organization (v2)
Return a page of groups in an organization that match the supplied parameters.
These APIs are provided to replace some recently deprecated APIs.
Use Search for users in an organization (v2) instead of:
Use Search for groups in an organization (v2) instead of:
Forge Rolling Releases is now available in Preview. This feature allows app developers to continuously deploy code updates to all eligible installations, even when new permissions are involved.
Getting started:
Add enforcement: app-managed to your manifest's permissions section
Implement the Permissions SDK to check permissions at runtime
Run forge deploy: a rollout will start automatically, or use --no-rollout and manage rollouts from the Developer Console
The new rollouts tab in the developer console is progressively rolling out over the coming days. If you don't see it yet, check back shortly as access is being expanded incrementally.
For full details, see https://developer.atlassian.com/platform/forge/rolling-releases/.
This is a Preview release of the Atlassian Rovo MCP v2. This endpoint is considered early access and will be subject to change; including the MCP tools and their responses.
We’re excited to share that a preview release of our new Atlassian Rovo MCP is now available for early access. This release introduces some significant changes including:
Dozens of new tools abstracted behind discover and execute tools
New and improved Confluence tools, introducing support for attachments, whiteboards, databases and more.
Reduced default tool exposure, reducing context window consumption by >50%
Optimised tool responses, substantially reducing context window consumption from tool invocations
The preview endpoint is now available at https://mcp.atlassian.com/v1/mcp/preview and can be utilised today.
The new customerServiceManagement:crmImport Forge module is generally available from June 30, 2026.
What's changing
This module allows you to add an item under the Manage dropdown on the Customers, Organizations, and Products pages within the customer directory of the Customer Service Management (CSM) app. When a user clicks the item, your app renders content inside a modal dialog.
This extension point is specifically designed for apps that import customer context data from external CRM systems into Customer Service Management, providing a dedicated UI entry point for these integrations.
What you need to do
To start using this module, refer to the customerServiceManagement:crmImport manifest reference for technical configuration and schema details.
What is changing?
We previously announced that usage of asynchronous Forge app invocations will become billable on Jul 1, 2026.
To compensate for the inclusion of these functions in your billable usage, we are doubling the free usage allowance for Forge functions from 100,000 GB-seconds per month to 200,000 GB-seconds per month.
The increased allowance will be rolled out progressively, for:
Newly-created Forge apps starting on Jun 29, 2026
Existing Forge apps starting on Jul 1, 2026
The increased allowance will apply for all apps for the billing month of July 2026.
What do I need to do?
No action is required. The increased allowance will be applied automatically.
We recommend reviewing your Forge functions consumption in the Forge Developer Console's Usage and Charges section to understand how this change affects your apps before billing begins.
Forge Realtime has moved from Preview to General Availability. You can now use Realtime in production apps with full platform support and operational readiness.
What's changing
Distinct subscriber and publisher roles: You can now issue tokens that grant only subscribe or publish access to a channel using the new permissions argument in signRealtimeToken. This lets you restrict publishing to your backend while granting subscribe-only access to frontends. Tokens without explicit permissions remain with full access.
Rate limits: Limits of 50 operations per app installation per second are now enforced. See Realtime limits and error messages for details.
What you need to do
Run the following commands in your app directory to install the latest versions of these packages:
npm install @forge/bridge@latest
npm install @forge/realtime@latest
The global:ui module is now available through the Early Access Program (EAP). This module allows your Forge app to have its own end-to-end experience within the Atlassian platform, independent of specific product contexts like Jira or Confluence.
What's changing
The global:ui module enables your app to:
Deliver a full-screen experience with side navigation that you control and top navigation provided by the Atlassian platform.
Appear in the Atlassian app switcher, allowing users to reach your app from anywhere in the platform.
Connect to one or more Atlassian apps through multi-app compatibility, and optionally surface data across them.
Build on platform capabilities such as Teamwork Graph, Forge Agents, Rovo Search, and Rovo Chat.
What you need to do
To start building apps with the global:uimodule:
Join the EAP by completing the sign-up form.
Review the detailed documentation.
We wanted to share a few updates on the trust front:
Atlassian Enterprise Certified — our new trust program
We've heard your feedback, and we're excited to announce that our new trust program is officially named Atlassian Enterprise Certified. This badge will recognize apps that meet rigorous enterprise standards for security, reliability, privacy, accessibility, and responsible AI — going beyond the baseline cloud standards required of all Marketplace apps. We plan to begin rolling out the program in Q3 CY2026 and phase out the Cloud Fortified Apps program by the end of the year.
New trust filters and verified indicators on the Marketplace
We're introducing enhancements that make it easier for customers to evaluate apps against their security, privacy, compliance, and procurement requirements.
New filters for faster shortlisting
Today, customers can filter Marketplace apps by Runs on Atlassian and Cloud Fortified. We're adding filters for:
SOC 2
ISO 27001
Penetration testing
Bug bounty
Partner trust center
Standard Legal Agreement
Verified indicators on the Privacy & Security tab
We're also adding a blue verified-tick icon to selected Privacy & Security tab fields, helping customers distinguish Atlassian-verified information from partner-attested responses at a glance.
At launch, verified indicators will appear on:
App REST APIs
Integration permissions with Atlassian apps
Marketplace Security Bug Bounty Program participation
Atlassian trust programs
We plan to expand verified indicators to more fields over time.
What you need to do
The new filters and verified indicators draw from information Atlassian already holds or that partners have already provided through existing Marketplace processes and Privacy & Security tab responses.
That said, to ensure your apps show well in trust-based evaluations, we recommend reviewing your Privacy & Security tab to confirm that your security, privacy, and compliance details are complete and up to date.
Forge Object Store billing will be rolled out in stages starting June 29, 2026. While most existing apps won't see changes until July, new apps created during the transition window will have billing enabled immediately.
What’s changing
Existing Forge apps: Object Store becomes a billable capability starting from your billing cycle on July 1, 2026. You will not see charges for Object Store usage before this date.
New Forge apps: For any apps created on June 29, 2026 or June 30, 2026, Object Store is billable immediately upon creation. Charges will apply if your usage exceeds the free quota during this window.
What you need to do
Review the Forge pricing guide to understand the free quota and pricing for Object Store.
If you are planning to create new apps on June 29 or 30, factor in the immediate billing activation for Object Store.
For more context on the Object Store release, see the Forge Object Store is now in Preview changelog entry.
We've added new convenience components and hooks for routing in UI Kit. These are now available in Preview in the latest version of @forge/react.
Routing is available in any full-page module and enables your app to manipulate the current page URL using a familiar API.
What’s changing
You can now use the following components and hooks to manage navigation within your Forge apps:
What you need to do
To use these new features, update to the latest version of the @forge/react package. In your terminal, run the following command from your project directory:
npm install --save @forge/react@latest
For implementation details and code examples, refer to the documentation links above.
The Status Search API now exposes a new optional includeGlobalStatuses query parameter. When set to true on a project-scoped query, the response includes global statuses (statuses not tied to any specific project) alongside the project's own statuses. Defaults to false. This parameter is only relevant for project-scoped queries.
This supports ongoing work to allow team-managed workflows to use global statuses, giving admins more flexibility and consistency across projects.
Bitbucket Forge page modules will now have their menu items grouped into sections by their app. This change improves the organization of the Bitbucket navigation menu, making it easier for users to identify which menu items belong to specific apps.
What’s changing:
The following modules will now have their menu items grouped by app:
What you need to do:
No action is required from you. If your app uses these modules, their menu items will automatically be grouped. You can see the linked documentation pages for example screenshots of the new grouping behaviour.
We've added a new Forge module (devops:securityInfoProvider) that lets your app send security information (such as vulnerabilities and security containers) to Jira and associate it with issues. This is now available in preview.
What's new
The devops:securityInfoProvider module surfaces your app's security data directly in the development panel of Jira issues. Apps can write and delete security information using the https://developer.atlassian.com/cloud/jira/software/rest/ via the requestJira function.
To register a provider, declare the module in your manifest.yml and configure the required endpoint handlers:
fetchWorkspaces: returns the list of workspaces available to the user
fetchContainers: returns security containers within a workspace
searchContainers: searches containers matching a query
Two optional lifecycle hooks are also available: onEntityAssociated and onEntityDisassociated, invoked when a container is linked or unlinked from a Jira entity.
Important behaviour to note
When a user uninstalls your app, all security data your app sent to Jira is deleted after a grace period.
There is currently a limitation, where your Forge app must define a Connect app key in order to be able to link workspaces. See https://jira.atlassian.com/browse/ECO-1602
Get started
See the https://developer.atlassian.com/platform/forge/manifest-reference/modules/jira-software-security-info/ for the full manifest schema, example requests/responses, and property details.
Check out this tutorial on building a Security Information Provider app in Forge: https://community.atlassian.com/forums/Jira-articles/Building-a-Jira-Security-Info-Provider-app-in-Forge/ba-p/3254780
Rate this page: