I'm trying to find out how Issue Security and Sprint Planning interact and whether it is "safe" to give the Sprint Planner permission to view "security-critical" issues.
The obvious issue is that, during planning, the Scrum Master will have their account open for all team members to view, thus exposing "security-critical" issues to the entire team...
Can this be avoided while still allowing the Scrum Master to lead Sprint Planning from their account?