Last updated Jan 26, 2023

Rate this page:

Atlassian developer changelog

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.

26 January 2023

Added New Endpoints Released for Confluence REST API v2

REST API - Confluence Cloud
More details

These granular endpoints correlate to more specific functions and allow you to be intentional about how you interact with Confluence data.

Content is broken down into specific types – so you can work with pages, blog posts, and more as discrete entities.

When retrieving bulk content, these granular endpoints also offer faster speeds (up to 30x). Our new cursor-based pagination allows quick iteration through content, instead of offset-based pagination.

This release includes support for Connect, OAuth 2.0 (3LO), and Forge apps.

You can see previous changelog entries related to Confluence Cloud REST API v2: one, two, three.

24 January 2023

Added UI modifications now support new methods

Forge - Jira Cloud Platform (excludes Jira REST APIs)

UI modifications is a Forge module that allows apps to modify fields on the Global issue create modal. You can now use the new in uiModificationsApi method, getFields, to iterate over all supported fields available on a current view form. Also, you can use the new Field API method, getType, to get the field’s type.

Fixed Forge CLI tunnel debugger now fixed

Forge - Core Platform (excludes product REST APIs)

Forge CLI version 6.4.0 introduced a bug that prevented the tunnel debugger (forge tunnel --debug) from working correctly. We fixed this in CLI version 6.4.1.

Run npm install -g @forge/cli@latest on the command line to install the latest version of @forge/cli.

18 January 2023

Deprecation Notice Project delete API now moves to trash

REST API - Jira Cloud Platform

We are changing the default behaviour for our Delete project API to improve safety for our customers. The new default behaviour will be moving the project to trash rather than an immediate deletion. You can still perform immediate deletion if you specify the enableUndo flag to be false.

This behaviour will be changed on the July 18th 2023 as per our deprecation policy.

Announcement We’re updating our API token, API key, and Repository Access Token length

REST API - Jira Cloud Platform
REST API - JSM Cloud
REST API - Jira Software Cloud
REST API - Confluence Cloud
REST API - Bitbucket Cloud
REST API - Cloud Admin

On January 18, 2023, we'll be extending the length of API tokens for Atlassian accounts, API keys, and Repository Access Tokens. This ensures new tokens and keys generated after this date are more secure and reliable. Tokens and keys created before January 18, 2023 won’t be affected.

Announcement Runtime upgraded to Node 16

Forge - Core Platform (excludes product REST APIs)

We’ve upgraded the Forge runtime to be based on Node 16. This ensures that Forge will continue receiving Node security updates until September 11, 2023.

Starting today, all apps will be deployed under this new runtime. We recommend that you re-deploy your apps to help ensure their security.

More details

For related information, see Node’s documentation on releases.

17 January 2023

Deprecation Notice Migrate to Google Analytics 4 before Google Analytics 3 deprecates on July 1, 2023

Marketplace Platform

Marketplace data is now available in GA4! Failure to migrate prior to Jul 1, 2023 will result in an interruption of data in your Google Analytics instance. We recommend migrating at least 1 month prior to Jul 1, 2023. See a step by step GA4 Migration Guide and demo video in the details below.

More details

What’s happening?

1️⃣ On Jul 1, 2023, Google Universal Analytics (UA) and Google Analytics 3 (GA3) properties will no longer process data. At this time, new data will only flow into Google Analytics 4 (GA4).

2️⃣ Because GA4 has a new data model, you cannot migrate your historical data from GA3 to GA4. Google has enabled historical data to be available on your GA3 instance until Dec 31, 2023.


How does this impact me?

You must take action to maintain visibility of your app listing page insights on Google Analytics, as well as archive your historical GA3 data.

Failure to migrate to GA4 prior to Jul 1, 2023 will result in an interruption of data visibility.

Failure to archive historical GA3 data prior to Dec 31, 2023 will result in a loss of historical data.

We recommend migrating at least 1 month prior to Jul 1, 2023. You can begin your GA4 Migration starting Jan 9, 2023 - read on to learn how.


