Problem
We use Jira Service Management for handling support issues, bugs, and overall requests within our organization, often sourced from other reporting software. However, because of how Jira regards these users as "customers", they are not able to see existing in-progress tickets for a related issue, nor can they access issues their teammates have submitted unless they have been added as a participant.
This harms the visibility principle for work management and requires a lot of extra communication on the side of the agents and product managers.
Solution
As a work-around, I've set up an automation to automatically include certain users as "Request Participants" to tickets. However, this does not feel scalable. So, we're looking for a way to better leverage support ticketing that focuses on visibility of what has already been reported, similar to how Atlassian itself handles community issues.
Thanks for your ideas!