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.
Marketplace has implemented a minor adjustment to the filtering logic within the license report. Community licenses will now be included in the paid license filter in the license reporting user interface.
Community licenses are subscription-based licenses offered at a 75% discount off the list price. Currently, these licenses can be filtered out using the free filter in the license reporting user interface (UI). Since customers do pay a portion of the subscription and these licenses are classified as paid, we are transitioning these licenses to be included under the paid filter in the licensing UI.
Partners can access their license report to explore this enhancement. We will continue to refine our filters in the future.
We’re happy to introduce a new Jira Forge product event:
Project version deleted - avi:jira:deleted:version
Follow the link above to read the event’s documentation.
As communicated earlier and as a part of our overarching strategy to enhance our core foundations, we are in the process of upgrading our tech stack. With that, we are implementing minor experience enhancements to the Downloads and Versions tab on the Marketplace partner portal:
Implementing the "Atlassian Design System" to ensure consistency and coherence across all Marketplace interfaces.
Introducing accessible charts featuring new colors and patterns to improve the readability of the chart on Downloads tab.
Improving the readability and usability of version listing by enabling a focus on hosting while viewing the released versions on Versions tab.
The enhanced experience will be introduced gradually, starting Nov 25, 2024. Initially, a small percentage of partners will have access, with a phased expansion to all partners over the following week. The objective is to complete the rollout to all our partners by Dec 4, 2024.
For more details, you can refer the quick reference guide.
UI modifications, the Forge module that allows apps to modify fields, now supports the original estimate field on the Issue view.
For more information, see the list of supported fields for Issue view.
Forge app templates for rovo:agent and actions are only available in Forge CLI 10.8.0 and later versions.
Run npm install -g @forge/cli@latest on the command line to install the latest version of @forge/cli.
Note: This change won’t impact any existing apps.
Bitbucket Cloud now allows custom merge checks to be configured at the workspace and project levels and enables rules set at higher levels to be inherited, reducing redundant configurations. The UI has also been redesigned to offer clearer guidance around the initial setup of the feature and make it easier for admins to configure checks across all levels.
For full details, refer to to our blog post.
We have added a new API to retrieve authentication policy information for a specified list of managed users.
This feature supports bulk actions, allowing information to be gathered for multiple users simultaneously.
This API allows you to retrieve the following information:
policyId
Date the user was added to the policy
We’ve stopped injecting stylesheets for Connect apps via inline styles, in favour of loading from the Connect CDN. This affects the Theming API and dynamic content macros that supported the legacy Confluence editor.
We originally announced this 6 months ago, in line with our standard deprecation policy. It is now live for https://developer.atlassian.com/cloud/confluence/developer-canary-program tenants, and will roll out to all customers widely throughout this week.
If your app doesn’t use the above Connect features, or doesn’t use a Content Security Policy (CSP) for style-src, no action is required. Otherwise, please read the details here or see https://developer.atlassian.com/platform/marketplace/security-requirements/#connect-apps on how to modify your CSP to support these changes.
To support these changes in your app, if you're using a Content Security Policy that sets the style-src policy, you must add the Connect CDN (https://connect-cdn.atl-paas.net) to your policy to allow these stylesheets to be injected. It's safe to remove unsafe-inline from your policy if you've been using it up until now.
The stylesheets mentioned here were included automatically via the Connect JS script, not manually by the app vendor. There are two circumstances under which Connect injected stylesheets into your app:
The first is only for apps which opted in to the Theming API.
The theme stylesheets previously loaded via an inline stylesheet, which forced vendors to adopt the insecure unsafe-inline policy, and is the main motivation for this change.
The second location is only for dynamic content macros.
We injected a stylesheet with CSS classes representing colors from the legacy Confluence editor.
This happened without opt-in, to be backwards-compatible with macros created in the legacy editor.
This injection was done via CSSOM, not inline styles, and therefore isn’t impacted by style-src CSP rules currently. However, it is also now being served from the CDN.
To summarise, all styles are now being loaded from the CDN, and the inline/CSSOM methods have been removed.
Marketplace is introducing a logic in the license report for partners to improve the quality of the data we provide. Licenses that do not possess a valid cloud ID, are inactive and do not have a valid transaction will be excluded from the license report.
Licenses enter this state in a specific edge case related to app provisioning. If our system encounters a failure during the app provisioning process (after creating an entitlement). We deactivate the license later, but that can take up to 7 days. During this time, there may be instances where the license appears in the report without a corresponding cloud ID, and lacks a valid transaction. Moving forward, after approximately 7 days, these types of licenses will no longer appear in the license report. While the likelihood of this occurring is minimal, some edge cases/system errors can still cause these.
Please note, we will not perform a historical update to the data. Partners will still be able to view historical licenses that do not have a valid cloud ID and may be active or inactive with or without historical transactions.
Connect On Forge apps supporting Server To Connect app migration path can register for app migration webhook on their manifest as detailed here.
The navigation changes to Jira, JSM, JPD, and Atlassian Home have now moved from EAP to Beta. For partners, this is an extension of the previously announced EAP. This extended EAP will enable partners to test the new navigation and assess how apps will adapt to the proposed changes. Unlike the previous EAP, the design direction is now near final, so we recommend partners start adopting the new navigation.
As part of the extended EAP, we’ve set up a dedicated group on CDAC where you can discuss these changes. To join the beta launch, register through the EAP form.
Please visit the community post https://community.atlassian.com/t5/Navigation-Refresh-articles/What-s-changing-in-Apps-with-Atlassian-s-Beta-launch-of-New/ba-p/2871925 where you will find detailed information about the changes, recommendations, and a comprehensive FAQ section tailored for our partners.
A Confluence 9.2 beta version is available now for testing. To find out what’s changed, check out Confluence 9.2 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.
Progressive Rollout: This change will be applied to all sites over the coming weeks.
Following the previous deprecation notice, changelogs for Epic Link and Parent Link field values are no longer available from Jira Cloud REST API. We recommend using the IssueParentAssociation changelog items instead.
For webhooks in Jira, we recommend consuming the IssueParentAssociation items, as mentioned in this community announcement (see Change 6).
Starting in December, we plan to gradually rollout a change to improve how apps are organized in Confluence’s page overflow menu into an Apps item, that will help the menu scale better with more items. See More details for imagery.
No work is required from developers due to these changes. Your apps will automatically appear in the Apps item.
As discussed in an RFC, apps will be organized into an “Apps” item in the overflow menu and given a higher relative position. Accessing apps will require no additional clicks as apps will appear upon hover.
Note that apps in the overflow menu in live pages are already organized this way.
As part of a larger Marketplace Technical foundations initiative to improve feature delivery rate, performance and reliability of Marketplace, we’re deprecating more legacy REST APIs. Please read further to understand the changes.
Marketplace V1 REST APIs changes:
Last month on 24th October, 2024, we announced the deprecation the V1 APIs intended for use by the marketplace partners. We are now announcing deprecation the remaining V1 APIs, which are intended to be used by Atlassian applications. These will be removed after a period of approximately 2 months from now on 10th January, 2025(Friday) along with the rest of the V1 APIs. Please see the More Details section for the APIs list.
Marketplace V2 REST APIs changes:
We’re also announcing here the deprecation of V2 APIs that are intended for use through the Atlassian applications only. Please see the More Details section for the APIs list. These will be removed after a period of approximately 6 months from now at the end of May, 2025.
p.s. As stated, all of these APIs are intended for Atlassian usage and therefore will not be supported in the future and will be deprecated.
Rate this page: