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’re announcing the deprecation of the V2 Reporting APIs on Atlassian Marketplace.
What’s changing
The Reporting APIs are now deprecated.
A six-month deprecation window begins immediately, and these APIs will be removed after May 31, 2026.
Refer to the updated documentation for V3 Reporting APIs to plan your transition.
What you need to do
Partners and developers should migrate to the V3 Reporting APIs to ensure continued functionality and support.
The requestRemote bridge API allows Forge apps to integrate directly with remote backends from the UI Kit and Custom UI applications via the Forge bridge.
This API is similar to invokeRemote, where requests include a Forge Invocation Token (FIT) as a bearer token in the authorization header; however, the request is not an official invocation that passes through the Forge platform. Therefore, requestRemote will not include OAuth tokens, even if configured for the remote, and will not be reflected in invocation metrics in the Developer Console.
For more details, see requestRemote.
The new Rolling releases feature is now available through Forge’s Early Access Program. To join the EAP, please complete this sign-up form.
Rolling releases let you decouple app permissions from app code, allowing code updates to be deployed independently of permission changes. This means your app can be upgraded to a new code version even if admins haven't approved new permissions yet, addressing the version fragmentation problem .
With rolling releases, developers can ship code improvements and bug fixes more frequently without being blocked by permission approval processes, while customers benefit from staying on current, secure versions. Admins maintain control by approving permission changes separately from code updates.
For more information on this feature, refer to the RFC-106: Future of Forge versioning - Permissions post.
EAP scope:
Available for Forge apps on Jira and Confluence only
Code-only upgrades via forge install --upgrade code
New Permissions SDK for runtime permission checks (@forge/react and @forge/api)
Current limitations:
Auto-upgrades not yet supported
Some upgrade paths unavailable (e.g., upgrading from free to paid)
The Jira full page module enables developers to build fully custom, chromeless app experiences within Jira Cloud, hosted directly on Forge.
This preview is accessible via the following URL: https://<tenant-name>/forge-apps/a/<app-id>/e/<environment-id>/r/<route-prefix>/<app-route>
For more information, see the Jira full page (Preview)
We are deprecating the forge webtrigger command as a leaf command in favour of 3 new sub-commands for managing webtriggers.
forge webtrigger create for creating a webtrigger URL
forge webtrigger list for listing existing webtrigger URLs
forge webtrigger delete for deleting a webtrigger URL
The forge webtrigger and forge webtrigger create command will function exactly the same until such time as the forge webtrigger command is no longer supported in May 2026, in line with our deprecation policy.
You can now configure the Forge Content Byline Item module to open in a modal instead of a pop-up. The modal supports both standard and full-screen sizes, giving you more flexibility in how your content is displayed. This can be done by using viewportContainer: modal in your manifest.
For more information, see our documentation.
What’s new:
Multi Year Billed Annual allows customers to commit to multi-year Marketplace App subscriptions with annual billing, instead of paying the full term upfront. This aligns with Atlassian’s parent product billing and meets enterprise customer demand for flexibility and predictability.
Key points detailing the MYBA transactions is covered in the attached QRG
Action required:
No action needed from partners at this time. Reporting enhancements are planned for Q1 CY 2026.
Link to the Quick Reference Guide is provided here: https://atlassianpartners.atlassian.net/wiki/spaces/resources/pages/1109983239/Marketplace+Partners+Multi-Year+Billed+Annual+MYBA+Quick+Reference+Guide
bitbucket:projectSettingsMenuPage module is now available. You can use this module to build a custom project settings page. See the project settings menu page for details.
bitbucket:repoCodeFileViewer module is now available. You can use this module to build a custom file viewer. See the file viewer page for details.
We've introduced the bitbucket:workspaceGlobalPage module for Forge apps. Your app will now appear as a menu item in the Apps section of the Bitbucket workspace navigation, displaying your custom page content when users select it.
To use this module, update your app’s manifest to include bitbucket:workspaceGlobalPage.
For implementation details and examples, see the bitbucket:workspaceGlobalPage module reference.
We are introducing new Directory, User, and Group APIs. These APIs are designed to work seamlessly with both centralized user management experience and the original user management experience, providing enhanced flexibility and control for managing users and groups within your organization.
Get directories in an organization
Retrieve a paginated list of directories in your organization that match the supplied parameters.
Get users in an organization
Retrieve a paginated list of users in your organization that match the supplied parameters.
Get user role assignments
Retrieve a paginated list of role assignments for a user that match the supplied parameters.
Suspend user access in directory
Temporarily suspend a user’s access in a directory, removing their access to apps.
Restore user access in directory
Restore a user’s access in a directory, allowing them to access apps again.
Remove user from directory
Remove a user from a directory to revoke their access and remove them from the directory.
Get count of users in an organization
Retrieve the count of users in your organization that match the supplied parameters.
Get user stats
Retrieve user statistics for your organization.
Get groups in an organization
Retrieve a paginated list of groups in your organization that match the supplied parameters.
Create group
Create a new group in a directory to manage app access and permissions for multiple users.
Get group details
Retrieve detailed information about a specific group.
Delete group
Delete a group from a directory if it is no longer needed.
Get group role assignments
Retrieve a paginated list of role assignments for a group that match the supplied parameters.
Grant access to group
Assign a role to a group, granting all members the same role.
Remove access from group
Revoke a role from a group, removing app access from all members.
Get the count of groups in an organization
Retrieve the count of groups in your organization that match the supplied parameters.
Get group stats
Retrieve group statistics for your organization.
Add user to group
Add a user to a group, granting them the same app access and permissions as the group.
Remove user from group
Remove a user from a group, revoking any app access and permissions granted by the group.
We’re sharing a guide that explains the benefits of using OpenSearch as an alternative to the default Lucene search platform in Jira Data Center. By using OpenSearch instead of Lucene, you’ll be able to speed up you Jira, reduce the number of required Jira nodes and use cheaper hardware.
The guide covers:
Key differences between OpenSearch and Lucene.
Benchmark results that show OpenSearch delivers faster search and better scalability.
Guidance on when and why to switch, with further configuration steps.
OpenSearch in Jira
OpenSearch in Jira isn’t just about searching — it supports everything you do, from loading boards and viewing backlogs to generating reports and working with issues. Because so many core actions rely on search, OpenSearch’s speed, consistency, and reliability have a direct impact on your team’s productivity and experience. Discover our hardware recommendations for OpenSearch
We are re-enabling automatic Connect to Forge migrations, following the temporary pause which started on Sep 23, 2025
Apps which were impacted by or published to the marketplace following this pause will now see Connect installations progressively move to Forge as long as they meet the minor update criteria. The pace of the migration will be dynamically adjusted to ensure high throughput and reliability of the pipeline as we clear these pending updates.
The new Forge rovo.open method is now available through Forge’s Early Access Program. To join the EAP, please complete this sign-up form.
The rovo.open method allows you to open the Rovo chat sidebar and create a new conversation with either a default or specified Rovo agent.
For more information, see the Rovo documentation.
Forge LLM is now available through Forge’s Early Access Program. This feature allows Forge apps to integrate with an Atlassian-hosted large language model (LLM) capability, meaning that apps that use the feature will still be eligible for the Runs on Atlassian program.
At launch, only the Claude model family is supported. Support for additional model families will be added soon.
To join the Early Access Program, complete the sign-up form.
For more information, see the Forge LLM documentation.
Participation in the EAP may be subject to limitations or eligibility requirements.
Rate this page: