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.
Bitbucket Data Center 8.19.2 and Bitbucket Data Center and Server 8.9.13 bug fix releases are available now!
To see the issues resolved in these bug fix releases, go to:
Dynamic Pipelines for Bitbucket Cloud are now generally available.
Dynamic Pipelines allow you to utilise Forge functions to augment and modify CI/CD workflows at runtime, implementing sophisticated dynamic logic that will enable unparalleled levels of CI/CD control.
For more info, check out the announcement post.
The first Data Center-only release of Crowd is now available. Explore Crowd 5.3.0
The prototype version of the new login experience for Data Center is now available. Download this .jar file and test it against your apps to identify any potential conflicts.
This prototype is intended purely as a test to check how the new two-step verification experience affects your apps' functionality and determine if any changes are necessary. The scope, functionality, API, quality, look and feel, and security level of the prototype aren’t representative of the final solution.
The production version of two-step verification will be developed separately from the prototype version but the fundamental technical concept will remain unchanged.
This prototype is for testing purposes only. Don’t install it on production environments.
To install the app, follow https://confluence.atlassian.com/upm/installing-add-ons-273875715.html#InstallingMarketplaceapps-InstallaDataCenterorServerapp. In case the upload is disabled, check https://confluence.atlassian.com/jirakb/how-to-re-enable-plugin-upload-1364557898.html.
Watch this video guide for more information on the prototype and how to test it.
Starting from Jun 1, 2024 , the send migration progress endpoint will reject requests containing more than 65,536 characters on the message field.
Forge app names can now be up to 60 characters when:
Set via the Forge CLI, or
Updated in the Developer Console.
Previously, Forge app names were limited to 50 characters, while Marketplace listing names could be up to 60 characters in length.
Custom merge checks are now generally available in Bitbucket Cloud. For full details on all the changes coming as part of this release, refer to our deep-dive blog post.
This release includes the following changes:
Repository Admins:
Custom merge checks can now be configured as either “recommended” or “required”.
“Recommended” checks will provide feedback to the PR author if failing, but will not block the merge.
“Required” checks will block the PR if failing.
As per existing classic merge checks, setting custom merge checks as “Required” is only available in premium workspaces.
Pull request reviewers/authors:
Classic merge check and custom merge check results have been consolidated into a single UI Element on the Pull Request screen.
The UI behaviour of classic merge checks has been updated to be consistent with the design of custom merge checks.
Failing “recommended” merge checks will be visible on the check result sidebar card with a unique visual indicator.
Custom merge checks that run “on-merge” have been more clearly distinguished from conventional “pre-merge” checks on the checks result sidebar card.
The new categories and keywords, as part of the new store experience, will start rolling out end of April. In order for customers to discover your apps via the new categories and keywords, please be sure to tag your apps accordingly as soon as possible.
You can tag your apps to the new categories and keywords in your App Details page. For more information, please visit this link.
Introducing new REST API endpoints to facilitate the management of pull request tasks. For further details, please refer to the documentation:
We are making changes to the responses of a number of endpoints within the REST API’s for Assets in Jira Service Management cloud. These endpoints include in their response body the ID for an object attribute value. This ID is now deprecated and will be removed (see https://community.developer.atlassian.com/t/object-attribute-value-id-will-be-removed-from-all-assets-rest-apis/79259 for details of all effected publicly documented endpoints).
This change will be made on or after 30 Sept 2024 for our publicly documented API endpoints. For any undocumented API endpoints that include this ID in their response body the change will be made sooner, on or after 1 Jul 2024.
Following our recent preview release of Forge UI Kit 2, we're excited to announce that UI Kit 2 is now generally available. With this release, UI Kit 2 has been promoted as the latest version of UI Kit and will now be referred to as simply UI Kit.
For more detailed information on using UI Kit components to design and build apps, please refer to our UI Kit components documentation.
The latest version is supported within the following products:
Bitbucket
Compass
Confluence
Jira
Jira Service Management
See the following documentation to know how to upgrade to the latest version of UI Kit:
With Forge UI Kit now generally available, we’re releasing a new major version of the Forge CLI.
Here’s a summary of the CLI changes:
We’ve renamed UI kit 2 (Preview) template option to UI Kit.
We’ve removed the original UI kit template option. This means no new UI Kit 1 apps can be created with this latest version.
To install the latest version, in your terminal, run: npm install -g @forge/cli@latest
Though we highly recommend creating new apps using latest UI Kit version, you can still do the following activities:
Deploy and install existing UI Kit 1 apps.
Create new UI Kit 1 apps as long as you remain on version 7.1.0 of @forge/cli.
We have now added the following rate limits to WebTrigger GraphQL operations:
createWebTriggerUrl - 500 requests / 60 seconds
This include usage of the webTrigger.getUrl method from the @forge/api NPM package.
deleteWebTriggerUrl - 500 requests / 60 seconds
webTriggerUrlsByAppContext - 1000 requests / 60 seconds
Each limit is applied with the following dimensions: appId + site + forge app environment + userId.
For more information, see https://developer.atlassian.com/platform/atlassian-graphql-api/graphql/#rate-limiting.
As part of our ongoing commitment to security, we’ll cease publishing development releases of Data Center product artifacts to the Atlassian Maven repository. Moving forward, only artifacts used in the Early Access Program (EAP) and final product releases will be available to maintain the highest level of security for our customers.
The UI modifications (UIM) module now supports new fields on the following views:
The complete list of supported fields for the issue view is available here.
Rate this page: