Integrating Insight and Jira is different in Insight for Server than it is in Insight for Cloud. In Insight for Cloud, the custom fields that contain Insight information are mapped onto Insight using the Asset type configuration screen.
To successfully integrate Insight with Jira, you will need to sign in with Jira administrator and Insight Administrator permissions.
Adding an asset type configuration
First, add an asset type configuration for the custom field you are linking, and add an IQL query to restrict the scope of the results.
When you create the new asset type configuration, you can select if you want to have it manually or automatically synchronized.
If you don't automatically synchronize your assets, you can manually synchronize them after any changes by clicking Asset Type Configuration > (your asset type configuration) >.
Adding a custom asset field in Jira
Then, create a custom field in Jira of type "Asset".
Creating a type configuration filter
To ensure that a custom asset field only displays the appropriate objects from Insight, you must add a type configuration filter to the field.
Specify Assets on issues
Jira agent view (Jira native)
When you create or edit an issue in the agent view (Jira native), you should be able to specify any assets from the synchronized listing of Insight objects. Assets are not filtered by assigned assets. Users entering characters in an asset field needs to type at least two (2) characters for results to become visible.
Customer Portal in JSD
The Asset Field on the customer portal in JSD are filtered by the assigned assets (if specified) so only the assets connected to the logged in user or the unassigned assets are possible to select.
Next Gen Projects
Currently the Asset Field is only supported on the agent view (Jira native) and not on the customer portal. This means that the assigned asset option will not work on Next Gen Projects. Atlassian are working on this.