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.
Rollout : progressive rollout by tenant in progress.
We are rolling out support for Connect rules (condition, validator, post function) and Forge rules (condition, validator, post function) in the new workflow editor for company-managed projects through a progressive rollout by tenant, starting in early February 2025.
Connect and Forge rules for the new workflow editor have already been enabled for all tenants in the Developer Canary Program.
Once app support for the new workflow editor is enabled, we expect apps using the documented workflow rule APIs to work without the need for changes:
All Marketplace workflow rules configured in the old workflow editor will automatically appear and become configurable in the new workflow editor.
Users will be able to create and configure Marketplace workflow rules in the new editor from scratch for company-managed workflows.
Workflows and workflow rules will continue to be editable in the old workflow editor.
The new workflow editor is a new experience that is already available to Jira Admins as an alternative to the old editor. Jira Admins can switch between the new and old editors, as well as change the default editor experience for company-managed projects.
Unlike the old editor, the new one previously did not support Marketplace workflow rules. With this change, Marketplace rules can now be added, viewed, and configured using the new workflow editor.
The new workflow editor doesn’t use drafts. Edits are made to the active workflow, changes are built up in the editing session and published with the update action.
The configuration in the context provided to marketplace rules will reflect pending changes. They won’t however be reflected in drafts. If your apps are reliant on drafts, some changes may be needed.
We’ve extended existing APIs to allow vendor rules to determine if the new workflow editor is being used.
For Connect
The callback passed to the getWorkflowConfiguration will receive the config as the first argument and a context object as a second argument in the new editor. The second argument will remain undefined in the legacy workflow editor.
1
2
3
jira.getWorkflowConfiguration( (config, context) => {
const isNewEditor = typeof context !== 'undefined';
} );
For Forge
An additional extension.isNewEditor key is set as true in the context object returned from the getContext API in the custom UI bridge. This key will continue to be unset in the legacy workflow editor.
1
2
const context = await view.getContext();
const isNewEditor = context.extension.isNewEditor || false;This change will be shipped for company-managed projects only. Marketplace rules for team-managed projects will be supported later, with more details to be shared in a separate announcement once available.
The long-term goal is to migrate all users to the new workflow editor once feature parity between the old and new workflow editors has been achieved. The old workflow editor will eventually be disabled. The timeline for this is not finalised yet, but it will happen no earlier than December 2025.
On Feb 15, 2024, we officially ended support for our server products. Customers were no longer able to purchase, renew, upgrade, or receive any further support for all Jira, Confluence, Bitbucket, Bamboo, and Crowd server apps.
In June 2025, we will be removing the Server listings from the Atlassian Marketplace. Post these changes for all apps (besides Fisheye and Crucible) -
Server-only app listings will be removed from the Marketplace.
Server pages for apps with server hosting type will be removed.
For more information and nuances, please check this QRG.
You can now create Jira issue view background script and Jira dashboard background script modules using UI Kit.
We've added a number of new APIs that can be used to find out what is using statuses, workflows, and workflow schemes. They allow you to page through the following:
These APIs will replace the usage expands in the workflow, status and workflow scheme APIs, so look for an upcoming deprecation notice shortly. When these deprecations happen, they’ll adhere to our deprecation policy.
As of today, event filtering for Forge apps has been promoted to general availability(GA).
For more information, visit the following documentation.
Following the deprecation announcements on October 24, 2024, and November 14, 2024, we have now removed the V1 Marketplace APIs.
Please switch to the applicable V2 alternatives listed in the More Details section.
Method | Path | V2 API alternative | |
|---|---|---|---|
| 1 | GET | /rest/1.0/applications/{applicationKey} | |
| 2 | GET | /rest/1.0/applications | |
| 3 | GET | /rest/1.0/applications/{applicationKey}/latest | |
| 4 | GET | /rest/1.0/applications/{applicationKey}/{applicationBuildNumber} | |
| 5 | GET | /rest/1.0/plugins/archive/{appKey} | https://developer.atlassian.com/platform/marketplace/rest/v2/api-group-apps/#api-addons-archived-get |
| 6 | GET | /rest/1.0/categories | |
| 7 | GET | /rest/1.0/plugins/{appKey} | https://developer.atlassian.com/platform/marketplace/rest/v2/api-group-apps/#api-addons-addonkey-get |
| 8 | GET | /rest/1.0/plugins/{appKey}/feedback | |
| 9 | GET | /rest/1.0/plugins/{appKey}/feedback/type | |
| 10 | GET | /rest/1.0/plugins/{appKey}/feedback/type/distribution | |
| 11 | GET | /rest/1.0/plugins/{appKey}/icon | https://developer.atlassian.com/platform/marketplace/rest/v2/api-group-apps/#api-addons-addonkey-get |
| 12 | DELETE | /rest/1.0/plugins/{appKey}/icon | |
| 13 | GET | /rest/1.0/plugins/{appKey}/logo | https://developer.atlassian.com/platform/marketplace/rest/v2/api-group-apps/#api-addons-addonkey-get |
| 14 | DELETE | /rest/1.0/plugins/{appKey}/logo | |
| 15 | GET | /rest/1.0/plugins/{appKey}/banner | https://developer.atlassian.com/platform/marketplace/rest/v2/api-group-apps/#api-addons-addonkey-get |
| 16 | DELETE | /rest/1.0/plugins/{appKey}/banner | |
| 17 | GET | /rest/1.0/plugins/{appkey}/tokens/{token} | |
| 18 | DELETE | /rest/1.0/plugins/{appkey}/tokens/{token} | |
| 19 | GET | /rest/1.0/plugins/{appkey}/tokens | |
| 20 | POST | /rest/1.0/plugins/{appkey}/tokens | |
| 21 | GET | /rest/1.0/plugins/{appkey}/pricing | |
| 22 | GET | /rest/1.0/plugins/{appkey}/pricing/draft | |
| 23 | GET | /rest/1.0/plugins/vendor/{vendorId} | |
| 24 | GET | /rest/1.0/plugins | https://developer.atlassian.com/platform/marketplace/rest/v2/api-group-apps/#api-addons-get |
| 25 | GET | /rest/1.0/plugins/{appKey}/version/{appVersion} | |
| 26 | GET | /rest/1.0/plugins/{appKey}/build-number/{buildNumber} | |
| 27 | PUT | /rest/1.0/plugins/{appKey}/build-number/{buildNumber} | |
| 28 | GET | /rest/1.0/plugins/{appKey}/version/{buildNumber}/screenshots/index | |
| 29 | DELETE | /rest/1.0/plugins/{appKey}/version/{buildNumber}/screenshots/index | |
| 30 | POST | /rest/1.0/uploads/artifact/ | |
| 31 | POST | /rest/1.0/uploads/artifact/fetch | |
| 32 | POST | /rest/1.0/uploads/image/{imageType} | |
| 33 | GET | /rest/1.0/vendors/{vendorId} | |
| 34 | DELETE | /rest/1.0/vendors/{vendorId}/contacts/{atlassianAccountId} | |
| 35 | DELETE | /rest/1.0/vendors/{vendorId}/{imageType} | |
| 36 | GET | /rest/1.0/plugins/{appkey}/similar | NA |
| 37 | GET | /rest/1.0/plugins/app/{applicationKey} | NA |
| 38 | GET | /rest/1.0/plugins/app/{applicationKey}/filterBy | NA |
| 39 | GET | /rest/1.0/plugins/filterBy | NA |
| 40 | GET | /rest/1.0/plugins/search | NA |
| 41 | GET | /rest/1.0/vendors | NA |
| 42 | GET | /rest/1.0/reference | NA |
| 43 | GET | /rest/1.0/reference/applicationStatuses | NA |
| 44 | GET | /rest/1.0/reference/applicationVersionStatuses | NA |
| 45 | GET | /rest/1.0/ | NA |
| 46 | GET | /rest/1.0/users/{atlassianAccountId} | NA |
We are removing mirrors of third-party packages such as maven-central from packages.atlassian.com
We're updating how we provide packages for customers and partners to develop with our platforms. Starting February 1, 2025, we will discontinue providing third-party packages on packages.atlassian.com. Instead, customers and partners must fetch these packages directly from the original upstream repositories.
For details on how this change affects you and for guidance on migration, please refer to the documentation available on Atlassian Developer .
The UI modifications (UIM) error handling method now supports a new error type - unregistered field.
The complete list of error types is available here.
We have introduced a message size limit for the logMessage string parameter in the addLog Forge API. The maximum allowed size for messages are 65,536 characters. Log messages exceeding this limit will be truncated by the app migration platform.
Dear Partners,
We are updating the look and feel of the "Create New Version" and "Make Version Public" flows in the partner portal for version publishing. These updates are aimed at simplifying the app version creation workflow. The functionality of the different components and the creation experience will remain the same; these 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.
p.s Please note that the “Publish App” UI will not undergo any changes as part of this.
The https://developer.atlassian.com/platform/forge/runtime-reference/app-context-api/ is extended with the the invocationRemainingTimeInMillis function that returns time remaining for the current Forge function invocation.
To use it, update @forge/api in your project and ensure you are using the latest version of @forge/cli.
The remaining execution time can be useful with long running functions. See the Use a long-running function example.
Forge functions that are handling async events can specify a timeout of up to 15 mins (900 seconds). They were previously limited to 55 seconds.
To extend a function’s run time, add timeoutSeconds property to the function definition (see the Function module reference). Functions with a longer timeout specified cannot be connected to any module other than consumer. For details, see https://developer.atlassian.com/platform/forge/runtime-reference/async-events-api/ and Invocation limits.
A Confluence 9.3 beta version is available now for testing. To find out what’s changed, check out Confluence 9.3 beta release notes.
Got feedback or want to discuss this beta? Chat with us in this Atlassian Developer Community thread. The earlier we know about potential problems, the more time we'll have to fix them before the final release.
The read:user:bitbucket Forge app scope has been removed from the following API endpoints since it is considered unnecessary. This is a non-breaking change and Forge app developers have the option of removing the read:user:bitbucket Forge app scope from apps that use the following endpoints.
Route | Before | After |
|---|---|---|
GET |
|
|
GET |
|
|
GET |
|
|
GET |
|
|
GET |
|
|
GET |
|
|
GET |
|
|
GET |
|
|
GET |
|
|
GET |
|
|
GET |
|
|
GET |
|
|
GET |
|
|
The following API endpoints have been updated to no longer require the read:user:bitbucket Forge app scope:
This is a reminder about the changelog announcement regarding the deprecation of UI Kit 1 issued on August 28, 2024.
The retirement of UI Kit 1 will take effect on February 28, 2025 (Friday) wherein which any apps using UI Kit 1 will stop working.
Please ensure you update your app before this date using our guides:
Rate this page: