Last updated Jan 17, 2023

Rate this page:

Changelog

This changelog is the source of truth for all changes to the Marketplace that affect people publishing apps.

Posts are made in the Marketplace announcements category of the developer community when the changelog is updated. Subscribe to the Marketplace announcements category to get notifications.

17 January 2023

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

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

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.

4 January 2023

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

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.

12 December 2022

Fixed Updated name and description fields of few scopes for Marketplace apps

The name and description fields for the following scopes have been modified in Marketplace. These changes appear in the REST API responses and App listing page (Integration Details).

  • read:me

  • read:servicedesk-request

  • write:servicedesk:jira-service-management

  • write:servicedesk-request

  • manage:servicedesk-customer

Note: There is no change in the scope key. The existing scope keys will continue to work.

More details

The table lists the before and after differences between the modified scope names and descriptions fields:

Before

After

“key":"read:me", "name":"View user profile", "description":"View the profile details for the currently logged-in user."

“key":"read:me", "name":"View active user profile", "description":"View the profile details for the currently logged-in user."

“key":"read:servicedesk-request","name":"View Jira Service Desk request data", "description":"Read customer request data, including approvals, attachments, comments, request participants, and status/transitions.Read service desk and request types, including searching for request types and reading request type fields, properties and groups."

“key":"read:servicedesk-request","name":"View Jira Service Management request data", "description":"Read customer request data, including approvals, attachments, comments, request participants, and status/transitions.Read service desk and request types, including searching for request types and reading request type fields, properties and groups."

“key":"write:servicedesk:jira-service-management","name":">-","description":"p the add organisations, customers and request types to"

“key":"write:servicedesk:jira-service-management","name":"Allows the app the add organisations, customers and request types to service desks","description":"Allows the app the add organisations, customers and request types to service desks"

“key":"write:servicedesk-request","name":"Create and manage Jira Service Desk requests","description":"Create and edit customer requests, including add comments and attachments, approve, share (add request participants), subscribe, and transition."

“key":"write:servicedesk-request","name":"Create and manage Jira Service Management requests","description":"Create and edit customer requests, including add comments and attachments, approve, share (add request participants), subscribe, and transition."

"key":"manage:servicedesk-customer","name":"Manage Jira Service Desk customers and organizations","description":"Create, manage and delete customers and organizations.Add and remove customers and organizations from service desks."

"key":"manage:servicedesk-customer","name":"Manage Jira Service Management customers and organizations","description":"Create, manage and delete customers and organizations.Add and remove customers and organizations from service desks."

7 December 2022

Announcement App editions build instructions available for cloud apps built on Connect

Instructions are now available in the Partner Portal to help Marketplace Partners start building a Free or Advanced edition of cloud apps built on Connect.

More details

Marketplace Partners who are interested in adding editions to their Connect cloud apps can start building out editions in the background now.

Forge instructions to come early next year.

  1. See the App Editions hub in the Partner Portal for details on App Editions.

  2. Find Connect build instructions here

1 December 2022

Announcement Atlassian has enabled app purchasing on the new billing engine for cloud customers without apps

Cloud app purchasing has been enabled on Atlassian’s new cloud billing engine.

More details

Currently, the only customers who are on the new billing engine are new cloud customers who do not have any Marketplace apps installed. However, if these customers choose to install apps moving forward, they will make their purchases using the new billing engine.

Partners should prepare in the following ways:

24 November 2022

Removed Cloud Fortified: Removal of StatusPage metrics UI

StatusPage has been replaced by Developer Console as the metrics UI for Cloud Fortified apps. The StatusPage metrics UI was deprecated on October 24, 2022.

4 November 2022

Added New sales support and approvals role under contacts on Marketplace partner page

We’ve added the sales support and approvals role under the contacts tab on the Marketplace partner page. This role helps Atlassian employees reach out to the right people in partner organizations for support on sales and discount approvals. Partners can assign a contact for this role using the Add Contact button or the Manage Contact option.

By default, primary contacts do not have this role assigned to them. If required, partners can assign this role to their primary contact.

Read the Blog.

More details

 

 

31 October 2022

Announcement Get help for Data Center and Cloud Fortified at Developer and Marketplace support

The following service requests have been deprecated and merged into Developer and Marketplace support [ECOHELP]:

  • Cloud Fortified Apps Program (ERCLOUD)

  • Data Center app technical review (DCHELP)

  • Server and Data Center app submission approval (AMKTHELP)
    **All new Cloud, Server and Data Center app submission approval tickets will be created in the ECOHELP project instead of AMKTHELP.

:warning: The ERCLOUD and DCHELP service desks will:

  • No longer accept new tickets

  • Allow read-only access to your tickets from legacy projects

We’ve also added a new request type. You can now visit Developer and Marketplace support to ask general questions about:

  • Atlassian Marketplace

  • Cloud Fortified

Announcement New Marketplace Security Requirements Are Now in Effect

Several months ago, we announced new security requirements for cloud apps, which take effect today (October 31). As of today, all Marketplace apps and Trello Apps (Power-Ups) are expected to meet the new requirements.

Maintaining a secure Marketplace is a collective effort, shared by Atlassian and partners. The new requirements reflect the most current best practices for building secure apps and provide platform-specific guidance. They set Atlassian’s baseline standard for cloud app security, and will be updated annually to ensure alignment with industry standards.

The new requirements apply across five categories: Authentication & Authorization, Data Protection, Application Security, Privacy, and Vulnerability Management. They benefit both developers and customers by providing guidelines for building secure apps and elevating the trust posture of our cloud ecosystem.

Read the blog to find out more about the changes that take effect today, and how we will validate that apps are following security requirements moving forward.

Read the blog

24 October 2022

Removed Cloud Fortified: Removal of metrics from the program

The following Connect metrics have been removed from the Cloud Fortified program:

  • Iframe load success rate

  • Iframe load success rate from app server

  • Synthetic check success rate from app server

Deprecation Notice Cloud Fortified: Deprecation of Metrics publish API

The Metrics publish API for Cloud Fortified will be removed after Apr 24, 2023.

Metrics being sent to the API have been removed from the program.

Deprecation Notice Cloud Fortified: Deprecation of StatusPage metrics UI

StatusPage will be replaced by Developer Console as the metrics UI for Cloud Fortified apps. StatusPage will be available until November 24, 2022.

Announcement Cloud Fortified: New UI for metrics in Developer Console

More details

If your Atlassian account is associated with a Marketplace partner profile, you can view metrics for all Cloud Fortified Connect apps that belong to that profile in the Developer console.

Added Cloud Fortified: Upcoming changes to App availability success rate

On Apr 24, 2023, Cloud Fortified Connect apps are required to meet new requirements for App availability.

  • All app base URLs that receive customer traffic will be monitored.

  • A single healthcheck path will be used for all app base URLs.

  • Only the HTTP status code 200 will be accepted.

  • A response must be returned within 3 seconds.

  • HTTP redirections will not be followed.

More details

App base URLs

App healthcheck requests will be made to each distinct base URL that receives customer traffic, including the latest version of the app, the last patch version for each minor version with installations, and all regions for app versions that support data residency. The 99.9% 28-day target SLO will be applied to each app base URL individually.

App healthcheck path

App healthcheck URLs will be determined by applying a healthcheck path provided by the Marketplace Partner to each of the applicable app base URLs. Initially, the healthcheck path provided via the Cloud Fortified app approval request will be used. If you would like to change your healthcheck path, please submit a request here. We are also exploring making self-serve modification of the healthcheck path available later.