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.
The first EAP for Jira Software 9.16 and Jira Service Management 5.16 is ready for testing. You can download the EAP from this page. If you’re using maven.atlassian.com, here are the versions: 9.16.0-m0001 for Jira Software and 5.16.0-m0001 for Jira Service Management.
If you want to share your feedback, just leave a reply in the Atlassian Developer Community thread.
We’ve added a set of new query parameters to the v2 Get space by id API endpoint that allows for optional fetching of metadata properties related to the given space. These include:
include-labels
include-operations
include-properties
include-permissions
By default, these metadata properties will not be included in the response unless specified.
You can now secure your Assets imports with the Jira allowlist. This way, you can make sure that your import configurations (such as Object Schema import, LDAP import) get data only from allowed external sources.
To start using this feature:
Make sure that the allowlist in Jira is configured.
Navigate to Jira administration, select Manage apps then Assets configuration.
In the Security section, select Yes for Use the Jira Allowlist to block import configuration URLs.
1: New setting to filter import configuration URLs
To reduce the computational load on your instance, your Workload report now contains additional filters, and is configured by default to show only agents with assigned issues. This will speed up the load time of Workload reports in large Jira Service Management instances and reduce timeouts. Whenever you need to view the workload of all agents, just modify the search filter.
1: New filter to view agents with workload
As we continue to strengthen the security of our products, we’ve made some changes to the Groovy scripts interface in Assets to reduce the risk of arbitrary code execution. From Jira Service Management 5.16, the Groovy script console, which lets you build and execute scripts on the fly, will no longer be available across Assets.
You can continue to use and run Groovy scripts, but you’ll need to store them in a common script directory (located within the shared home directory of Jira) and add the script path for use within workflow transitions and object schema automations. We’ve added a new read-only panel to help you easily verify script content before you use or run scripts. How to use Groovy scripts
This feature is on by default and the change impacts the following:
The console available in Administration (select Manage apps then Assets script console).
The console available in Workflows (conditions, validators, post functions).
The Automation tab in Assets schema configuration.
The Assets allowlist page will no longer be available. However, your existing automations that rely on the scripts you added to the allowlist before this upgrade won’t be affected. The new Groovy scripts page contains a read-only list of these allowlist files.
Any file paths you saved in Workflows will be added to the allowlist during the upgrade.
Any code you added to the console before the upgrade will be available in the read-only panel.
Introducing additions to the Assets archiving experience we released in 5.15. You can now restore archived objects easily from the Archived objects page and take advantage of the new Archive object action in Assets automations. More about archiving objects
What’s new?
Search for objects in the Archived objects page and:
use the new Archived by me filter to search for objects that you’ve archived
restore an archived object directly from this page (select an object and then from the Actions column, select More actions (…) and then Restore)
bulk restore objects (you can either select Restore all to restore all the filtered objects or select the desired objects and then select Restore selected)
Use the new Archive object action in Assets automations. Note the following:
For the action to run successfully, the rule needs to run as a user with manager permissions for the object type.
Each condition can contain only one Archive object action.
As attributes can’t be updated on archived objects, you can’t add an Attribute value action after an Archive object action.
As archived objects can’t be updated, any actions that trigger changes to archived objects will fail. For example, Groovy script or HTTP request actions that attempt to modify objects affected by the Archive object action.
1: New action to archive objects
If you’re already running your Jira Data Center instance in AWS, you can now securely store backups in Amazon S3 object storage.
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.
Rate this page: