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.
Action needed by June 30, 2026: If you have an Atlassian Bug Bounty program, it must be made public to maintain your program status and Marketplace badges.
The good news: you don't need to be fully public by then — you just need to submit an ECOHELP ticket to start the process. Submitting by June 30th protects your program.
Here's what to do:
Please note:
Tickets not submitted by June 30th will be automatically closed.
Submitted tickets that are inactive for 14 days will also be closed.
Either may result in your program being paused and the removal of associated Marketplace badges.
We’ve added a new field additionalDetails to the response object for the validate update workflows and validate create workflows APIs.
This will contain additional context if applicable related to the validation warnings and errors returned from the APIs.
The Revoke portal-only access for user JSM API is now generally available (GA). We have removed the experimental flag, meaning the API will no longer be modified without prior notice.
What's changing
GA Status: The API is no longer experimental.
Error Handling: We've updated the status code from 400 to 404 when a passed accountId does not exist.
What you need to do
If you are currently using this API, update your error handling to account for the new 404 status code when a user is not found. You can find the full technical details in the Jira Service Management Cloud REST API documentation.
We're excited to announce that the downloadable product catalog CSV, available via the Marketplace V3 Product Catalog Snapshot APIs, has been enhanced with Total Install Counts.
This new field provides the aggregate number of installations for each app. For more details see: V3-Product Catalog Snapshot API
A filter to breakdown usage of function compute by compute type (sync or async) is now available in the Forge Developer Console’s Usage and Charges section.
Sync: Synchronous function executions.
Async: Asynchronous function executions.
This filter is available on the detailed Usage view of Functions - compute usage and the Site breakdown view.
No action is required. However, we recommend using this filter to understand your asynchronous compute consumption before billing for this compute type begins on July 1, 2026. For more context, see our previous announcement: CHANGE-3120
We’ve added an optional urlFormat field to the webtrigger module in manifest.yml so you can choose which URL format Forge uses for each web trigger. This field accepts two values:
v1: uses the existing app-based URL format, and remains the default when urlFormat isn’t specified (for backwards compatibility).
v2: uses a new installation-based URL format with an improved domain and path. Use v2 for new web triggers and when you want to opt in to the newer URL style.
Future web trigger capabilities will require urlFormat: v2, and at that point urlFormat will become a required field.
We've added new components to UI Kit, now available in Preview in the latest version of @forge/react:
For implementation details and examples, see the documentation links for each component.
To update to the latest version, in the terminal from your project directory, run the following command:
npm install --save @forge/react@latest
SSH access to Bitbucket Cloud repositories via bitbucket.org will be removed after approximately six months. SSH traffic is being separated from HTTPS traffic to enable enhanced security protections on Bitbucket's public web and API endpoints.
Customers who use Git over SSH must update their remote URLs to use ssh.bitbucket.org instead of bitbucket.org. HTTPS access to bitbucket.org is not affected by this change.
What is changing
Bitbucket Cloud is splitting HTTPS and SSH traffic so that bitbucket.org will serve only HTTPS requests. All SSH-based Git operations (clone, push, pull, fetch) must use the new ssh.bitbucket.org hostname.
Migration steps
For each repository using an SSH remote, update the remote URL:
1
git remote set-url origin git@ssh.bitbucket.org:<workspace>/<repo>.gitOn first connection to ssh.bitbucket.org, verify and accept the new host key when prompted, or pre-add it to ~/.ssh/known_hosts.
Update any CI/CD pipelines, deployment scripts, or automation that use SSH to clone or push to bitbucket.org.
If your network restricts outbound SSH connections via firewall rules, ensure ssh.bitbucket.org on port 22 is allowlisted.
More details are captured in this community blogpost.
Timeline
Customers will have approximately six months from the announcement date to complete the migration. After the migration period ends, SSH connections to bitbucket.org will be refused.
To maintain system stability as our usage scales, we updated Bitbucket Pipelines to only detect the [skip ci] or [ci skip] label within the first 200 characters of a commit message. This means pipelines won’t be skipped if the label appears further in a long message.
To ensure your builds are intentionally skipped, place the label near the start of your commit message, ideally in the subject line. Manual runs are not affected by this change.
For details, read
https://support.atlassian.com/bitbucket-cloud/kb/how-to-skip-triggering-an-automatic-pipeline-build-using-skip-ci-label/.
We are removing support in Jira for permission grants that rely on certain non–group-picker custom fields. These grants work by matching a field's selected option name to a group name; a pattern that is being deprecated in favor of explicit group‑picker fields.
Effective date: May 12, 2026
Affected custom field types:
com.atlassian.jira.plugin.system.customfieldtypes:select
com.atlassian.jira.plugin.system.customfieldtypes:multiselect
com.atlassian.jira.plugin.system.customfieldtypes:radiobuttons
com.atlassian.jira.plugin.system.customfieldtypes:multicheckboxes
com.atlassian.jira.plugin.system.customfieldtypes:datetime
com.atlassian.jira.plugin.system.customfieldtypes:textfield
com.atlassian.jira.plugin.system.customfieldtypes:jwm-category
com.pyxis.greenhopper.jira:gh-epic-status
What happens after this date:
Permission grants that reference the above field types will no longer be evaluated. Affected issues may lose their expected access grants.
What you should do:
Review your permission schemes for grants that use these field types and replace them with explicit group-picker fields. See What are permission schemes in Jira? | Atlassian Support for guidance.
To identify affected schemes, go to Jira administration → Permission schemes and check for grants tied to the field types listed above.
You can now migrate a Connect Jira Issue Field module to Forge's Custom Field module. The functionality is now available for Text (text) and Rich Text (rich_text) fields.
See https://developer.atlassian.com/platform/adopting-forge-from-connect/migrate-jira-issue-fields/#text-and-rich-text-fields for more details.
The boolean usages of the autoFocus prop have now been removed from @atlaskit/modal-dialog. The previously default value of true, which automatically moves focus to the first interactive element within the modal, is now the default with no option to set it to false. This is to improve accessibility and follow the WCAG guidelines for focus within a modal dialog.
Boolean usages of autoFocus can be removed by running the included codemod.
EDITED 8 May 2026
Hello Marketplace partners,
We're excited to share that the newest improvements to Atlassian’s design language is here, as you may have seen at Team '26!
Tile & Object system
Spotlight component
Shape – Border & Radius foundations
Labelling system (for status and categorisation)
Motion foundations
These build upon on our refreshed visual language that launched last year at Team ’25 (including colour, typography, and iconography that many of you already adopted). It makes it even easier to build modern UI that is cohesive across Atlassian and Marketplace apps, with better visual clarity and accessibility.
We will be shipping these improvements to components, design tokens and guidance as part of the Atlassian Design System (ADS), and Forge UI Kit will also receive updates.
The following are in development behind feature gates. To preview the new improvements, please see Atlassian Design System documentation. We will share adoption and migration details once they are ready for use in your apps.
The Tile & Object system replaces inconsistent custom tile-like UI elements — previously scattered across products with mismatched sizes, radii, colours, and naming conventions. We now offer a single, coherent standard for representing tasks, pages, objects, and app icons.
Changes are coming to Avatar, Icon tile, Tile and Object packages to align with the new Tile system. The Icon-object package has been deprecated and replaced by Object.
Before/After of Tile System in Jira
We are introducing a modernised onboarding component for product tours and user engagement flows consistent with our improved design language. The new Spotlight replaces the deprecated Onboarding component.
Before: Onboarding Component
After: Spotlight Component
New design tokens for border widths and corner radii bring consistency to the shape language across Atlassian UI. Atlassian Design System components will be updated as well as the @atlaskit/tokens package.
Together, these foundations ensure components feel more unified and polished — rounded corners and border styles will follow a consistent system rather than being defined ad-hoc per component. For more information on whats to come, check out our border width and radius docs.
New radius tokens
New border width tokens
We’re introducing a more intuitive, accessible, and scalable labelling system that standardises consistent presentation of statuses and categorisation, supporting app-specific needs while maintaining coherence and visual clarity.
We’ve updated the visual appearance of Lozenges, Tags, and Badges to have the right level of prominence in the UI, and look and feel harmonious in every context they show up. Lozenges can now included a trailing metric, and we are introducing a new Lozenge dropdown variant, as well as a new Avatar tag to represent individuals, teams, or AI agents.
Additionally, to provide greater visual distinction and hierarchy between Lozenge and Tag, subtle Lozenge will be deprecated and need to be migrated to the new default Lozenge appearance, or where applicable to Tag instead.
Updated components: Badge, Lozenge, ad Tag
New components: Lozenge Dropdown and Avatar tag
Motion breathes life into every interaction and brand moment within apps, helping users understand spatial relationships, confirms their actions, and carries branded human expression across experiences. Our approach to motion introduces a systematic, shared language, enabling you to make good motion the easy default, not an exception.
In the initial release, we will be introducing semantic motion tokens and base tokens as the foundation of the system. Uplifted and new motion in key Atlassian Design System components are coming, as well as an improved motion primitive to replace legacy entering components and simplify applying entry and exit transitions in UI.
Learn more about how we think about motion on atlassian.design.
Motion package before vs after
We'd love to hear from you — please share on the Atlassian Developer Community!
The nodejs20.x runtime for Forge apps has reached the end of its deprecation period and is no longer supported.
Starting May 6, 2026, Atlassian will progressively block the ability to deploy or update apps using the nodejs20.x runtime. Existing deployments will continue to function, but they are provided "as-is" without support or warranties. Over time, apps using unsupported runtimes may become non-functional or vulnerable to security issues.
You must update your app's to a supported Node.js runtime (nodejs22.x or higher) to continue deploying updates.
Edit your app’s manifest.yml file
Update the app.runtime.name property to nodejs22.x or nodejs24.x
Update your local development environment to a supported Node runtime
Update your Forge CLI to the latest version
Run npm install to update your dependencies
Test your app for compatibility with any breaking changes in the Node runtime
Deploy your app to production using forge deploy -e production
For detailed instructions, see the Node.js runtime documentation.
We are announcing the deprecation of https://developer.atlassian.com/platform/forge/manifest-reference/modules/jira-issue-glance/ (jira:issueGlance), as we have replaced with https://developer.atlassian.com/platform/forge/manifest-reference/modules/jira-issue-context/ (jira:issueContext) module. The Jira Issue Glance module will soon be removed from the work items completely.
Please refer to the following documentation for more details - https://developer.atlassian.com/cloud/jira/platform/future-proof-issue-glance-implementation/
Rate this page: