Issue Summary

This issue has been there for some time (insight 6.n).

Logged here as a bug, since other Insight Postfunctions will work for a JSM Customer - for example, Update an Object's Attribute with a predefined value.

Steps to Reproduce

1. Make sure you have a User with no Application Access to Jira, who can access the JSM Portal and create a Ticket
2. Install and configure an Insight Tempo Integration, sync the import
3. Make sure the Schema is enabled for Portal users (Roles Tab)
4. Create an Insight CF to be populated by the Tempo Account Objects - make it available in the Portal
5. Configure an Insight Tempo Postfunction to use the "Account Id" attribute from the Insight Account CF to set the Tempo Account CF. Make sure the PF is not the first one.
6. Log in as the Customer, and create a Ticket. Select an Insight Account Object in the Insight Account CF and create the Ticket

Expected Results

The Postfunction will set the Tempo Account CF as per the object selected in the Insight Account CF

Actual Results

The Insight Account Object is there, but the Tempo Account is not showing.
The Log shows:

2021-04-14 15:56:31,524-0400 http-nio-8080-exec-19 WARN 1007 956x1460x1 1123l2a 0:0:0:0:0:0:0:1 /rest/servicedesk/1/customer/requests/transition [c.r.j.p.insight_tempo_accounts.workflow.WorkflowFunction] Post function could not execute: PermissionInsightException: User JIRAUSER10702 didn't have correct permission (view) for object: 611,830

Workaround

Possibly use the Groovy Script postfunction to set the account on the Ticket.

Set the account on an Agent's transition.

Note:

Even if this is by design - the error suggests that the user (customer) does not have permission to view the Object. However - in the same transition, you may configure an Insight PF to Update an Object's Attribute with a predefined value or even to Create an object...even though the Customer does not have the permissions!