...
On this page:
|
|---|
Overview of changes
The External Assets Platform custom field will no longer be available.
A new Asset Custom Field is provided as a replacement.
Existing data will be migrated to the new custom field.
Some configuration updates, particularly related to asset filters, may be required.
Admins need to decide on the best migration approach for their organization and complete the necessary actions.
Migration steps
| Tip |
|---|
If you encounter any issues or have questions during the migration process, our support team is here to help. Contact us to get assistance and ensure a smooth transition. |
Step 1: Notification and initial configuration
Admins will see a banner in the application notifying them of the upcoming changes.
...
The banner includes information about the new custom field, and a call-to-action to Configure the migration option.
Actions required
Admins must:
Click Configure the migration.
Choose your preferred migration approach:
Automated updates – Check the box labeled Yes, update them to automatically update existing issue data. Note that this may trigger automation rules or impact reports.
Manual configuration – Leave the box unchecked if you prefer to manage configurations manually.
Important
If you leave the box unchecked, all asset data stored in the old custom field will be lost when the External Assets Platform is shut down on . You will need to migrate the data manually.
Step 2: Data migration
The migration process automatically maps existing data from the deprecated custom field to the new one.
...
Upgrade the application – Install the new Forge-based version of the app.
Migration begins automatically – When the admin upgrades to the Forge app, the migration starts automatically.
Monitor progress – Real-time updates will be displayed during the migration.
Completion – Once the migration is complete, the new custom field will be added to relevant screens and schemes for continued functionality.
Step 3: Optional configuration for filters
If you used asset filters with the old custom field, follow these steps to replicate the functionality in the new field:
...
If you skip this step, the migration will still succeed, but filters may not function as expected in the new custom field.
Adding the new custom field to Jira Service Management (JSM) Portal
To display the custom field on the JSM portal:
...
Optionally, you can enable the Display Asset Details in Portal View checkbox to show asset information on the portal.
...
Limitations
The new custom field cannot be set as mandatory on JSM portal forms due to Atlassian platform limitations.
The position of the custom field on the portal form cannot be rearranged.
Known issues
String vs. ID values
Due to Atlassian limitations, the custom field may display ID values instead of labels (for example, showing 1 instead of Employee). This issue affects:
...