Getting errors when trying to create an Assets object in forge app in Prod, but not QA!

I have a forge app that creates a record in an Assets table when a button is clicked. I deployed to our QA environment (which is a backup of production) and it works great. When I deploy to the production environment (with either the dev or prod version of the forge app) I get this error:

"message":"Failed to create Beyond Trust interaction record: {\"errorMessages\":[\"Sorry, you do not have permission to perform this action. PermissionInsightException: User 712020:04ce1dc4-476e-4f9d-97f4-8a805b77df87 didn't have correct permission (create object) for object type: 171\"],\"errors\":{}}",
"name":"FUNCTION_ERR",
"stack":"Error: Failed to create Beyond Trust interaction record: {\"errorMessages\":[\"Sorry, you do not have permission to perform this action. PermissionInsightException: User 712020:04ce1dc4-476e-4f9d-97f4-8a805b77df87 didn't have correct permission (create object) for object type: 171\"],\"errors\":{}}\n at createBeyondTrustInteractionRecord (index.js:87841:13)\n at async Object.onButtonClick [as onClick] (index.js:87988:31)\n at async index.js:60407:13\n at async asyncMap (index.js:60389:24)\n at async index.js:60410:29\n at async asyncMap (index.js:60389:24)\n at async index.js:60472:23\n at async asyncMap (index.js:60389:24)\n at async index.js:60410:29\n at async index.js:59816:17",

What gives the forge app permissions on the Asset objects? Customer does have special permissions for Assets, but can’t give this app user those permissions because they’re not a real Jira user. Everything works in their QA system, but getting this error in their production:

{"errorMessages":["Sorry, you do not have permission to perform this action. PermissionInsightException: User 712020:04ce1dc4-476e-4f9d-97f4-8a805b77df87 didn't have correct permission (create object) for object type: 171"],"errors":{}}

Hey @EricKruegerStrataCom,

Closing the loop here from the support ticket that was raised for this query. The permission issue was identified to be a restriction on the Assets roles, which was different between production and the QA environment. Modifying the roles which the Forge app had access to enabled creating objects in the schema/object type

2 Likes