After adding a JSM project to a site structure, users can create and view requests directly on your Refined sites. We that site.
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
...
The beta version of this feature support most Forms fields. We’re developing support for additional fields:
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).
The ability to edit and submit a re-opened form from the request view.
There are currently some limitations to this feature:
...
While it is possible to submit forms with an attachment, it’s not possible to view attachments.
...
Assets fields in JSM requests and forms are supported, once you manually connect your site to Atlassian’s Assets API.
| Excerpt | ||
|---|---|---|
| ||
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 the Assets permissions of users on your site. 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 |
...
| Info |
|---|
All Forms created before January 1st 2023 are missing UUIDs. Atlassian is gradually assigning UUIDs to these Forms throughout the remainder of 2023. Forms without UUIDs will not show on your Refined sites. |
Assets (previously called Insights) fields
...
. The feature won’t work if you use the Atlassian premium feature IP allowlist. Please vote and comment on |
...
Assets REST API: add support for Oauth2 and JWT authentication
Affected Services fields
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. You’re welcome to 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. You’re welcome to Please vote /and comment on this active Atlassian ticket on Atlassian.
Assignee field
Only users with a Jira Software license can see the assignee: it is it’s not visible to JSM customers.
Cascading select field
The field is supported in request forms. In a regular request, it renders with only one selection box.