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.
We’re happy to present the third Early Access Program (EAP) build of Jira Software 11.0 and Jira Service Management 11.0. To find out what’s in scope of this EAP release, refer to Preparing for Jira 11.0.
You can download the current EAP from this page. If you’re using maven.atlassian.com, the version is 11.0.0-m0012.
This EAP release isn't for production or demonstration use.
Crowd 7.0 EAP03 milestone is available now for testing.
To find out what else changed, check out Preparing for Crowd 7.0 or download the latest EAP
When an app moves from Connect to Forge today, developers can opt-in to automatically roll out the Forge version to existing Connect customers. Following the introduction of Forge bulk-upgrades, from Aug 18, 2025 the first update from Connect to Forge will now automatically rollout to customers when an app is eligible. Rollouts will now also occur over a 120 hour (5 day) period, rather than the existing 96 hours utilised during the preview.
Apps which have already moved from Connect to Forge and have not opted in for this behaviour will see customers progressively updated if their latest Forge version is eligible from Aug 18, 2025.
A Confluence 10.0 beta 3 version is available now for testing. To find out what’s changed, check out Confluence 10.0 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.
We've introduced support for all Forge custom field types on the Jira Service Management portal view. This update allows you to specify the portal-view experience in the view entry point when using UI Kit for app rendering. The goal is to improve the flexibility and functionality of custom fields in the Jira Service Management portal.
Additionally, Forge custom fields on Jira Service Management portal requests are now generally available.
We're also introducing unlicensed access support for Forge custom fields on the Jira Service Management portal. Documentation for it can be found here: https://developer.atlassian.com/platform/forge/access-to-forge-apps-for-unlicensed-jsm-users/.
For more information on Forge custom fields, see the https://developer.atlassian.com/platform/forge/manifest-reference/modules/jira-custom-field/ or https://developer.atlassian.com/platform/forge/manifest-reference/modules/jira-custom-field-type/
We’re launching a Forge module to allow extension of the new home dashboards that are currently in open beta. This early access program (EAP) will enable partners to test the new module, and provide feedback and requests.
We plan to run this EAP for roughly 3 months and we are particularly keen to hear what is missing from the module and the additional areas of extensibility we can provide.
As per the Atlassian Developer Terms, EAPs are offered to selected developers for testing and feedback purposes. APIs and features under EAP are considered “Early Access Materials” (set forth in section 10 of the Atlassian Developer Terms) and are unsupported, subject to change without notice, and are not recommended for use in production environments.
To participate, please sign up for the EAP here.
We've updated the payment method for US-based bank accounts of Marketplace Partners from Wire to ACH (Automated Clearing House) transfers.
In July 2025, our Accounts Payable Team will perform a penny test payment of $1 via ACH to the routing number you provided in the Marketplace portal to verify its accuracy. If your current routing number does not accept ACH payments, the test payment will be returned to us.
Marketplace Partners will be notified if any updates are required. We recommend reviewing your banking information in the Marketplace Portal to ensure it supports ACH payments.
ACH transfers typically take 1-3 business days to reflect in your bank account. You may notice payments appearing around 3 days later than usual, similar to current processing times, unless affected by holidays, weekends, or payment issues.
If you have any questions or need assistance updating your banking details, contact us through the AP Service Desk.
Rollout: Progressive rollout by tenant. IMPLEMENTING
Updating workflows via the Bulk update workflows API will discard existing draft workflows that are associated with the workflow.
This change is being made because draft support will be discontinued with the retirement of the old workflow editor.
We are removing documentation for internal APIs from public docs for graphql APIs (from Connect Service section). These APIs are meant to be used by Atlassian experiences only and we do not support these APIs for public consumption.
The APIs for which docs are removed are:
extensionsEcho
extensionContexts
extensionContext
extensionsByKey
apps
app
appHostServices
appHostServiceScopes
ecosystem / userGrants
ecosystem / checkConsentPermissionByOAuthClientId
ecosystem / userInstallationRules
ecosystem / appInstallationsByContext
ecosystem / appInstallationsByApp
ecosystem / appVersionRollout
ecosystem / globalInstallationConfig
ecosystem / appVersionEnrolments
ecosystem / appInstallationTasks
ecosystem / userAccess
ecosystem / appEnvironmentsByOAuthClientIds
ecosystem / appByOauthClient
ecosystem / forgeMetrics
ecosystem / forgeAuditLogs
ecosystem / forgeContributors
ecosystem / appPoliciesByAppIds
ecosystem / dataClassifications
ecosystem / fortifiedMetrics
ecosystem / appsInstalledInContexts
ecosystem / marketplaceData
ecosystem / forgeAlerts
appInstallationTask
installApp
uninstallApp
upgradeApp
subscribeToApp
unsubscribeFromApp
Atlassian previously announced that customer general availability (GA) for multi-instance pricing would move to the fourth quarter of 2025. We are pleased to share that, while GA is still planned for Q4, we have launched a closed Early Access Program (EAP) with customers. This EAP will help us ensure we deliver a high-quality, robust feature.
In order to help Marketplace Partners accommodate larger customers, Marketplace cloud app pricing will be adjusted to match parent product pricing. We increased the number of users that customers can license on Jira Cloud from 50,000 to 100,000 on Jun 26, 2025
Beginning Jul 9, 2025, the pricing tiers for Jira cloud apps will be increased up to 100,000 users, a 100% increase from the previous limit of 50,000 users, with the following new pricing tiers added: 50,001 - 60,000 60,001 - 70,000 70,001-80,000 80,001-90,000 90,001-100,000 .
Transactions for KVS and Custom Entity Store is now generally available (including its REST API).
This feature allows multiple operations in a single transaction, ensuring that all operations are either committed or rolled back together if one fails. When used in the Custom Entity Store, you can add conditions to operations.
While version 3 of the Marketplace Review APIs is still under development, we’re releasing the documentation for these reporting APIs early to help you prepare for the upcoming changes. This release includes a preview of the API documentation schema and examples of API requests and responses.
To ensure smooth transition with the upcoming changes, we recommend to review the API documentation to understand and prepare for the upcoming changes.
Here are some helpful suggestions for you to consider:
Transition planning: Based on this documentation, it may be helpful to assess the bandwidth required for these changes and incorporate them into your roadmaps. Reviewing this documentation could provide a clearer understanding of the new APIs and help you accurately estimate the efforts involved in the transition.
Project planning: Consider preparing your execution plans and project plans so that you’re ready to hit the ground running once the APIs become available.
Staying informed: Keeping an eye out for upcoming communications from the Marketplace team can help you stay updated on timelines. Look out for updates via changelogs, enhancements to the quick reference guide on the Partner Portal, DAC, and other channels.
Description:
Bitbucket Data Center and Server 8.19.20 and 9.4.8 bug fix releases are available now!
To see the issues resolved in these bug fix releases, go to:
A Confluence 10.0 beta version is available now for testing. To find out what’s changed, check out Confluence 10.0 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.
Rate this page: