After adding a JSM project, users can create and view requests directly on your Refined sites. The sites Sites support most JSM request fields, with limitations for the ones listed below.
We continually add support for newly introduced fields. Sites don’t support fields from third-party apps.
...
We’re unable to support the Asset Object Custom Field, due to an Atlassian limitation. Please vote and comment on this active Atlassian ticket: Add API to be able to retrieve Insight field values.
Forms APIs are blocking Connect apps for customers who use IP allowlisting. This has been reported as a bug to Atlassian, and they're working on resolving it.
Assets (previously called Insights) fields
Due to Atlassian APIs, we are We’re currently unable to support Assets fields, due to Atlassian APIs. Please vote and comment on these active Atlassian tickets:
...
Due to Atlassian APIs, we currently do not render don’t show this field on Refined because the field does not because it doesn’t return any values (ie. the field is not functional). As a result, we do not display the field. We are We're in direct contact with Atlassian regarding this. Please vote and comment on this active Atlassian ticket.
If this is a mandatory field, we suggest that it’s set to making it optional. Otherwise, requests cannot can't be created via your Refined site.
Hidden Summary fields and preset values
If a request type has a Hidden Summary field and a preset value, we are not able to can’t display that value on Refined in the request view on a Refined site. This happens because the Atlassian API doesn’t return that value to us. Please vote and comment on this active Atlassian ticket.
...
Only users with a Jira Software license can see the assignee: it is it’s not visible to JSM customers.