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.
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:
We’re happy to present the second Early Access Program (EAP) build of Jira Software 11.0 and Jira Service Management 11.0. To find out what’s in scope of this EAP release, refer to Preparing for Jira 11.0.
You can download the current EAP from this page. If you’re using maven.atlassian.com, the version is 11.0.0-m0002.
This EAP release isn't for production or demonstration use.
We’ve added new Confluence product events for labels:
avi:confluence:created:label
avi:confluence:added:label
avi:confluence:removed:label
avi:confluence:deleted:label
You can use these events to invoke your Forge app function when label is created, added to an entity, removed from an entity, or deleted. For more details see https://developer.atlassian.com/platform/forge/events-reference/confluence/#labels.
We’ve published new documentation explaining how grace periods work for licenses. To help you programmatically identify grace period status, the getLicensesAPI now includes an inGracePeriod field.
This field enables you to determine if a license is:
Currently in a grace period → inGracePeriod: Yes
Was previously in a grace period, but is no longer → inGracePeriod: No
Never had a grace period → inGracePeriod field will be absent
📝 Note: There are no UI changes associated with this update - the information is available only via API.
We’re happy to present the second Early Access Program (EAP) build of Jira Software 10.7 and Jira Service Management 10.7. To find out what’s in scope of this EAP release, refer to Preparing for Jira 10.7.
You can download the current EAP from this page. If you’re using maven.atlassian.com, the version is 10.7.0-m0004.
This EAP release isn't for production or demonstration use.
The URL of the page on which a module is being rendered has been added to its extension context. extension.location will be returned in the context object from view.getContext().
Following its Preview release, we’re excited to announce that the Runs on Atlassian program is now generally available.
This means that customers can now see the Runs on Atlassian badge for eligible apps on the Atlassian Marketplace. Similarly, customers can also filter for eligible apps.
Check out Runs on Atlassian documentation to know more about the program, as well as the eligibility requirements and the next steps you can take.
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.
Following the initial release of the forge version command in Forge CLI, we’re introducing more improvements to amplify the usage of the command.
You can now compare versions across two different environments, which lets you, for example, compare your major app version between development and production environments:
1
forge version compare --version1=10 --environment1=development --version2=3 --environment2=production
The output then includes the following details:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
forge version compare --version1=10 --environment1=development --version2=3 --environment2=production
✔ Comparing app versions...
ℹ Comparison between app versions [10 in development] and [3 in production] is shown below:
┌─────────────────┬──────────────────────────────────────────────────┬──────────────────────────────────────────────────┐
│ Property │ Version 10.x [development] │ Version 3.x [production] │
├─────────────────┼──────────────────────────────────────────────────┼──────────────────────────────────────────────────┤
│ deployment date │ "2024-11-05T06:18:03.129Z" │ "2024-12-17T04:38:54.678Z" │
├─────────────────┼──────────────────────────────────────────────────┼──────────────────────────────────────────────────┤
│ egress │ [] │ [ │
│ │ │ { │
│ │ │ "addresses": [ │
│ │ │ "https://google.com" │
│ │ │ ], │
│ │ │ "type": "fetch.backend" │
│ │ │ } │
│ │ │ ] │
├─────────────────┼──────────────────────────────────────────────────┼──────────────────────────────────────────────────┤Run npm install -g @forge/cli@latest on the command line to install the latest version of @forge/cli and receive these changes.
We’ve released a new module, Confluence page banner, which enables apps to add a banner to Confluence pages. This module is generally available.
This feature provides equivalent Forge functionality to the Connect Confluence atl.general web panel.
Rate this page: