Support mapping Asset object fields through Jira integration

Who would benefit?

Customers using the Asset object through Jira Service Management.

What impact would it make?

When these Asset fields are added to Jira issue screens, this would allow users to map these fields to Aha! fields through the Jira integration.

How should it work?

When configured on the Jira issue Create and Edit screens, users should be able to map Asset objects to Aha! fields similarly to other issue custom fields.