Issue Summary

Currently, if a user does not have read permission for an Asset, our gadget is unable to display the Asset name, even though the user can see the Asset name in the Jira’s issue view or in the Jira’s issues table when the Asset is referenced in a custom field.

However, for users without permission to access the Asset, this API call returns a 403 Forbidden error.
We understand that users without full access cannot open the Asset details, but we’d like to at least display the Asset name, similar to what Jira already allows.

Steps to Reproduce

1. Making an API call towards /gateway/api/jsm/assets/workspace/{workspace}//v1/object/XX?includeAttributes=false

Expected Results

Display the Asset name, similar to what Jira already allows.

Actual Results

403 Forbidden error.

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available