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.
To improve performance and address constantly evolving threats on the web, Atlassian is enabling AWS Cloudfront Content Delivery Network (CDN) and Web Application Firewall (WAF) for all Confluence and Jira Cloud customers.
This rollout will occur over the coming months, country by country, with each country taking around 1-2 weeks to complete the migration.
This improvement may unfortunately impact a small number of Jira and Confluence Cloud API integrations (like those written in Python, Node/JS, Java, libcurl, Axios, atlassian-connect-express, etc) that are accidentally including a body/data/payload in GET requests.
Such requests will no longer have their body payload silently discarded and continue to be processed. Instead, they will be rejected with a HTTP 403 response code.
Atlassian products such as Loom, Trello, Opsgenie, Statuspage etc already reject GET requests with Body payloads.
For resolution instructions see more details below.
Previously Jira and Confluence Cloud APIs silently discarded any body included with a HTTP GET request and continued to process the request as normal. Unfortunately, AWS Cloudfront will actively reject such requests:
If a viewer
GET
request includes a body, CloudFront returns an HTTP status code 403 (Forbidden) to the viewer.
HTTP clients (other than browsers) that attempt to include a body with a GET request will observe a HTTP 403 response code, with text like the following:
1
2
3
4
5
6
7
8
9
403 ERROR
The request could not be satisfied.
Request blocked. We can't connect to the server for this app or website at this time. There might be too much traffic or a configuration error. Try again later, or contact the app or website owner. If you provide content to customers through CloudFront, you can find steps to troubleshoot and help prevent this error by reviewing the CloudFront documentation.
Generated by cloudfront (CloudFront)
Request ID: L23_HKTRmXpYbGS8c9dcwq-Zy5fx3_a7htuNzMlvJE6rW814efVx2h==
Unfortunately, it is not possible to configure Cloudfront to preserve the existing silent discard behavior which previously allowed these malformed requests to be successful.
To resolve the issue ensure that your HTTP client code for your API integration does not include any body with its GET requests. These are never necessary and were previously discarded.
We have found that some developers are not even aware their program or script is including a body with a GET, and the most common body payloads are as follows:
1
2
3
4
5
{}
""
''
If you observed the aforementioned error in your browser then the underlying cause is different, as browsers do not send GET requests with a body.
Please contact Atlassian Support, and ideally include the full text of the error, including Trace ID, and a HAR file covering the error: https://confluence.atlassian.com/kb/generating-har-files-and-analyzing-web-requests-720420612.html
As per CHANGE-1787 from Jul 8, 2024 , the author
and updateAuthor
fields of Worklog are no longer mandatory for the issue worklog created and issue worklog updated product events.
From Jul 7, 2025, we'll remove the ability to use the expands
query parameter for fetching associated projects, workflows, issue types, and schemes in several Jira Cloud APIs. This change is necessary due to the absence of pagination, which can lead to scaling and reliability challenges on larger sites. On these sites, workflows, statuses, and schemes can be extensively interconnected, with numerous projects and issue types.
Once the removal comes into effect, we'll ignore the expands
queries for this data and stop returning usage information in these APIs.
Affected APIs and parameters
Workflows:
Bulk get workflows: The ability to use the workflows.usages
and statuses.usages
expands will be deprecated.
Bulk create workflows: Usage information will no longer be included in responses.
Bulk update workflows: Usage information will no longer be included in responses.
Statuses:
Bulk get statuses: The usages
and workflowUsages
expands will be deprecated.
Search statuses paginated: The usages
and workflowUsages
expands will be deprecated.
Bulk create status: The usage
and workflowUsages
fields will no longer be returned.
Workflow schemes:
Bulk get workflow schemes: The workflows.usages
parameter will be deprecated.
You may need to update your app as a result of this change - see the more details section.
Migrate to the new usage APIs announced as part of CHANGE-2292.
Reminder: Starting Apr 30, 2025, a subset of Connect extension points will no longer be available on Confluence pages. For details, see the original deprecation notice linked below.
deprecation notice Deprecating a subset of Confluence page extension points.
Dear Partners,
We are updating the look and feel of the "App details" flows in the partner portal. The functionality of the different components will remain the same and the updates are limited to visual changes only.
Initially, a small percentage of partners will gain access to these updates, with a phased rollout planned for all partners to complete by Feb 14, 2025. For more information, please refer to the Quick Reference Guide(QRG) here.
include-collaborators
optional-field is now supported in the following V2 APIs:
This will list the users that have made changes to these content types. See “More details” for an example.
Example:
Adding ?include-collaborators=true
in the above APIs will result in
1
2
3
4
5
6
7
8
9
10
11
{
...
"collaborators": [
{
"accountId": "<collaboratorUserId>"
},
{
"accountId": "<collaboratorUserId>"
}
]
}
Previously retrieving collaborators would require calling the Version V2 API for every version of the content. Now this can all be done from a single call.
The V1 Get URI to download attachment API now supports retrieving attachments with specific statuses via the query param status
. Previously only attachments with the current
status can be retrieved. See “More details” for an example.
Single status example:
Adding ?status=draft
on V1 Get URI to download attachment API will retrieve an attachment only if its status is draft
.
Multi-status example:
Adding ?status=current&status=draft
on V1 Get URI to download attachment API will retrieve an attachment it’s status is current
or draft
.
You can now Assign roles to a group, Revoke roles from a group and Invite user to an org via APIs.
These will help you:
Grant and revoke product access to groups.
Invite user to org and add them to the directory.
Assign a role for a given resource
The APIs are in limited availability and access. The development, release, and timing of any features or functionality described herein remain at the sole discretion of Atlassian and are subject to change. Please reach out to Atlassian support to get access to the APIs.
Until now, the first version of an app to adopt Forge features or migrate fully to Forge required admin approval in order to be upgraded on an existing installation site.
Connect apps moving to Forge can opt-in to have their existing Connect installations updated to their latest Forge version, as long as they do not have an elevation in permissions. The rollout will be staggered over 96 hours by default, but can be further staggered via the staged migration process.
Instructions on how to opt your app in to this feature and check its eligibility can be found at Minor version updates (Connect to Forge) (Preview).
You can now Grant user access and Revoke user access via APIs.
These will help you:
Grant Platform Roles to a user
Revoke Platform Roles from a user
The APIs are in limited availability and access. The development, release, and timing of any features or functionality described herein remain at the sole discretion of Atlassian and are subject to change. Please reach out to Atlassian support to get access to the APIs.
As mentioned in a previous deprecation notice, on Feb 20, 2025 Bitbucket will be removing the List pull requests for a user API endpoint, which fetches pull requests authored by a given user across all of their workspaces.
We have introduced a new endpoint, List workspace pull requests for a user, which returns pull requests authored by the specified user in a given workspace. This new operation works the same way as the deprecated endpoint but requires the {workspace}
path parameter.
API consumers must migrate their usage to the new endpoint before Feb 20, 2025.
To retrieve pull requests authored by a given user across multiple workspaces, follow these steps:
Get the list of available workspaces using the List workspaces for user operation.
Iterate over the list of workspaces and use the List workspace pull requests for a user operation to get requests authored by the user in each workspace.
If you’re using GitKraken Desktop with Bitbucket Cloud repos, you should update to version 10.6.3 or later. Previous versions were making use of the deprecated endpoint, and will stop working correctly as of Feb 20, 2025.
Forge SQL is now available in Preview. This release provides improvements to database provisioning, performance, and observability.
Please review the available documentation to get started with Forge SQL, including assessing all of the current limitations of the service.
The Preview version of Forge SQL currently does not support data residency. By using Forge SQL, you acknowledge that Section 6 (Data Residency) of the https://developer.atlassian.com/platform/forge/developer-terms/ does not apply to data stored using Forge SQL, and you must not use Forge SQL for any applications that require data residency.
What’s new in Confluence 9.3?
Displaying days in the Roadmap Planner macro
Creating blog posts from templates
Aligning editor shortcuts with Confluence Cloud
New REST APIs
Default time zone setting in General configuration
Save time and space with more control over data pipeline exports
Rotate your encryption keys like clockwork
Lots more!
To learn more, see Confluence 9.3 Release Notes.
The Rovo agent and action modules are now generally available.
Get started with the Build a Rovo Agent hello world app tutorial.
Rate this page: