This page includes release notes and updates for Jira Cloud app developers. Use this page to keep track of upcoming changes, deprecation notices, new features, and feature updates from Jira Cloud Platform.
For updates about changes to the Forge platform, see the Forge changelog in the Forge documentation.
Go to our developer community to ask questions. You may also be interested in the What's New blog for Atlassian Cloud where details of major changes that affect all users of the Jira Cloud products are announced.
On February 10th 2025, we announced the Deprecation of automation.atlassian.com incoming webhooks for Automation rules https://developer.atlassian.com/changelog/#CHANGE-2299. As of 30 May 2025, the legacy incoming webhook has now been deprecated.
We’ve started to gradually shut down the legacy endpoint across all customer sites. Rules recently triggered through legacy webhooks will now be marked with error icons.
To view impacted rules:
Open the automation rule list in Jira or Confluence.
Click on the ‘Trigger' filter and select the ‘Incoming webhook’ filter. All rules triggered by an incoming webhook will be shown.
Within these filtered rules, any which have recently been triggered through a legacy webhook will have a error icon next to their name. This shows which rules were unable to complete a successful run due to using the legacy URL.
To learn how to update these rules, you can read our support documentation.
Since incoming webhooks may be called from non-Atlassian systems that we don’t have access to, or aren’t aware of, rule owners will need to migrate impacted rules to the new endpoint manually, read our support documentation.
The Get all workflows API has been deprecated due to significant scaling challenges stemming from its unbounded nature. We strongly recommend transitioning to Search workflows, which is more efficient and scalable.
Reason for deprecation: Superseded
Recommended alternative: Search workflows
Removal date: Feb 2, 2026
Action Required
Please review your apps for calls to Get all workflows and migrate to Search workflows as soon as possible.
The create workflow API will be removed on Feb 2, 2026. This API’s original deprecation notice indicated a removal date of Feb 16, 2024. However, due to unforeseen circumstances, public access has continued.
We’ve since introduced the Bulk create workflows and Bulk update workflows APIs, which offer more flexible and powerful options for creating and updating workflows. With these APIs, the create workflow API is now redundant.
Reason for deprecation: Superseded
Recommended alternatives: Bulk create workflows and Bulk update workflows
Removal date: Feb 2, 2026
What you need to do
Please review your apps for any usage of the create workflow API and transition to utilizing the Bulk create workflows and Bulk update workflows APIs.
The Get workflows paginated API is being deprecated in favour of the Search workflows API. This new API follows the updated workflow API format, and provides greater flexibility by allowing searches across both company-managed and team-managed workflows.
Reason for deprecation: Superseded
Recommended alternative: Search workflows API
Removal date: Jun 1, 2026
What You Need to Do
Please review your apps for any usage of the Get workflows paginated API and transition to the Search workflows API.
The new API will not return information about draft workflows. This is intentional, as draft support will be discontinued with the retirement of the old workflow editor.
The Workflow transition properties API is being deprecated. This API’s capabilities are now available through either the Bulk get workflows or Bulk update workflows APIs.
Reason for deprecation: Superseded
Recommended alternatives:
Use Bulk get workflows to fetch workflows. Transition properties are available under transitions in the workflows.
Use Bulk update workflows to change the values of transition properties in a workflow.
Removal date: Jun 1, 2026
What you need to do
Please review your apps for usages of the Workflow transition properties API, and transition to either Bulk get workflows and/or Bulk update workflows.
The new APIs will not return information about draft workflows. This is intentional, as draft support will be discontinued with the retirement of the old workflow editor.
Atlassian font assets are now being preloaded by the Connect JS library (ACJS) to support consistent typography across Atlassian and Connect apps. These assets are served from dedicated design system CDN https://ds-cdn.prod-east.frontend.public.atl-paas.net.
Connect apps using the standard all.js ACJS bundle will now automatically pre-load:
atlassian-fonts.css
Atlassian Sans font files (e.g., AtlassianSans-latin.woff2)
These files are delivered from the new ds-cdn host. The change was previously gated and is now enabled for all Connect apps.
Apps with a strict Content Security Policy (CSP) must update their style-src and font-src directives to allow the new CDN host. Without this, CSP violations may block font and styles loading.
Update your CSP to include:
1
2
style-src https://ds-cdn.prod-east.frontend.public.atl-paas.net
font-src https://ds-cdn.prod-east.frontend.public.atl-paas.net This change improves visual alignment with Atlassian’s visual refresh program. For further background, see:
With the Forge CLI 11.5.0 release, we've enhanced the Forge platform to let you specify the memory available to functions at runtime by setting the memoryMB property in the Manifest (https://developer.atlassian.com/platform/forge/manifest-reference/#runtimev2) . Increasing the function memory also increases its CPU allocation. The memory value can now be set between 128 MB and 1,024 MB, doubling the previous limit of 512 MB. If you do not configure the function memory, the default memory allocation of 512MB applies to your function. This change helps address out-of-memory (OOM) issues by allowing higher memory allocation.
For more information on configuring Forge function memory, see https://developer.atlassian.com/platform/forge/manifest-reference/#runtimev2.
For details on the relationship between memory and CPU allocation, refer to the https://docs.aws.amazon.com/lambda/latest/dg/configuration-memory.html.
We are deprecating the following Atlassian Connect-related unscoped npm packages in favor of their @atlassian scoped equivalents.
Starting 23rd of June 2025, these packages will no longer be supported, and we recommend transitioning to the corresponding scoped packages instead.
The affected packages are:
old package name | new package name | latest version of new package |
|---|---|---|
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
The scoped packages maintain 100% API compatibility with their unscoped versions, ensuring a seamless migration experience. We recommend updating to the scoped versions as soon as possible before the deprecation date.
All of these packages are part of the Atlassian Connect ecosystem and are used for developing Connect apps. The scoped packages provide identical functionality but align with our standardized package naming conventions. This change helps ensure consistency across our npm ecosystem and improves package security.
To update your dependencies, replace the unscoped package names with their scoped equivalents in your package.json files.
If you encounter any issues during migration, please reach out through the Developer Community forums.
We’re notifying you regarding the use of API tokens. Starting November 22, 2025, Atlassian will implement rate limits for API tokens to ensure a consistent, reliable, and secure experience for all users.
If you are using API tokens, please review this documentation to learn more about the limits
In some circumstances, where integrations using API tokens heavily impact the stability of our platform, we reserve the right to enforce the limits at an earlier date. If you will be rate-limited before November 22, 2025, Atlassian will contact you directly.
The introduction of rate limits is a proactive measure to safeguard our platform's stability and security. Rate limits help ensure platform stability and reliability by preventing integrations from overloading Atlassian’s systems.
A new url field is now returned when calling Get dynamic webhooks for app REST API.
url field is included the Webhook body. See example:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
{
"isLast": true,
"maxResults": 1,
"startAt": 0,
"total": 1,
"values": [
{
"events": [
"jira:issue_created"
],
"expirationDate": "2025-05-20T10:00:00.000+0000",
"id": 10001,
"jqlFilter": "project = TEST",
"url": "https://your-app.example.com/webhook-received"
}
]
}We’re announcing the general availability of a number of APIs for workflows, workflow schemes, and statuses. These APIs were made available as experimental features as part of, CHANGE-1011, CHANGE-1143, CHANGE-2264, and CHANGE-2292. These APIs are designed to help manage and interact with both Team and Company managed workflows in Jira, providing greater flexibility and control and back the new workflow editor that is being released in Jira Cloud.
Some of these provide new functionality for those using APIs to manage their sites. Other APIs improve on existing capabilities, and will eventually replace the existing API functions. For these APIs, both will still work, but will be deprecated in the future. Please follow the developer changelogs for upcoming deprecation announcements.
Workflows APIs
Workflow schemes APIs:
Status APIs:
These APIs are now fully supported and ready for integration, offering enhanced capabilities for developers and administrators to efficiently manage workflows and related components within Jira Cloud.
We previously announced the deprecation of the modal experience for Forge custom fields on the Issue view, which was scheduled to take effect on April 1, 2025. We understand the importance of this transition and have decided to extend the deprecation period to August 1, 2025. This extension is intended to provide additional time for developers to adapt to the new inline rendering mode.
During this extended period, apps that continue to use the deprecated modal experience will display a warning message. This message will inform users that the app is relying on a deprecated feature and advise them to contact their system admin or app developer for an update.
Please note that this will be the final extension. After August 1, 2025, rendering fields in the modal will only be possible using the dedicated https://developer.atlassian.com/platform/forge/ui-kit/components/modal/ or https://developer.atlassian.com/platform/forge/apis-reference/ui-api-bridge/modal/.
We encourage all developers to make the necessary adjustments to their apps to ensure a smooth transition. Thank you for your understanding and cooperation.
The new work item search experience we introduced in Jira Cloud will soon fully replace the previous issue search experience.
Take note of the next steps:
By Sep 1, 2025, users will no longer have the option to search for issues using the previous experience. This means you will no longer see the option to go back to the old issue search.
By Nov 3, 2025, all users will use the new work item search experience by default, and the previous search experience will be fully retired.
Forge Automation Actions are now available as an Early Access Program (EAP) feature for Forge. This feature allows developers to extend the Atlassian Automation Platform and add new Forge-based actions to the Automation Platform.
To sign up for this EAP, use the request form. As per the Atlassian Developer Terms, EAPs are offered to selected developers for testing and feedback purposes. APIs and features under EAP are considered “Early Access Materials” and are unsupported, subject to change without notice, and can’t be used in production environments.
For more information about this new capability, refer to the Forge documentation for the Forge Automation Actions.
To enhance the security and consistency of comment visibility in Jira, we have implemented a restriction on changing the visibility of child comments. This update ensures that child comments inherit the visibility settings of their parent comments, promoting consistency across comment threads to ensure the flow of communication is maintained. This will not impact modifying the visibility of the parent comment.
Concerned REST API: https://developer.atlassian.com/cloud/jira/platform/rest/v3/api-group-issue-comments/#api-rest-api-3-issue-issueidorkey-comment-id-put
Details:
Visibility Inheritance: Child comments will automatically inherit the visibility settings of their parent comments. This means that any changes to the visibility of a parent comment will be reflected in all its child comments.
API Update: The REST API for updating comments will no longer allow changes to the visibility of child comments. Attempting to update a child comment's visibility will result in a 400 (Bad Request) error.
Impact:
API Usage: Customers using the API to modify comment visibility should be aware of this change and adjust their usage accordingly. This will not impact modifying the visibility of the parent comment.
Examples:
Case 1: If a parent comment is visible and a user attempts to restrict a child comment to another visibility using the API, the request will fail with a 400 error.
Case 2: If a parent comment's visibility is changed to restrict access, all child comments will automatically inherit this restriction.
We appreciate your understanding and cooperation as we work to improve the security and functionality of Jira comments.
Rate this page: