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.
As shared in our https://developer.atlassian.com/cloud/bitbucket/changelog/#CHANGE-2887, Bitbucket Cloud will fully deprecate support for OAuth 1.0 and implicit grant flows on Feb 27, 2026. To help teams identify and migrate any remaining usage ahead of the enforcement date, we will run a series of controlled brownouts starting Feb 28, 2026, for two weeks, after which the functionality will be fully removed on Mar 14, 2026.
During each brownout window:
All requests to generate OAuth 1.0 or implicit grant access tokens will fail with an HTTP 400 error code.
All requests authenticated with existing OAuth 1.0 or implicit grant access tokens will fail with an HTTP 401 error code.
Dates | Brownout duration per window | Brownout window start times (UTC) |
|---|---|---|
Feb 28, 2026 | 15 minutes | 00:00, 06:00, 12:00, 18:00
|
Mar 1, 2026 | ||
Mar 2, 2026 | 30 minutes | |
Mar 3, 2026 | ||
Mar 4, 2026 | 1 hour | |
Mar 5, 2026 | ||
Mar 6, 2026 | 2 hours | |
Mar 7, 2026 | ||
Mar 8, 2026 | 3 hours | |
Mar 9, 2026 | ||
Mar 10, 2026 | 4 hours | |
Mar 11, 2026 | ||
Mar 12, 2026 | 5 hours | |
Mar 13, 2026 | ||
Mar 14, 2026 | Final removal | |
After the brownout schedule completes on Mar 14, 2026, OAuth 1.0 and implicit grant flows and existing access tokens will no longer be usable.
To maintain access, migrate to a supported OAuth 2.0 flow by following our OAuth 2.0 guide which provides complete details.
We understand these changes require effort, and we're here to support you. If you have questions, need migration guidance, or run into issues, please https://support.atlassian.com/contact/.
Effective date: 25 Feb 2026 (PT)
“Community Licenses” pricing plans are now called “Social Impact Licenses.”
Social Impact customers are eligible nonprofit and social enterprise customers approved for Atlassian Social Impact (formerly Community) Licenses.
The new discounts are designed to remove cost as a barrier to adopting collaboration tools—including Marketplace apps—so social impact teams can focus on delivering their mission.
For detailed information on:
the new Social Impact and Social Impact – Global Access license types
discount levels and eligibility
expected impact on Marketplace Partners
please see the Quick Reference Guide:
https://atlassianpartners.atlassian.net/wiki/spaces/resources/pages/1330544651/Changes+to+Community+Licenses+-+Quick+Reference+Guide
From 25 Feb 2026 (PT):
Existing Social Impact customers
Automatically receive the new discounts at their next renewal (no action required from partners).
From 25 Feb 2026 (PT), the license_type field in the Transactions API and Licenses API will return:
SOCIAL_IMPACT
SOCIAL_IMPACT_GLOBAL_ACCESS
instead of the previous COMMUNITY license_type value.
Exception: COMMUNITY Licenses in the new billing system(check here to identify licenses from New Billing system here) will be updated to the new license_type post next renewal.
Action for partners:
Update any logic, reporting, or internal tooling that:
filters or segments customers by license_type
Ensure your systems recognize SOCIAL_IMPACT and SOCIAL_IMPACT_GLOBAL_ACCESS as new license_type.
As shared in our previous announcement, Bitbucket Cloud will fully sunset the cross-workspace APIs on March 31, 2026. We had previously communicated an earlier date but have decided to postpone this due to feedback from our partners.
Based on feedback, we have also released a new API that allows you to list repository permissions in a workspace for a user.
To help teams identify and migrate any remaining usage ahead of the enforcement date, we will run a series of controlled brownouts starting March 23, 2026, for one week. During each brownout window, requests using the old cross-workspace APIs will be rejected, and affected endpoints will return a 404 Not Found error. If you have made the switch to the new APIs, announced here, then you will not be impacted during the brownouts.
Dates | Brownout duration per window | Brownout starting windows (PST) |
March 23, 2026 | 120 min/2 hours | 10:00 |
March 24, 2026 | 120 min/2hours | 15:00 |
March 25, 2026 | 240 min/4 hours | 09:00 |
March 26, 2026 | 240 min/4 hours | 13:00 |
March 27, 2026 | 480 min/8 hours | 08:00 |
March 30, 2026 | 720 min/16 hours | 06:00 |
March 31, 2026 | Final removal
| |
During the brownout, if you encounter an error, please contact your app vendor. They will need to switch to using the new, support cross-workspace APIs.
After the brownout schedule completes, requests to the old cross-workspace APIs will stop working entirely at all time will no longer be supported starting March 31, 2026.
We understand these changes require effort, and we're here to support you. If you have questions, need migration guidance, or run into issues, please contact Atlassian Support.
Effective 2025-12-16, Atlassian Marketplace no longer accepts new Data Center (DC) app submissions. This change aligns with the Data Center App Submission Policy Update and Atlassian’s broader Data Center end-of-life milestones.
As part of this update, we have removed the ability to publish new DC apps from the Marketplace Partner Portal. Partners will see updated, in-product messaging in the app publishing journey to explain this change and help set expectations.
For more details, please refer to:
https://www.atlassian.com/blog/developer/from-data-center-to-cloud-the-next-chapter-for-marketplace-apps
For any concerns or requests, partners are requested to raise an Ecohelp ticket.
We have added advanced conditional logic in the Forms API responses. The ‘save form template’ now accepts requests with advanced conditional logic.
When a section has advanced conditional logic, the form response will include two new properties in the form condition input object design.conditions.CONDITION_ID.i:
operator - the logic operator between check groups, OR or AND.
groups - the list of check groups. In each check group:
operator - the logic operator between checks in the group, OR or AND.
checks - the list of checks in the check group. In each check:
fieldId - the question ID which the check depends on.
type - the comparison type, SOME_OF, NONE_OF or ALL_OF.
constraint - the list of constraint values the check depends on.
The form condition output object’s condition type design.conditions.CONDITION_ID.o.t now supports two types:
sh - show
hide - hide
Example:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
{
"design": {
"conditions": {
"15": {
"i": {
"operator": "OR",
"groups": [
{
"operator": "AND",
"checks": [
{
"fieldId": "12",
"type": "SOME_OF",
"constraint": ["1", "0"]
}
]
}
]
},
"o": {
"sIds": ["3"],
"t": "hide"
}
}
}
}
}A new RFC is ready for review at: https://community.developer.atlassian.com/t/rfc-128-local-development-mocks-for-forge-storage/99256
As part of our wider announcement for deprecation of native Bitbucket Cloud Issues and Wikis, we will be removing API endpoints that support Issue Tracker in mid-August, 2026.
Expand the More Details view below to see the full list of endpoints being removed.
Here is the full list of endpoints for Issue Tracker that will be removed:
GET/repositories/{workspace}/{repo_slug}/components
GET/repositories/{workspace}/{repo_slug}/components/{component_id}
GET/repositories/{workspace}/{repo_slug}/issues
POST/repositories/{workspace}/{repo_slug}/issues
POST/repositories/{workspace}/{repo_slug}/issues/export
GET/repositories/{workspace}/{repo_slug}/issues/export/{repo_name}-issues-{task_id}.zip
GET/repositories/{workspace}/{repo_slug}/issues/import
POST/repositories/{workspace}/{repo_slug}/issues/import
GET/repositories/{workspace}/{repo_slug}/issues/{issue_id}
PUT/repositories/{workspace}/{repo_slug}/issues/{issue_id}
DEL/repositories/{workspace}/{repo_slug}/issues/{issue_id}
GET/repositories/{workspace}/{repo_slug}/issues/{issue_id}/attachments
POST/repositories/{workspace}/{repo_slug}/issues/{issue_id}/attachments
GET/repositories/{workspace}/{repo_slug}/issues/{issue_id}/attachments/{path}
DEL/repositories/{workspace}/{repo_slug}/issues/{issue_id}/attachments/{path}
GET/repositories/{workspace}/{repo_slug}/issues/{issue_id}/changes
POST/repositories/{workspace}/{repo_slug}/issues/{issue_id}/changes
GET/repositories/{workspace}/{repo_slug}/issues/{issue_id}/changes/{change_id}
GET/repositories/{workspace}/{repo_slug}/issues/{issue_id}/comments
POST/repositories/{workspace}/{repo_slug}/issues/{issue_id}/comments
GET/repositories/{workspace}/{repo_slug}/issues/{issue_id}/comments/{comment_id}
PUT/repositories/{workspace}/{repo_slug}/issues/{issue_id}/comments/{comment_id}
DEL/repositories/{workspace}/{repo_slug}/issues/{issue_id}/comments/{comment_id}
GET/repositories/{workspace}/{repo_slug}/issues/{issue_id}/vote
PUT/repositories/{workspace}/{repo_slug}/issues/{issue_id}/vote
DEL/repositories/{workspace}/{repo_slug}/issues/{issue_id}/vote
GET/repositories/{workspace}/{repo_slug}/issues/{issue_id}/watch
PUT/repositories/{workspace}/{repo_slug}/issues/{issue_id}/watch
DEL/repositories/{workspace}/{repo_slug}/issues/{issue_id}/watch
GET/repositories/{workspace}/{repo_slug}/milestones
GET/repositories/{workspace}/{repo_slug}/milestones/{milestone_id}
GET/repositories/{workspace}/{repo_slug}/versions
GET/repositories/{workspace}/{repo_slug}/versions/{version_id}
We are introducing baseline security requirements for Atlassian Government Cloud (AGC) apps, which will take effect on Mar 31, 2026. If you have any questions regarding these new standards, please contact us here: https://ecosystem.atlassian.net/servicedesk/customer/portal/34/group/109/create/579
We’re also publishing our annual update to the general Cloud App Security Requirements for 2026, which includes new provisions for AI security, data protection, and supply chain security. See More details for highlights on this update.
Key additions to the general Cloud App Security Requirements include:
AI Security: New requirements for apps using Forge Rovo actions and agents, including validating action inputs as untrusted, implementing permission checks for admin-level actions, and accurately configuring actionVerb values.
Data Protection:
External OAuth2 clients must use Forge's OAuth2 Providers and be configured as confidential clients where supported.
Application logs must strictly exclude PII, credentials, and sensitive data.
Apps must ensure strict tenant isolation during runtime.
Apps must not execute arbitrary code by spawning child processes (e.g., using Node.js child_process).
Application Security:
Apps using Forge SQL must use parameterized queries to mitigate SQL injection risks.
Updated guidance on Content Security Policy (CSP) regarding unsafe-inline and unsafe-eval directives.
Runtime Security:
Apps must not use EOL (end-of-life) Node.js runtimes.
As part of the ongoing Marketplace platform re-architecture, we’ve updated our deprecation timelines and API details to give partners more time and clarity for migration.
What’s changed?
The deprecation date for the Marketplace V2 APIs covered in this guide has been extended to 30 June 2026.
You can find the full context, including updated timelines, replacement V3 endpoints, and partner enablement details in the Quick Reference Guide here:
https://atlassianpartners.atlassian.net/wiki/spaces/resources/pages/735608891/Marketplace+Platform+Changes+GA+and+Partner+Implications+-+Quick+Reference+Guide
Key-Value Store(KVS) editor is now available for all non-viewer app roles in the developer console for development and staging environments. Use the editor to
Add new keys and values
Update the values of existing keys
The editor is designed for fast, iterative testing, so you can quickly experiment with and validate changes to your app’s stored data.
We’re introducing display condition support to the following Jira Service Management (JSM) Forge portal modules as a preview release:
Portal footer
Portal header
Portal profile panel
Portal request create property panel
Portal request detail
Portal request detail panel
Portal request view action
Portal subheader
Portal user menu action
For these JSM modules, Forge apps can now declare displayConditions in the app manifest and have them evaluated by the host, consistent with how display conditions work for Jira and Confluence Forge modules today.
For further details, see the documentation here.
Support for Claude Opus 4.6 model is now available in Forge LLMs. This is in addition to the already supported Claude Opus 4.5 and Claude Opus 4.1 models.
Forge LLMs remain in Early Access (EAP). Due to high demand, participation is limited. To request access, join the waitlist here.
For the exhaustive list of supported models, refer to our documentation here
We've introduced two new components to UI Kit, now available in Preview: AtlassianTile and AtlassianIcon. Use these components to display Atlassian object type icons—such as stories, tasks, epics, blogs, and more—with consistent styling that aligns with the Atlassian Design System.
Both components provide fixed color, size, and styling options for Atlassian object types. Any updates to icon or tile styling in the Atlassian Design System are automatically reflected in your app.
For implementation details and examples, see the Atlassian icon and Atlassian tile component documentation.
The Connect Inspector service is moving to open source and also being deprecated. This service will no longer allow the creation of new temporary apps. Already registered temporary apps will stop recording new events, and old events will be deleted. Any apps already installed on developer sites will not be uninstalled.
Connect Inspector helped developers better understand Atlassian Connect lifecycle events and web-triggers. This service allowed developers to generate a temporary and unique Atlassian Connect app, which could be installed on a cloud development environment. This, in turn, let developers inspect the full request flow of a Connect app.
However, usage of the Connect Inspector has decreased significantly due to the following:
Atlassian Marketplace no longer accepts new Connect app listings
Local installs of Atlassian Connect apps will be locked from March 2026
Deprecating Connect Inspector allows the team to focus on Forge.
The Connect Inspector service will be discontinued by the end of February 2026.
Developers who still need similar functionality can use the open‑sourced version of the tool.
Atlassian Connect will reach end of support in December 2026. Migrate to Atlassian Forge for a more robust Events model.
Bitbucket Data Center and Server 8.19.27, 9.4.16, and 10.1.4 bug fix releases are available now!
To see the issues resolved in these bug fix releases, go to:
Rate this page: