Atlassian developer changelog

We have now added the ability to use the following as dynamic modules, available under Forge’s Early Access Program (EAP):

• Issue Action

• Issue Activity

• Issue Panel

• Issue Context

• Custom Field

• Custom Field Type

• JQL Function

• Entity Property

To start testing, sign up for the EAP here.

We’re introducing support for multiple field contexts per project in Jira Cloud. This allows more than one context to exist for a single project across different issue types, and multiple default values to be set for different issue types within a single context.

As part of this change, the existing REST APIs for managing context default values are being deprecated and will be replaced by new APIs that support multiple default values.

Deprecated APIs:

• Get custom field contexts default values

• Set custom field contexts default values

Deprecation Timeline:

• July 2026: New default values REST APIs introduced. Existing "Get" API will return an error for contexts with multiple defaults; "Set" API will override all issue types in a context.

• October 2026: Existing default values APIs will be removed.

What you need to do:
If you use the affected APIs, plan to migrate to the new REST APIs before October 2026.

You can now nominate genuine migration blockers or major customer‑impact risks via the “Request review” flow on FRGE issues.

This flow will allow us to triage and assess requests to address remaining blockers to Forge migration before Connect end of support in December 2026. We’ll review requests over 3 monthly cycles, then freeze decisions.

Please review for existing tickets before creating new FRGE tickets. You may also review the announcement.

We’ve upgraded the Lucene search library from version 7.3 to 10.3.1 for the upcoming Jira 12 release. This upgrade improves search performance and accuracy but includes breaking API changes and requires a full reindex.

Key changes:

• Full reindex required

• API updates

• Configuration cleanup

• Label ordering fix

View the full list of changes

The KVS and Custom Entity Store now allow you to batch multiple delete and get operations. These new capabilities are included in the latest version of the @forge/kvs package.

Bitbucket Data Center 10.2 is available for upgrade!

Get the most out of handy features, such as responsive pull requests on mobile and merge queues!

Learn more about the new features in the release notes

Get Bitbucket Data Center 10.2

You can now generate Atlassian API tokens that are scoped to only the permissions required for the Forge CLI. Update to Forge CLI version 12.15.0 or later to start using scoped tokens.

Previously, Forge CLI relied on tokens with broad permissions. Scoped tokens help you follow security best practices, apply the principle of least privilege in CI/CD pipelines, and reduce the blast radius of a compromised token.

What you need to do

1. Update your Forge CLI to version 12.15.0 or later.

2. Run forge login and follow the instructions to create a Forge scoped API token.

Existing unscoped tokens will continue to work.

The Forge Model Context Protocol (MCP) Server is now generally available. This remote MCP server enables Forge app developers to use coding agents with up-to-date Atlassian Forge and Cloud documentation, including markdown-based guides, module catalogs, and manifest references. The Forge MCP Server also offers a search feature for Forge reference documentation and implementation patterns. These features are designed to streamline Forge app development in AI-powered workflows.

This release packs performance, reliability and search relevance improvements. We invite you to try the Forge MCP Server and share your feedback to help us improve.

Effective March 2, 2026, we are starting the phased enforcement of points-based quota rate limits for Jira and Confluence Cloud REST APIs. The rollout will begin with a small percentage of apps and gradually expand over several weeks, allowing us to closely monitor progress and minimize any disruption. API requests will start consuming points based on the work they perform, with app-level quotas applied consistently across two tiers:

1. Global Pool (Tier 1)

2. Per-Tenant Pool (Tier 2)

All Forge, Connect, and OAuth 2.0 (3LO) apps are in scope. API token-based traffic is not affected. The vast majority of apps are already operating well within these limits and will not be affected.

• To learn whether points-based quota enforcement has started for your app, inspect your API response headers. Quota-related headers with a Beta- prefix (e.g., Beta-RateLimit-Policy: "global-app-quota") indicate enforcement has not yet begun for your app. When enforcement begins, these transition to their non-prefixed equivalents (e.g., RateLimit-Policy: "global-app-quota").

• Jira REST APIs use multiple rate-limiting systems (quota, burst) that are transitioning to a unified structured headers(Beta-RateLimit, Beta-RateLimit-Policy)independently. The Beta- prefix on a header indicates that the system has not yet transitioned to production for your app. Use the policy name in the header (e.g., "global-app-quota" or "tenant-app-quota" for quota and for burst"jira-burst-based" ) to identify which system a header belongs to. Additional rate limit policy transitions to this unified header will be announced separately.

• We plan to discontinue sending quota rate limit values via the X-RateLimit-* headers in the future. A timeline will be published separately.

For full details on how points are calculated, quota tiers, unified header format and values, and best practices for handling rate limits, please refer to:

• Jira Cloud Platform rate limits

• Confluence Cloud rate limits

Marketplace partners, we’re introducing a new pricing plan for a small group of Atlassian Foundation nonprofit customers.

The Atlassian Foundation provides free Atlassian product licenses (“Foundation Free”) to a select group of close nonprofit partners (around 30 organizations globally). Until now, these nonprofits have paid full commercial price for Marketplace apps on top of their free Atlassian product licenses.

Effective February 25, 2026, we are introducing a 75% discount on Marketplace apps for customers with Foundation Free licenses, aligning their pricing with our other social impact discounts.

All Marketplace apps are automatically opted in to this new pricing plan.

From 25 Feb 2026 (PT), licenses opted into the new pricing plan will have the license_type field in both the Transactions API and Licenses API set to:

• Foundation-Free

For apps impacted as of February 25, a partner manager has emailed you with more details.
For more information about Foundation Free and other app discount programs, learn more here.
For questions or concerns, please contact social-impact-teams@atlassian.com.

We've introduced three new Forge triggers for Bitbucket deployment events. These triggers allow your Forge app to respond to deployment lifecycle events in Bitbucket Pipelines.

The new triggers are:

• avi:bitbucket:pending:deployment — Fires when a deployment is pending

• avi:bitbucket:started:deployment — Fires when a deployment starts

• avi:bitbucket:completed:deployment — Fires when a deployment completes

To use these triggers, add them to the trigger section of your app's manifest.yml file. Each trigger provides deployment event data including environment, state, and pipeline details.

For more information, see Bitbucket events.

Following this deprecation announcement on Feb 17, 2026, the Connect Inspector Service is now decommissoned.

We recommend migrating to Atlassian Forge for a more robust Events model, as Atlassian Connect will reach end of support in December 2026.

Developers who still need similar functionality can use the open‑sourced version of the tool.

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.

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.