Atlassian developer changelog

We’re announcing the deprecation of the V2 Applications APIs on Atlassian Marketplace.

What’s changing

• The Applications APIs are now deprecated.

• A six-month deprecation window begins immediately, and these APIs will be removed after May 6, 2026.

• Refer to the updated documentation for V3 Parent software APIs to plan your transition.

What you need to do
Partners and developers should migrate to the V3 Parent software APIs to ensure continued functionality and support.

We’re happy to present the release of Jira Software and Jira Service Management 11.2. To find out more about breaking changes, new features, and introduced fixes, check out the Jira Software 11.2 release notes and Jira Service Management 11.2 release notes.

Download Jira Software 11.2 and Jira Service Management 11.2.

The ability to build Forge apps that are compatible with multiple Atlassian apps is now available in Preview. This feature allows you to declare compatibility in your app’s manifest and enables your app to be installed and used across Jira, Confluence, and Compass.

For more information, see App compatibility.

We’ve added new Confluence Forge events for relations:

• avi:confluence:created:relation

• avi:confluence:deleted:relation

You can use these events to invoke your Forge app function when a relationship is created or deleted in Confluence. For more details, see the Confluence events reference documentation.

Following our prior deprecation notice, the following internal API endpoints will now result in a 404 Not Found response.

• /wiki/rest/masterdetail/1.0/detailssummary/lines

• /download/thumbnails/{id}/{id}

• /download/resources/{id}/icons/{id}

• /download/resources/{id}/{id}

• /download/resources/{id}/images/{id}

What’s changing?
Partners have consistently requested comprehensive order history for entitlements to better track cloud subscription state changes over time.

To this end, Marketplace team is introducing a new query parameter, showLicensesHistory, to the Licenses API.
When set to true, this parameter enables partners to retrieve historical events - snapshots of licenses.
The response body for historical events remains unchanged, except for the addition of a new field: recordCreatedDate, which indicates when each snapshot was created.

On setting showLicensesHistory: true on Nov 12, 2025 for these licenses,

1. ENT -1 : Displays 2 Snapshot Data with respective recordCreatedDate

2. ENT -2: Displays 1 snapshot Data with respective recordCreatedDate

Benefits:

• Partners can now proactively track subscription lifecycle events

• Reduce support tickets related to license state inquiries

Availability:
This feature is targeted for release on 3rd November 2025.

Next steps:
Partners are encouraged to review and integrate the new reporting capability to access license history snapshots.

You can now connect Jira Product Discovery ideas with delivery items on remote Cloud or Data Center instances linked to your Jira Product Discovery site. After setup, a new “site” field appears, letting you choose whether to create or link a delivery item locally or remotely. This integration keeps delivery progress in sync across your Cloud sites and Data Center instances, so you no longer need to update items manually on each platform. You’ll always see up-to-date insights about delivery progress from all linked items.

This integration requires Jira Data Center version 10.3 or higher, a free Marketplace app, and a Jira Product Discovery Premium plan. There are no additional edition requirements for connecting to a remote Cloud instance.

View the app on Marketplace or read the app documentation.

Atlassian is revising the timeline for upcoming Marketplace revenue share rate increases, originally scheduled to take effect on January 1, 2026. The new effective date for these changes is April 1, 2026, with subsequent increases adjusted accordingly.

Learn more

You can now call Web trigger URLs with additional path suffixes. Previously, requests to a WebTrigger URL with a path suffix (for example, /hello/world) returned a HTTP 404 error. With this update, such requests are now routed to your associatedhttps://developer.atlassian.com/platform/forge/manifest-reference/modules/function/, and the suffix is available in the new userPath property of the request.

This enhancement lets you handle dynamic routes and build more flexible integrations with your Forge app.

From Apr 30, 2026, the nodejs20.x runtime will be deprecated. This is in line with the Node.js version 20.x end-of-life, scheduled for Apr 30, 2026.

You must update your apps to use the newer nodejs22.x runtime before this date. Otherwise, you will not be able to deploy changes to your app.

We’re announcing the deprecation of the V2 Privacy and Security APIs on Atlassian Marketplace.

What’s changing

• The V2 Privacy and Security APIs are now deprecated.

• A six-month deprecation window begins immediately, and these APIs will be removed after April 30, 2026.

• Refer to the updated documentation for V3 Privacy and Security APIs to plan your transition.

What you need to do
Partners and developers should migrate to the V3 Privacy and Security APIs to ensure continued functionality and support.

Following its review release, we are excited to announce that the V3 Privacy and Security APIs are now generally available on the Atlassian Marketplace. This means these APIs are now fully operational and can be used in production environments.

For more information, see V3 Privacy and Security API documentation.

From Nov 1, 2025, Atlassian will migrate all Forge apps to a new app lifecycle platform. This migration introduces changes to how the platform handles apps with inactive licenses:

• Unified uninstall flow:

  • Unsubscribing and uninstalling an app will be combined into a single ‘uninstall’ action.

  • When an admin selects ‘uninstall’, the app will remain active until the end of the current subscription or trial period, plus an additional 60 days, before it is permanently deleted. No further user action is required during this period.

• Expedited uninstall:

  • Admins can choose to expedite the uninstall process. This will immediately uninstall the app and forfeit any remaining subscription period.

• Legacy “free” licensing state:

  • Apps that have already passed the end of their subscription or trial period will temporarily transition to a legacy “free” licensing state. These inactive installations will not thus be affected by the new uninstall flow until an admin initiates an uninstall action.

  • Partners are encouraged to request that customers either re-subscribe or uninstall these apps.

Read more in the community post and our support doc.

New features:

The following are the new commands:

• 🆕 acli jira board list-sprints command to get all sprints.

• 🆕 acli jira board search command to search through all the boards.

• 🆕 acli jira field create command to create a custom field in Jira.

• 🆕 acli jira field delete command to move a custom field to trash.

• 🆕 acli jira field cancel-delete command to restore the field from the trash.

• 🆕 acli jira filter list command to list filter that are either my or favourite.

• 🆕 acli jira filter add-favourite command to add a filter as favourite.

• 🆕 acli jira sprint list-workitems command to list work items in a sprint.

• 🆕 acli jira workitem attachment delete command to delete an attachment from a workitem.

• 🆕 acli jira workitem comment delete command to delete a comment for a given workitem.

• 🆕 acli jira workitem comment update command to update a comment on a work item.

• 🆕 acli jira workitem create-bulk command to bulk create Jira issues.

• 🆕 acli jira workitem watcher remove command to remove a watcher from workitem.

A new RFC is ready for review at: https://community.developer.atlassian.com/t/rfc-117-forge-llms/96506