We use JSM for all of our internal ticketing. All projects have custom issue types with their own custom field(s), permission settings, issue security etc. We've also set it up so each project has permission set to the project via specific project role(s) to prevent the standard "Service Desk Team" assignment from giving browse access to all projects since some projects have complex Issue Security in place (HR / Legal)
We currently have an automation running that allows users to kick off a linked issue automation that will copy basic fields (Reporter, Summary, Description etc) and tag it with a specific linked issue type. It also adds whomever picks up the ticket as assignee to the "Request Participants" field on the original ticket so in theory they can see the basic details. But that dosnt work if they are an agent and not looking via the portal.
The question is whats the best practice for allowing visibility into the issues that need to be linked for agents in different projects while not opening these projects up more than necessary?
