Atlassian has announced the deprecation of its External Assets Platform, which will be fully shut down on December 31, 2024. We are proactively introducing new solutions to minimize any disruption, and these will be available well before the shutdown date.
We have adopted Atlassian's Forge capabilities to deliver a new custom field that replaces the External Assets Platform.
This document provides detailed guidance on the migration process to the new Asset Custom Field solution, highlighting key steps, user actions, and considerations.
On this page: |
|---|
Overview of changes
We are introducing a new custom field solution for asset management that replaces the deprecated Atlassian External Assets Platform. This change includes:
Automatic creation of a new custom field.
Migration of existing data to the new custom field.
Configuration updates to ensure seamless functionality.
Admins are required to take specific actions to ensure the transition is smooth.
Steps in the migration process
Step 1: Notification and initial setup
Admins will see a banner in the application notifying them of the upcoming changes. The banner includes:
Information about the new custom field.
A call-to-action to configure the migration option.
Actions required
Admins must:
Review the migration notification in the banner.
Choose whether to proceed with automated updates to existing issue data or manage configurations manually.
Step 2: Data migration
The migration involves:
Automatically mapping existing data from the deprecated custom field to the new custom field.
Updating issue screens and schemes to include the new field.
Important notes
No manual action is needed for data transfer.
Screens and schemes will be updated to ensure the new field is visible and functional.
Step 3: Advanced configuration options
Admins can configure the new custom field as follows:
Define specific asset filters to display relevant data.
Customize visibility based on departments, teams, or asset types.
User responsibility
Admins must:
Update filter content manually to ensure the correct data is shown in the new custom field.
Choose the relevant filters from the configuration settings.
Example
If an admin wants to display only "Full-Time Employees," they must:
Select the appropriate asset type in the filter.
Save the configuration.
Limitations
Mandatory Field Restriction: The new custom field cannot be set as mandatory due to Atlassian platform limitations.
Field Order on Screens: The field position cannot be rearranged in Jira Service Management portals.
These limitations should be communicated to users to manage expectations.
Known issues
String vs. ID Values
In certain cases, the custom field may display ID values instead of labels (e.g., showing "1" instead of "Employee"). This issue affects:
JQL queries.
Issue details in the history panel.
If you’re affected by this and would like us to consider adding a "Asset History Panel", please reach out to our support team so that we can prioritize.