After adding a JSM project, users can create and view requests directly on your Refined 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.
Forms (previously called ProForma) fields
Your sites support most Forms fields.
Limitations
We’re unable to support the Asset Object Custom Field, due to an Atlassian limitation. Please vote and comment on this active Atlassian ticket.
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
We’re currently unable to support Assets fields, due to Atlassian APIs. Please vote and comment on these active Atlassian tickets:
Affected Services fields
Due to Atlassian APIs, we currently don’t show this field because it doesn’t return any values (ie. the field is not functional). 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 making it optional. Otherwise, requests 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 can’t display that value 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.
Assignee field
Only users with a Jira Software license can see the assignee: it’s not visible to JSM customers.