Atlassian has announced the deprecation of its External Assets Platform, with a complete shutdown scheduled for . To ensure a seamless transition and minimize disruptions to your workflows, we are introducing a new Asset Custom Field, built on Atlassian's Forge capabilities, as a replacement.
This guide provides detailed instructions for migrating to the new solution, including essential steps, required actions, and key considerations to help you adapt effectively.
On this page: |
|---|
Overview of changes
External Assets Platform custom field is gone, but we are offering the new Asset Custom Field to replace it.
There is a migration of existing data to the new custom field.
You may need to perform some configuration updates related to filters to ensure seamless functionality.
Admins are required to decide on the best way to go for their organization and accordingly take specific actions to ensure the transition is smooth.
Migration steps
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:
Click the Configure the migration option.
If you’d like to proceed with automated updates to existing issue data, check the Yes, update them box. Be aware that this process may trigger automation rules or impact reports.
If you’d like to manage configurations manually, leave it unchecked.
What happens if you leave it unchecked?
Once the External Assets Platform goes offline on , you will lose all the asset data you stored in the old custom field. If you leave this unchecked, you will need to migrate this information one by one.
Step 2: Data migration
The migration involves a utomatically mapping existing data from the deprecated custom field to the new custom field.
After configuring the migration option, the admin must install the new version of the application. The upgrade process involves moving from the current Connect App to the Forge-based application. When the admin upgrades to the Forge application, the migration process starts automatically.
[screenshot]
The admin will receive real-time updates on the migration progress. Once the migration is complete, all custom fields will be successfully transferred. The new custom field will be added to relevant screens and schemes to ensure visibility and functionality.
Step 3: Optional configuration options
If you were using asset filters before, this is the steps you may want to follow to have this same functionality in the new custom field:
For example, you have a custom field called "HR assets". To make sure you can continue to use this custom field, we create a filter called "HR assets filter".
While the screens and schemes are automatically transferred, you need to do the Contexts yourself.
After the migration is done, the custom fields where you use filters may not work. To make sure they work, you need to perform three steps. 1) Go to Asset Navigator, find the asset filter, and check its contents and make sure they are what you want to have in this filter. 2) Go to Filter's settings, go to Viewers, and make sure My Organization is selected. 3) Go to Jira Settings > Custom fields, and find the specific custom field you want to edit the filter for. Click on the custom field, then select Contexts > Create, edit or delete contexts. Here, go to Custom field config, and click Edit custom field config.
Here you will see three options. For Asset filter, select the filter we've automatically created for you. We create the filter, but updating the filter's context is up to the user. This is optional. When you select the asset filter, the custom field will only show the assets in that filter.
Then you can select Field type, which can be Single or Multiple choice.
You can also make this screen read-only by checking the box.
If you don’t do this, the migration won’t be affected in any way. But you won’t be able to see the results you want in the custom field.
Keep in mind that, when you're creating a new filter and you want this filter to apply to the new custom field, you must select My Organization for Viewers. Otherwise, the filter won't work even if you select it on Contexts.
Adding custom fields to JSM portal
To add the custom field to the Jira Service Management portal, navigate to your service proejct's settings by clicking Project Settings on the side menu. You can add custom fields to different request types.
Under Settings, find Apps, and click Assets settings (AIP).
Here you see all the request types in your service project. Click the Edit fields button next to the request type you want to add the field to, and select the custom field you want. Click Save.
The custom field now appear on the customer portal form under that request type.
Here you can also chose to have asset informations displayed by checking the box “Display asset details in portal view”.
Limitations
On the Jira Service Management customer portal form screen, the new custom field cannot be set as mandatory due to Atlassian platform limitations.
The field position cannot be rearranged in the Jira Service Management portal request type form screen.
Known issues
String vs. ID Values
Due to Atlassian’s limitations, the custom field may display ID values instead of labels (e.g., showing "1" instead of "Employee"). This issue affects:
JQL queries. The query will work just fine, and the custom field on issue view will show the asset label as normal. However, the display on Issues query may confuse you.
Issue details in the History panel. The changes related to the custom field will have the same issue under History. 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.