What action is required of me?

Save these important dates & plan some capacity to migrate to GA4

We highly recommend migrating to GA4 at least 1 month prior to Jul 1, 2023

  • Jul 1, 2023 - UA and GA3 properties will no longer process data. Last date to migrate to GA4 without data interruption.

  • Dec 31, 2023 - Google Analytics will no longer store your UA/ GA3 historical data. Last date to archive your data.

Begin your 4-step GA4 migration

  1. Set up your GA4 property

  2. Provide Atlassian with your new GA4 Measurement ID

  3. Migrate from GA3 to GA4

  4. Archive GA3 historical data

Completing the first 3 steps at least 1 month before Jul 1, 2023 to avoid interruption of data visibility. Complete step 4 before Dec 31, 2023, after which Google will no longer retain historical data on GA3.

Early migration gives you a major advantage. The earlier you migrate to GA4, the more time you’ll have to recreate events, calibrate the necessary data into custom dashboards, and better understand the additional capabilities and features in GA4 that you can potentially integrate to your analytics.


Set up your GA4 property

 In Google Analytics, a property is a website, mobile application, or blog, etc. that is associated with a unique tracking ID. A Google Analytics account can contain one or more properties.
Learn more about Google Analytics properties.

  • For new Google Analytics Users: In the Admin tab, there is an option to Create Account/Create Property.

  • For existing GA3 users: In the Admin tab, go to create a new GA4 property for the account.

The following screenshots explain the flow.

 Step-by-step guide for creating a GA4 Property

Step 1: Name your property

Step 2: Complete business information

Step 3: Choose a platform

Step 4: Set up data stream for your app listing. Learn more about data streams.

Step 5: You can now see your new data stream under Admin > Data Streams

Step 6: Select the new data stream, validate details on the confirmation page and edit as needed.

This is also where you can view your GA4 property’s measurement ID!

 


Provide Atlassian with your new GA4 Measurement IDs

Your data stream will have a unique Measurement ID. You must provide Atlassian with your new GA4 Measurement IDs in order for Atlassian to trigger Marketplace data to flow to your GA4 properties. Without your GA4 Measurement ID, Atlassian will be unable to link Marketplace data to your GA4 property, and your reports will have no data flowing into them.

Example of a GA4 Measurement ID:
G-WY78KAL806

  1. To locate your GA4 Measurement ID, see the instructions here.

  2. Share this information with Atlassian through the details tab on Manage App section of your Marketplace partner account

See below guidance on how to share your Measurement IDs with Atlassian:

If you’re already on GA3, you may notice that the space to enter your GA4 Measurement ID is directly below the space where you had previously shared your GA3 Measurement ID with Atlassian. Do not delete your current Google Analytics ID - otherwise your GA3 instance will no longer receive data.

Go to the Details tab on Manage Apps


Migrate from GA3 to GA4

Give yourself at least 1 month for this part. Marketplace data will be available for you to migrate into GA4 as early as Jan 9, 2023, and you will have a maximum of 6 months to monitor both dashboards: Jan 9, 2023 through Jun 30, 2023.

  1. Set up your GA4 events as early as possible: Once your new GA4 property starts receiving the tracking data, recreate your GA3 events on GA4, and create new custom dashboards as required. Learn more on mapping GA3 functionalities to the corresponding GA4 functionalities here.
    If you’re new to GA events, read more about GA events here.

  2. Take some time to get familiar with the tool: We recommend testing and monitoring your GA3 and GA4 dashboards side-by-side for at least 1 month.

Our team has created some handy resources to help you make the most of GA4 capabilities

Prepare to archive your GA3 data: Once you are comfortable with GA4, you can move to GA4 as your single source of truth.


Archive GA3 historical data

You CANNOT move your historical data from GA3 to GA4.

Since GA4 has a new data model, Google has not enabled migration of your historical data from GA3 to GA4. The GA4 property will only collect new data for which it has been configured.

