...
On this page:
|
|---|
Overview of changes
The External Assets Platform custom field is gone, but we are offering the will no longer be available.
A new Asset Custom Field to replace it.There is a migration of existing data is provided as a replacement.
Existing data will be migrated to the new custom field.
You may need to perform some Some configuration updates, particularly related to filters to ensure seamless functionality.
...
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 the Configure the migration option.If you’d like to proceed with automated updates to existing issue data, check the .
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
What happens if If you leave it unchecked?Once the External Assets Platform goes offline on , you will lose all the asset data you the box unchecked, all asset data stored in the old custom field . If you leave this unchecked, you will be lost when the External Assets Platform is shut down on . You will need to migrate this information one by onethe data manually.
Step 2: Data migration
The migration involves a utomatically mapping process automatically maps existing data from the deprecated custom field to the new custom fieldone.
Process:After configuring the migration option, the admin must install the new
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.
[screenshot]
...
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 were using used asset filters before, this is the steps you may want to follow to have this same with the old custom field, follow these steps to replicate the 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.
...
Review and update filters:
Navigate to Asset Navigator, locate the automatically created filter, and verify its contents.
Adjust settings as needed under Filter Settings > Viewers, and make sure My Organization is always selected
...
. Otherwise, you won’t be able to use this filter in the custom field.
Update custom field Contexts:
Go to Jira Settings > Custom
...
Fields.
Find the relevant custom field, then select Contexts > Create, Edit,
...
or
...
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.
...
Delete Contexts.
Edit the context settings and select the appropriate Asset filter.
Choose the Field type (Single or Multiple choice) and optionally make the field read-only.
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:
Navigate to Project Settings in your service project.
Under Apps, click Assets settings (AIP).
...
Locate the request
...
type where you want to add the field
...
and click Edit fields.
Select the custom field
...
and click Save.
...
The custom field now appear on the customer portal form under that request type.
...
Here Optionally, you can also chose to have asset informations displayed by checking the box “Display asset details in portal view”enable the Display Asset Details in Portal View checkbox to show asset information on the portal.
...
Limitations
On the Jira Service Management customer portal form screen, the The new custom field cannot be set as mandatory on JSM portal forms due to Atlassian platform limitations.
The field position position of the custom field on the portal form cannot be rearranged in the Jira Service Management portal request type form screen.
Known issues
String vs. ID Values
Due to Atlassian’s Atlassian limitations, the custom field may display ID values instead of labels (e.g.for example, 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 prioritizefunction correctly, but the Issues view may show IDs instead of labels.
History panel – Changes in the custom field will also display IDs instead of labels in the issue History tab. If this affects your workflow, contact our support team to discuss adding an Asset History Panel to improve usability.
