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.
Fields with limitations
Assets (previously called Insights) fields
Assets fields in JSM requests and forms are supported, once you manually connect your site to Atlassian’s Assets API.
Because you connect one user’s API token, that user’s Assets permissions apply to the entire site. So the site doesn’t take into account individual visiting user’s Assets permissions. We recommend creating a service user specifically for the purpose of creating a token, giving that user a product admin role and the specific Assets permissions you want all users on your site to have.Fields always show as multi-select, even when you set them up to be single-select. To help users, make sure to mention in the field description whether users should choose one or multiple assets.
These limitations occur to due Atlassian API limitations: please vote and comment on this active Atlassian ticket.
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 license can see the assignee: it’s not visible to JSM customers.