Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

« Previous Version 10 Next »

image-20240328-125543.png

JSM Assets fields BETA

Connecting to the sssets API isn’t recommended by Atlassian. Providing your account credentials is done at your own risk.

To display sssets fields in JSM requests and forms, connect your site to Atlassian’s Assets API.

First, create this setup in native JSM:

  1. In native JSM, create a service user with a product admin role. Give this user the specific assets permissions you want all users on your site to have.

  2. In the top navigation bar, select Assets > Object schemas.

  3. Open your object schema.

  4. In the top-right, select Object schema > Configure.

  5. Switch to the Roles tab.

  6. Add Refined Sites to the Object Schema:

Then create this setup in the Refined Administration:

  1. Go to the site’s Configuration tab.

  2. Scroll down to JSM assets fields.

  3. Click the Connect to API button.

  4. Let an Atlassian user in your JSM instance create an API token. The users who visit your site will be able to see all Asset fields that this Atlassian user can see. Learn more about Atlassian tokens

  5. Fill in the user’s email address and the user’s token.

  6. Click the Connect button.

Limitations

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.

The feature won’t work if you use the Atlassian premium feature IP allowlist. Please vote and comment on this active Atlassian ticket.

  • No labels