Panel | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
This page is about Assets & Inventory Plugin for Jira DC. Using Cloud? Click here. |
In Jira, the Assignee field is used to specify who is responsible for an asset. With the update to AIP v7.0, the Assignee field has become a default system field. If you've been using a custom Jira User Picker to assign assets, this guide will show you how to transfer that information to the system's Assignee field"Assignee" and "Status" have become default system fields. This guide explains how to move data from custom fields you might have been using to these system fields. We'll cover two scenarios: updating the "Assignee" and "Status" fields.
Step-by-Step Guide
to Migrating Assignee DataImportant Note
If the assignee information in a text attribute does not correspond to a valid Jira username or user key, it will not be transferred and will be ignored during the update process.Step 1: Select the Assets to Update
There are two methods to select assets for updating:
Via Checkbox: Manually select the assets using checkboxes and choose the Update Selected option from the Bulk Operations menu.
Via Filter: Use filters to select assets and then select Update All from the Bulk Operations menu.
Step 2: Choose the Field for Update
After selecting Once you've selected the assets:
A, a pop-up window will appear. Choose the system field you want to update:
For Assignee: Select "Assignee (System)" from the list.
For Status: Select "Status (System)" from the list.
Click Continue to proceed to the field selection step.
Step 3: Specify the Data to Transfer
At this stage, specify the source from which the assignee data will be transferred:
Assignee:
Important Note
If the assignee information in a text attribute does not correspond to a valid Jira username or user key, it will not be transferred and will be ignored during the update process.
Choose Jira User Picker (Assignee) if the assignee data is currently held in a user picker field.
Optionally, select By Another Text Attribute if your assignee information is stored in a text attribute.
Ensure the correct data source is selected for a smooth transition.
Status:
For Status, this section won't be applicable. You'll define the mapping between your custom list box options and the system fields (Status and Substatus) in Step 4.
Step 4: Update the Assets
Assignee:
Once the Assignee data source is configured:
Click Update to apply the changes to the selected assets.
Monitor the progress in the Bulk Operations Status pop-up window.
Status:
Here's how to define mappings for Status updates (this is not applicable for Assignee):
Search for assets with the specific status you want to map (for example,
Deployed
).Click Update All from the Bulk Operations menu.
Select Status (System), and click Continue.
Choose the corresponding system field value based on your custom list box option (for example,
In Use
forDeployed
).(Optional) If your custom list box has sub-statuses, select the corresponding sub-status value (for example,
Available
forReady to Use
).Click Update and monitor the progress in the Bulk Operations Status window.
Repeat steps 1-6 for any other custom list box options you want to map.
Step 5: Verify the Update
After the process completes, verify that the data from the Jira User Picker has been successfully moved to the system fields (Assignee (System)
or Status (System)
).