Shutdown Notice: Update on deprecation of the External Assets Platform

Hello Developer Community,

We’re reaching out with an important update concerning the External Assets Platform.

Shut Down Date

Following our previous deprecation announcement, we will shut down the ‘External Assets Platform’ from 31 December 2024 as part of our ongoing efforts to deliver the most streamlined and integrated service management solutions.

This means the ‘External Assets Platform’ custom field will cease to work from 31 December 2024, and all remaining components will be shut down and removed over the following weeks.

We understand the challenges that come with such changes, especially when it involves a service you rely on. Our commitment to providing an improved experience remains our top priority, and this decision was made with a long-term vision for the growth and enhancement of our products and your apps.

What This Means for You

Shutting down the ‘External Assets Platform’ means:

  • Related custom fields will be removed and will no longer show in Jira, and any JQL using these fields will cease to function.
  • The REST API will no longer be available, all existing apps or integrations built using those APIs will cease to work after the shutdown.
  • All related data currently stored will be deleted. The Atlassian Data Retention policies will be adhered to.

If you’re a customer currently using the ‘External Assets Platform’ to add context to your Jira issues, we recommend you consider adopting Assets in Jira Service Management, available to Premium and Enterprise customers. Assets allows you to use the Assets objects custom field to display your objects on Jira tickets, and gives you the ability to display your Assets data within Confluence, along with many other features. Try Premium for free.

If you’re an app developer currently using the ‘External Assets Platform,’ we encourage you to transition to building apps that integrate with our native Assets capability in JSM Cloud. To support this, we launched Forge and Oauth2.0 support for Assets last year, and more recently added JWT authentication for Connect apps on Assets.

PLEASE NOTE that the ‘External Assets Platform’ is completely separate from Assets in Jira Service Management. Assets, including its ‘external imports’ import type, will remain unaffected by this change.

Support and Guidance

We appreciate your understanding and cooperation as we make this shift. Your support allows us to evolve and enhance our offerings - ensuring a better, more integrated experience for all users. Please don’t hesitate to reach out with any questions, concerns, or feedback, and thank you for being a valued member of the Atlassian Developer Community.

Warm regards,

The Atlassian Team