Jira issues linked to a Service via the Affected Services field should appear as a connected Jira issue in Assets

Issue Summary

When viewing a Service via the Insight Services schema any Jira issues that have been linked via the Affected services field do not appear under the Connected Jira issues section. Currently this is only populated if the Jira issue is linked via an Insight custom field.

Steps to Reproduce

1. Create a service (e.g. service-1) (via the JSM Services menu or within the Insight Services schema)
2. Create a new Jira issue and specify the service-1 within the Affected services field.
3. View service-1 within the Insight services schema.

Expected Results

The Jira issue is listed under Connected Jira issues.

Actual Results

The Jira issue is not listed. 

Workaround

While the linked Jira issues do not appear within the Insight view, they do appear when viewing a service via the JSM Services menu.

You could use an Automation Rule to set the custom Asset picker field with the same value of Affected Services, when that field is filled in, or on issue creation (for example). This will ensure that the Jira Issue is linked in Assets and a part of the Affected Services.