Google has enabled historical data to be available on your GA3 instance for at least 6 months after the deprecation date of Jul 1, 2023. After that, your data will no longer be accessible in the Google Analytics interface. See Google’s plans to retain your historical data for UA/ GA3 for 6 months here.

Archive your GA3 historical data by exporting it to a data visualization tool like Tableau or Looker Studio. Do this before Dec 31, 2023. Learn more about a few ways to export historical data from Google Analytics.


Demo Video: Steps 1-3

Stay tuned for a demo on Step 4!


FAQs

Question

Answer

What is Google Analytics 4 (GA4)?

GA4 is the new version of Google Analytics, designed and released by Google in 2020 which aims to better understand the customer journey. It provides more flexibility with the data, better precision, predictive capabilities and many more features.

Is it mandatory to migrate versions if I am currently using Google Analytics 3 (GA3)? 

Yes. Google has announced that all standard UA/GA3 properties will stop collecting data as of Jul 1, 2023 and you will need to migrate to GA4 to continue using Google Analytics services.

Can I use GA4 in parallel with GA3?

Yes. And we highly recommend you to do so. Because GA4 is a major update, please give yourself at least 1 month to monitor GA3 and GA4 simultaneously. You may monitor both GA3 and GA4 for a maximum of 6 months: Jan 9, 2023 through Jul 1, 2023. Starting Jul 1, 2023, data will no longer flow into GA3.

It is advised to use GA3 as the main reporting platform while you are collecting data and getting familiar with GA4 capabilities. Once, there is enough understanding, you can complete a full migration.

Can I move my historical data from GA3 to GA4?

No. Since GA4 has a new data model, Google has not enabled migration of historical data from GA3 to GA4. GA4 properties will only collect new data for which it has been configured. All historical data from GA3 needs to be exported to a separate data visualization tool like Tableau or Looker Studio.

How is GA4 different from GA3?

A few differentiators between GA3 and GA4:

  • GA4 differs from GA4 takes a more holistic approach: while GA3 used session-based data, GA4 uses events with parameters.

  • GA4 uses new privacy controls that provide greater accuracy in reporting on unique users across all platforms. Features include cookie-less measurement and behavioral and conversion modeling with predictive capabilities.

  • GA4 offers guidance without complex models in some places where data may be incomplete.

  • With GA4, there are no limits to the volume of data you can send.

  • Debugging is readily available within the GA4 reporting interface.

  • GA4 allows you to create custom reports that can be added to the left-hand navigation to make finding this data easier.  

How big is the GA3 to GA4 update by Google? 

This update is significantly larger than recent Google Analytics releases. It will require a thorough plan of action to successfully migrate to the new platform. Atlassian will enable you to trigger your GA4 events starting Jan 9, 2023.

What will happen to my GA3 data?

Google has enabled historical data to be available on your GA3 instance until Dec 31, 2023. After that, your data will no longer be accessible in GA3 or GA4. We recommend that you archive your GA3 historical data by exporting it to separate data visualization tools like Tableau or Looker Studio.

How can I get support with GA4 Migration?

If you have questions prior to Jan 9, 2023, post them in the comments below and a member of our team will be in touch.

If you need support sharing your GA4 Measurement ID on Partner Portal after Jan 9, 2023, open a ECO-HELP Support Ticket.

For support with the GA4 platform, check out Google’s GA4 Guides and GA4 Support.

Announcement User verification step added to Marketplace cloud app reviews

Marketplace Platform

Starting today, Atlassian will verify that users who post app reviews on Atlassian Marketplace cloud app listings either:

a) have the relevant app actively installed on their instance, or

b) had the relevant app installed on their instance in the last 6 months

Read more on the Developer Blog: New improvements to app reviews on the Atlassian Marketplace

More details

After a reviewer submits their post, Atlassian will verify that they have or recently had the app installed before the review is published on the Marketplace listing. This will add a short delay between submission and publication.

Added New Endpoints Released for Confluence REST API v2

REST API - Confluence Cloud
More details

