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.
This feature will allow Connect apps to move to Forge and existing Forge apps to offer data residency - realm pinning for remotes.
We’re happy to present the last Early Access Program (EAP) build of Jira Software 10.4 and Jira Service Management 10.4. To find out what’s in scope of this EAP release, refer to Preparing for Jira 10.4.
You can download the current EAP from this page. If you’re using maven.atlassian.com, the version is 10.4.0-m0004.
This EAP release isn't for production or demonstration use.
We’re introducing optional properties under a security egress field to the webtrigger module:
allowDataEgress
allowedResponses
Using these properties prevent data egress, which enables apps using web triggers to be eligible for Runs on Atlassian.
To join the EAP, sign up here.
We’ve introduced optional parameters for the webtrigger module that define whether data egress is permitted and enable the developer to define status codes that can be returned to the process that invoked the web trigger.
This new no-egress solution will provide partners with a way to use web triggers while still meeting Runs on Atlassian eligibility.
At this stage, we believe that this will support:
Callers that require indicating success or failure generically (e.g., "200" for success, "500" for failure)
Callers that require a static error or success message based on the response
We look forward to receiving your feedback.
Bitbucket Data Center and Server 8.9.24, 8.19.14, and 9.4.2 bug fix releases are available now!
To see the issues resolved in these bug fix releases, go to:
We've introduced the bitbucket:repoCodeOverviewPanel Forge module. This module adds an expandable panel on the Source page of a repository to display custom information defined in a Forge App.
This enhancement allows developers to customize the information displayed in the repository Source page, improving the visibility of critical data. For more information, see Bitbucket code overview panel.
User-Defined Remotes is now being considered as a future improvement to the developer platform. If this is of interest watch this roadmap item for updates. See https://ecosystem.atlassian.net/browse/ROADMAP-99 for more information.
We’re happy to introduce a new Jira Forge product event:
configuration changed - avi:jira:changed:configuration
Follow the link to read more about it.
To help with discount information for zero-dollar transactions, we have now included the discount amount to provide context on the total discount amount for the given license. This information was also present earlier but only for a limited number of $0 transactions; it has now been populated for all $0 transactions that have discounts.
Data can be seen in the purchaseDetails.discounts array field of the transaction API. Partners can fetch this data using the lastUpdated field of this API. Change is live in production starting Jan 13, 2025(today).
We have back-filled the data for zero-dollar transactions for approximately 86,000 transactions across partners, and we will provide this discount information for future zero-dollar transactions. This includes all currently active and historical $0 transactions in the past that have a discount associated with them.
We have now fixed the issue with the DynamicTable component where custom components in the cell contents would throw an error. Upgrade to the latest version of @forge/react to get the fix.
With the recent updates to our content delivery network (CDN), all Custom UI apps now allow-list the Atlassian emojis API URL by default. This means you no longer need to declare egress to load images coming from the emojis API in Custom UI apps.
These recent updates can effectively help you reduce egress from your Custom UI apps.
These updates can help if you’re looking to make your app eligible for the Runs on Atlassian badge. To know more about Runs on Atlassian, see this developer blog post.
Note, the removal of egress does not require a major version update of apps.
Look for opportunities to remove the following external permissions from your manifest:
1
2
3
4
permissions:
external:
images:
- *.atl-paas.netBitbucket Data Center 9.5 is available for upgrade! This release introduces new features, such as default reviewer groups for pull requests, encryption key rotation, improvements to logging and profiling, and more.
Today we published a blog titled Taking the Ecosystem Forward: An Update on the Future of Connect, which shares an early look at plans to phase out support for Connect. This early announcement is intended for owners of business critical Connect apps, including partners and customers with custom apps, to provide ample time to explore requirements and arrive at a fair timeline for end of support, together.
We’re seeking your feedback to help us shape the next steps for Connect - you can provide your feedback via the survey linked in the blog post.
The blog post details the key stages of our plan, as we progress on this journey. By the final stage, Connect will enter an end of support state (defined in the blog post), where apps can continue to utilise Connect modules, but do so at their own risk. At this stage, we do not have definitive dates for each of these phases - determining a fair and appropriate end of support date will be a joint effort with our partners and other app builders. The purpose of today’s announcement is to start that conversation.
We’re happy to present the second Early Access Program (EAP) build of Jira Software 10.4 and Jira Service Management 10.4. To find out what’s in scope of this EAP release, refer to Preparing for Jira 10.4.
You can download the current EAP from this page. If you’re using maven.atlassian.com, the version is 10.4.0-m0002.
This EAP release isn't for production or demonstration use.
A Confluence 9.3 EAP milestone is available now for testing. To find out what’s changed, check out Preparing for Confluence 9.3.
Got feedback or want to discuss the latest EAP? 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.
This is a reminder about the changelog announcements issued on October 24, 2024, and November 14, 2024, concerning the deprecation of legacy REST APIs.
The deprecation of Marketplace V1 REST APIs will take effect on January 10, 2025 (Friday). These APIs are intended for Atlassian usage and will not be supported after this date.
Please review your current implementations and make any necessary adjustments before January 10, 2025, to ensure continued functionality.
See the More details section for the APIs list.
The following APIs will no longer be available from Jan 10, 2025 :
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 |
Rate this page: