You can effectively achieve that by taking the screenshot from an account with access to the project (Browse Projects permission) that doesn't belong to the group or project role to which the comment was so restricted.
But, if the comment is restricted to a group, wouldn't you want to hide the comment completely, not just the fact that it's restricted?! If they can view the issue from their own accounts, they will notice that they don't see these comments, so what's the point? And if it was worth restricting in the first place, then why would you let people without that access see it during a screenshare?
I would suggest that if you want to keep this information hidden, the person doing the screenshare should access JIRA using an account that has no special privileges and therefore will not see the comment at all.
Atlassian Summit is an excellent opportunity for in-person support, training, and networking.Learn more
Hello! I'm Rayen, a product manager at Atlassian. My team and I are working hard to improve the trial experience for Jira Software Cloud. We are interested in talking to 20 people planning t...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs