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.
Forge SQL is now available as an Early Access Program (EAP) feature, allowing developers early access to test SQL hosted storage functionality for their Forge app and provide feedback.
Refer to Forge SQL documentation for more information about the EAP.
To signup to the EAP, please use the request form.
We are deprecating the synchronous Convert content body v1 REST API in Confluence Cloud on Apr 4, 2025. The POST /wiki/rest/api/contentbody/convert/{to} endpoint will be removed at that time.
By using asynchronous content conversion APIs instead, developers can avoid lengthy rendering timeouts and page load failures that can occur when the Convert content body API is used to render large, complex content.
Developers can use the Asynchronously convert content body endpoint for single conversions and Create asynchronous content body conversion tasks in bulk endpoint for multiple conversions.
What’s new in Confluence 9.1?
Support for languages and special characters in page URLs
Code Block macro enhancements
Single click to copy heading links
More secure login with two-step verification
New REST APIs
Password policy
Microsoft Entra ID integration
Retention rules performance and reliability improvements
Lots more!
To learn more, see [Confluence 9.1 Release Notes](https://confluence.atlassian.com/display/doc/confluence+9.1+release+notes ).
[Download the latest version](https://www.atlassian.com/software/confluence/download-archives )
This release doesn’t support Server licenses. If you have a Server license, [check out your options for upgrading] (https://www.atlassian.com/blog/announcements/server-support-5-month-countdown ).
As a workspace admin, you can now access the direct distribution link for a Bitbucket Forge app installed on your workspace.
To do this, go to Workspace settings > Installed apps and then select the Manage link next to the app.
We’ve added a new REST endpoint that allows you to fetch configurations for multiple Forge custom fields at the same time.
We’re pleased to announce a preview release of support for a new location via the UI modifications extension point: Issue transition.
It’s the third Jira location to be supported, following the initial support for the Issue create modal and Issue view.
Documentation specific to the Issue transition is available under this link. The supported fields and methods are listed here.
To assign a UI modification to the Issue transition context, you need to pass a viewType equal to IssueTransition while creating or updating the UI modification. See more details in our REST API docs.
At the same time, we’re ending the UI modifications Issue transition Early Access Program. Your apps developed during the EAP will continue to work.
The UI modifications (UIM) module now supports the people field on the Issue view.
The complete list of supported fields for the Issue view is available here.
Global fetch, included by default in Node.js 18 and later versions, now works in the Forge Node.js runtime. You now have the choice of global fetch, the Forge-specific fetch module, or the https module when making egress calls.
Note that you will not be able to provide a custom dispatcher or set a global dispatcher for the fetch call, as the runtime implementation will override it.
The UserPicker component is now supported for Bitbucket Forge apps. Users available for selection are scoped to the current workspace users.
To reduce the need for app developers to maintain a list of Atlassian sites in egress declarations, Atlassian product API redirects are now treated as internal traffic by the Forge Node.js runtime. As a result, they no longer require egress declarations in your app's manifest. Atlassian has addressed all known instances of redirects, allowing you to remove egress declarations for internal domains like api.media.atlassian.com.
Developers should review their app manifests and remove any unnecessary egress declarations for internal domains.
If you find any internal redirects that are not handled automatically, please contact Atlassian support so that they can inform the product team.
As discussed in RFC-45, there are upcoming changes to Jira and JSM Cloud navigation. As a result, you may want to trial the navigation changes and assess how your apps will adapt to the proposed changes.
To participate in the upcoming Early Access Program (EAP), please provide your Jira/JSM test instance details via the EAP waitlist form. This will give access to the EAP version of the new look of Jira and JSM. We will notify you about your enrollment once the EAP launches on October 14, 2024.
This EAP will give the opportunity to test the navigation changes, understand the direction Jira products are heading in, and share your feedback. As part of EAP, we’ll set up a dedicated group on CDAC where you’ll be able to discuss these changes. Please note that the designs in the EAP are not final, so you are NOT expected to make any changes to your apps during the EAP.
Forge custom fields on the Issue view will render inline in edit mode by default from Apr 1, 2025 (6 months from this announcement).
During the transition period, you can use the isInline property in the app manifest to enable the inline edit mode for apps built with UI kit and Custom UI. You can read more about custom field rendering in the Forge documentation. After the deprecation period, rendering fields in the modal will be possible only using the dedicated UI kit modal component or Forge bridge API.
The marketplace license report has been enhanced to accurately handle some of the edge cases with respect to license status. Moving forward, instead of the created date of licenses, we will take into account the maintenance start and end dates to display their status in our license report. This will especially help us in handling some of the edge cases such as pre billed licenses.
Partners will now be able to the correct point in time status of licenses in cases when multiple period of the same licenses are bought but at different times.
What are the changes in license report some partners might see:
Due to the presented change in our logic, while most of the data will remain the same, some partners might observe some of the licenses in their reports move from expired to active. These are licenses which have an edge case such as a pre-billed period that was bought before another period of the same license was paid for etc.
In the latest version of @forge/react, we're releasing a new UI Kit product-specific Jira component, CustomFieldEdit, which can be used to offer inline editing for Forge custom fields.
For more information on this component, see the component documentation.
To update your UI kit app to the latest version, run the following command in your project directory:
npm install --save @forge/react@latest
The prompt property of a Rovo agent (Preview) module now supports a relative path to a declared resource.
In the Forge CLI version 10.6.0(or higher), you no longer need to provide the entire prompt as a string in the manifest.
For more information, see the prompt as a resource example.
To install the latest version, in your terminal, run: npm install -g @forge/cli@latest.
Rate this page: