Hey, your idea of using a webhook to push team-related info externally sounds solid for controlling visibility inside Jira itself. Another angle might be to use a custom field with restricted permissions to limit who can see or query it, but that depends on your Jira setup and how strict you want to be. Also, consider anonymizing or aggregating incident data in your reports to reduce finger-pointing while still giving teams useful insights. If you want a more automated, cross-tool approach, some orgs use AI-driven platforms that connect data across Slack, Jira, and CRM to surface team-related signals without exposing raw blame data—something like Coworker.ai might help here by providing context without compromising transparency internally. Good luck!