After adding a JSM project, users can create and view requests directly on your Refined sites. The 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.
Forms (previously called ProForma) fields
Your sites support most Forms fields, and we’re developing support for the rendering of multiple forms in the request view (only one can be attached to a request in the create state, but additional forms can later be added by the agent).
Limitations
We’re unable to support the Asset Object Custom Field, due to 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 currently unable to support Assets fields. Please vote and comment on these active Atlassian tickets:
Affected Services fields
Due to Atlassian APIs, we currently do not render this field on Refined because the field does not return any values (ie. the field is not functional). As a result, we do not display the field. We are 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 optional. Otherwise, requests cannot be created via Refined.
Hidden Summary fields and preset values
If a request type has a Hidden Summary field and a preset value, we are not able to display that value on Refined in the request view. This happens because the Atlassian API doesn’t return that value to us. Please vote and comment on this active Atlassian ticket.
Assignee field
Only users with a Jira Software license can see the assignee: it is not visible to JSM customers.