These granular endpoints correlate to more specific functions and allow you to be intentional about how you interact with Confluence data.

Content is broken down into specific types - so you can work with pages, blog posts, and more as discrete entities.

When retrieving bulk content, these granular endpoints also offer faster speeds (up to 30x). Our new cursor-based pagination allows quick iteration through content, instead of offset-based pagination.

This release includes support for Connect, OAuth 2.0 (3LO), and Forge apps.

You can see previous changelog entries related to Confluence Cloud REST API v2 here and here.

16 January 2023

Deprecation Notice Start issuing issuers with native value in OAuth tokens

OAuth 2.0 (3LO) Platform (excludes product REST APIs)

On the Apr 17, 2023, the value of the issuer claim of OAuth access and refresh tokens will be:

  1. Updated from Auth0 (https://atlassian-account-prod.pus2.auth0.com/)

  2. Changed to the native Atlassian value (auth.atlassian.com).

Currently, this is not specified in our API documentation. For this reason, we don’t expect you to verify OAuth token issuer claims as Auth0. We're giving 3 months for the deprecation period until Apr 17, 2023.

12 January 2023

Deprecation Notice Get user accountIds REST API

REST API - Confluence Cloud

We are deprecating the Get user accountIds REST API in Confluence Cloud.

On July 12, 2023, the GET /wiki/rest/api/user/bulk/migration endpoint will be removed. If you require this endpoint for GDPR-related migrations from usernames/userkeys to Atlassian Account IDs, make sure to complete them before this date.

More details

In 2018, we deprecated usernames and user keys as valid forms of user identification in the REST API, in order to improve user privacy in accordance with GDPR. These forms of user identification were removed in April 2019.

We introduced this endpoint in March 2019 to enable developers to migrate these deprecated forms of identification to Atlassian Account IDs (AAIDs). Because its purpose is migration, it only supports user keys and usernames for users created before the GDPR-related deprecation was announced. Developers should have completed their migrations at this point, so we’re sunsetting this endpoint.

5 January 2023

Removed Bitbucket no longer supports personal Connect apps

Connect - Bitbucket (excludes Bitbucket REST APIs)

We’ve discontinued support for personal Connect apps in Bitbucket. Please see the deprecation notice for more details.

4 January 2023

Announcement New Privacy & Security Tab coming to cloud app listings - questions available now

Connect - Core Platform (excludes product REST APIs)
Forge - Core Platform (excludes product REST APIs)
Marketplace Platform

To streamline the cloud app assessment and procurement process for customers and Marketplace Partners, we plan to add a new Privacy & Security tab to each Marketplace cloud app listing.

You can start preparing information to fill out the new tab for your cloud apps using the questions documented here.

This new Privacy & Security tab will replace the Security Self Assessment for cloud apps. It will also replace the Security Self Assessment requirement for Cloud Fortified apps starting 6 months from when the API documentation and web form are released.

More details

We will follow up in the coming weeks (estimate: February) with API documentation and more detailed information on the web form to submit responses for your Privacy & Security tabs. We plan to make the new tab live for customers in March 2023.

In the meantime, you can start preparing responses for the tab using the questions documented here.

For customers that have security, compliance, and privacy requirements, this new tab on Atlassian Marketplace will provide key details about cloud apps in a consistent and discoverable place. It will also help Marketplace Partners more easily showcase investments in cloud app privacy and security.

View the new documentation here.

19 December 2022

Added New FieldUpdateOperation type added to the Create issue API v3

REST API - Jira Cloud Platform

We’ve added copy to the list of FieldUpdateOperation types of the Create issue API v3. This operation allows you to create issues with field values copied from source issue(s). It’s currently supported for two fields:

  • issuelinks

  • attachment

16 December 2022

Announcement Atlassian support can now trigger transfer cancellation on customer's request

App Migration Platform

Atlassian support can now cancel transfers upon customer’s request. This was previously an experimental feature.

When this is requested, your cloud app will receive a new event with the type transfer-cancellation-requested and you may need to take an action.