never mind - figured out our error Workspaces application - users cannot see tickets prior to workspace setup

Hello

I have a Workspace where the group has access to ticket app, but the members do not.  We do not want direct ticket access for the users of the group. During sandbox testing, the tickets that existed under the current service were accessible through the workspace even though they were assigned to other groups (filters set to see certain responsible groups).  All setting in sandbox were migrated to prod.  We did not re associate tickets in sandbox so this is a change in prod.

During the migration to prod.,  a new service was created to replace the exist one.  The tickets in the existing group were re associated with the new service.  Now the users in the workspace get  protected view.   For any of the re associated tickets. 

Is it possible that re associating the tickets from old to new service somehow changed the view access for the workspaces people?

If not, what else can we check and if so, is there a way to fix this?

UPDATE  - even new tickets associated with the new Service  are giving a permission denied error even though I can see the ticket name in the workspace

Thanks

Kay

 

 

Asked by Kay Kazinski on Mon 3/4/24 12:34 PM Last edited Mon 3/4/24 1:42 PM
Sign In to leave feedback or contribute an answer

Answer (1)

This answer has been marked as the accepted answer
Mark Sayers Mon 3/4/24 1:56 PM

Hello Kay,

Did you make sure in your Production ticketing application to set your app's "External User Settings" the same as you had them set for that ticket application in Sandbox?

Sincerely,
Mark Sayers
Sr Support Consultant, CS

No feedback