Atlassian developer changelog

We will be conducting scheduled maintenance from September 23rd, 0:00 AM UTC to October 5th, 0:00 AM UTC, 2024.

During this period, we will be migrating installations on a site-by-site basis. Each site's migration will take approximately 300 milliseconds.

During this window, app installations, uninstallations, upgrades, and subscriptions may be temporarily affected. However, other app functionalities, such as invocation or listing installations, will remain unaffected.

Any interrupted operations will succeed upon retry.

We’re happy to present the first Early Access Program (EAP) build of Jira Software 10.1 and Jira Service Management 10.1. To find out what’s in scope of this EAP release, refer to Preparing for Jira 10.1.

You can download the current EAP from this page. If you’re using maven.atlassian.com, the version is 10.1.0-m0003.

You can now specify the language which a template form can be translated to, using the new requestLanguage query parameter for the following endpoints:

• Get Form Template

• Get Form on a Request Type

In December 2023 we have announced a new limit coming to Connect field options and scopes: https://developer.atlassian.com/changelog/#CHANGE-1347.

This is a notice that we are going to begin rolling out this change beginning Sep 23, 2024.

Forge apps can now access the Get User Email and Get User Email Bulk APIs on Jira and Confluence when declaring the read:email-address:jira or read:email-address:confluence scopes.

Endpoints and scopes have been added for Confluence Folders. For further information about these updates, reference the Atlassian Developer Documentation for OAuth and Forge scopes as well as Confluence Cloud REST API v2.

Three new scopes have been added for Folders: read, write, and delete. These additions will support the implementation of Folders in Forge applications.

Creation, retrieval, and deletion of Folders have been added for v2 REST APIs. Creation, retrieval, modification, and deletion of properties as well as retrieval of operations and ancestors is supported via these added APIs.

Back in June, we announced a deprecation notice for the behavior of the parent field in the Edit issue metadata API. Starting on Sep 23, 2024, we will be rolling out these changes.

Previously, the parent field was always returned by this API regardless of screen configuration. These changes will mean that in company-managed projects, the parent field will only be returned in the response if the parent field is in the screen associated with the edit issue operation. The issue view experience will also be updated so that the parent field is only editable when it's on the screen associated with the edit operation. You can find more details here.

We’re aware that some customers currently rely on being able to edit the parent field regardless of their screen configuration. To ensure that these customers can continue to do so, the field has been added to the screen configured for the edit issue operation. Jira administrators can then remove the parent field from the edit issue operation screen if they wish to restrict its editing.

A Confluence 9.1 beta version is available now for testing. To find out what’s changed, check out Confluence 9.1 beta release notes.

Got feedback or want to discuss this beta? Chat with us in this Atlassian Developer Community thread. The earlier we know about potential problems, the more time we'll have to fix them before the final release.

Download the latest beta

This capability allows a Connect app supporting data residency to remain in the same region which the app was originally installed for up to 30 days after uninstall. This allows customers to reinstall an app without suffering data loss by being pinned to a different region

You can read more here, or read our developer docs here

We are simplifying the left nav experience for Confluence users, including cleaning up unused features in spaces.

We will turning off blogs in existing Confluence spaces that have not published a blog. While blogs can still be created after this change, users won’t be able to see blogposts in the side navigation until they turn the feature back on in the Edit Features page (Space Settings > Features).

We’re making preparations to introduce OpenSearch as an opt-in feature for our customers in a future Jira Data Center release. With OpenSearch, we’re aiming to externalize indexing processes to support large customers in improving performance for their search- and index-related functions in Jira DC.

Starting from Jira 11, we will stop providing Lucene as a dependency and we’ll keep you informed about future deprecations.

This project has only just begun, so we don’t yet have a timeline. We wanted to give you as much advance notice about this feature as possible, and we’ll share a guide to help you migrate and test your apps as soon as it’s ready.

Join the conversation on this Atlassian Developer Community thread.

We will be automatically turning off blogs for any newly created space to simplify the left nav experience.

While blogs can still be created after this change, users won’t be able to see blogposts in the side navigation until they turn the feature back on in the Edit Features page (Space Settings > Features).

This change will take place on all forms of space creation whether the request is coming from the UI, GraphQL, or REST API.

In our v2 Smart Link APIs, we provide HTTP methods for creating and getting Smart Links in the content tree. Previously, the URL embedded as the Smart Link in the content tree was inaccessible from these APIs (as reported here); now, they are provided in the response payload under the “embedUrl" property key (if present).

We are removing atl.list-templates and atl.list-templates.after from Confluence Connect web panels. These extension points will no longer be available to apps that modify admin settings.

Following its preview release back in February, Adopting Forge from Connect is now generally available.

The majority of apps can now incrementally adopt Forge with their existing Connect apps. The remaining apps will be able to do so when Data Residency support is available for Forge Remotes.

Learn more in our blog post - Connect apps will gain new extensibility features through Forge