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 introducing a Data Center security checklist and best practices for admins. This guide will provide you with valuable insights on safely deploying and administering Atlassian self-managed software.
We value your input and actively encourage feedback from the community. Your contributions will help us refine this guideline into the most reliable source of information for admins. Please select the "Provide feedback about this article" link located at the bottom of the document.
We're deprecating injecting stylesheets for Connect apps via inline styles in favor of loading from the Connect CDN. This affects the Theming API and dynamic content macros that supported the legacy Confluence editor.
At the end of the deprecation period (18th November 2024), we’ll stop injecting any inline styles and only load from the CDN.
If your app doesn’t use the above Connect features, or doesn’t use a Content Security Policy (CSP) for style-src, no action is required. Otherwise, please read the details here or see https://developer.atlassian.com/platform/marketplace/security-requirements/#connect-apps on how to modify your CSP to support these changes.
To support these changes in your app, if you're using a Content Security Policy that sets the style-src policy, you must add the Connect CDN (https://connect-cdn.atl-paas.net) to your policy to allow these stylesheets to be injected. It's safe to remove unsafe-inline from your policy if you've been using it up until now.
The stylesheets mentioned here are included automatically via the Connect JS script, not manually by the app vendor. There are two circumstances under which Connect injects stylesheets into your app.
The first is only for apps which opted in to the Theming API. The theme stylesheets currently load via an inline stylesheet, which forces vendors to adopt the insecure unsafe-inline policy, and is the main motivation for this change.
The second location is only for dynamic content macros. We inject a stylesheet with CSS classes representing colors from the legacy Confluence editor. This happens without opt-in, to be backwards-compatible with macros created in the legacy editor. This injection is currently done via CSSOM, not inline styles, and therefore isn’t impacted by style-src CSP rules currently. However it’ll also start being served from the CDN.
During the deprecation period, styles will be loaded simultaneously via the current methods described above and from the CDN. After the deprecation period, styles will only be loaded from the CDN, and the inline/CSSOM methods will be removed.
requestBitbucket is now available in @forge/bridge, so you can make Bitbucket API fetch requests from the front end of a UI Kit or custom UI app. For more information on using requestBitbucket, see the Part 2: Call a Bitbucket API tutorial.
This change is still a work in progress.
We’re working on improving the security of our login experience for Jira Software and Jira Service Management by allowing customers to add a native second authentication layer.
The new login process will support a built-in two-step verification (2SV) capability managed by the Atlassian SSO for Data Center app implemented as a system plugin using a time-based one-time password (TOTP) as a second factor.
This change is scheduled to be included in a future feature version following the initial release of Jira Software 10.0 and Jira Service Management 6.0. Today, we’re happy to announce that we’re launching an Early Access Program (EAP) to seek feedback for the prototype of this solution and invite you to take part in this. Follow the Atlassian developer changelog for updates.
A new RFC is ready for review at https://community.developer.atlassian.com/t/rfc-51-multiple-help-centers-on-jira-service-management/79958.
We are making changes to the /object/aql and /object/navlist/aql endpoints within the REST API’s for Assets in Jira Service Management cloud.
We will be removing the total attribute from the response payload of the /object/aql endpoint. If you require this, instead use the /object/aql/totalcount endpoint which will provide a total count for any AQL query.
We will be removing /object/navlist/aql from our list of supported public endpoints and it should now be considered deprecated. Instead we recommend you migrate to the /object/aql endpoint.
These changes will be made on or after 30 Sept 2024.
We’re happy to inform you that we’re making the following new API endpoints available:
Returns a paginated list of priority schemes
GET /rest/api/3/priorityscheme
Get available priorities by priority scheme
Returns a paginated list of available priorities to be added to a scheme
GET /rest/api/3/priorityscheme/priorities/available
Get priorities by priority scheme
Returns a paginated list of priorities
GET /rest/api/3/priorityscheme/{schemeId}/priorities
Get projects by priority scheme
Returns a paginated list of projects
GET /rest/api/3/priorityscheme/{schemeId}/projects
POST /rest/api/3/priorityscheme
PUT /rest/api/3/priorityscheme/{schemeId}
DEL /rest/api/3/priorityscheme/{schemeId}
Suggested priorities for mappings
Returns a paginated list of priorities
POST /rest/api/3/priorityscheme/mappings
Confluence Data Center is now shipping an EAP with approximately 95% of the targeted breaking changes for the platform release. We encourage marketplace partners to test and provide feedback.
Get your app ready in three steps:
Beginning on 15th May 2024, we will update our marketplace reports to use the invoice issuance date as the sale date, aligning it with the sale date used by our finance systems. This change is designed to benefit Atlassian Marketplace Partners by resolving inconsistencies between marketplace and remittance reports and enhancing clarity. Please note that this change will not impact historical transactions or alter our current payment process.
For more details, please refer to https://atlassianpartners.atlassian.net/wiki/spaces/news/blog/2024/04/12/453771297/Reports+Alignment+of+Sale+Date+Across+Marketplace+and+Finance+Systems
We are deprecating the Bulk remove content states from content and the Get update on long running task for setting of content state v1 REST APIs in Confluence Cloud.
On Nov 13, 2024, the POST /wiki/rest/api/content-states/delete endpoint and the GET /wiki/rest/api/content-states/task/{taskId} will be removed.
We recommend you use the Removes the content state of a content and publishes a new version endpoint instead.
A new RFC is ready for review at https://community.developer.atlassian.com/t/rfc-50-let-users-easily-interact-with-and-configure-macros-in-the-editor/79871.
Following the deprecation notice (see https://developer.atlassian.com/cloud/jira/platform/changelog/#CHANGE-916), the products field will be mandatory for the Jira User Create REST API.
This change will take effect as soon as the new Create User API doc is released, expected within the next few days.
Valid product name for the products field: jira-core, jira-servicedesk, jira-product-discovery and jira-software. To create a user without product access, set this field to be an empty array.
Bitbucket Data Center 8.19.3 and Bitbucket Data Center and Server 8.9.14 bug fix releases are available now!
To see the issues resolved in these bug fix releases, go to:
The UI modifications (UIM) module now supports three new entry points for the issue view:
list
issues
search
The complete list of supported entry points is available here.
To resolve several security vulnerabilities, the JDBC driver for the H2 database engine is no longer bundled with Jira Software 10.0 and Jira Service Management 6.0. This means that we’re removing it from the list of supported platforms. Additionally, you’ll no longer be able to evaluate Jira Software 10.0 and Jira Service Management 6.0 using H2.
Rate this page: