Can a publicly visible Jira issue have internal comments hidden

[Deleted user]

We are currently planning to have some Jira issues that will be made publicly accessible/searchable, but internal development teams may comment on that issue, either to ask questions or to tell a customer that an issue has been fixed. Is it possible to hide individual comments from the publicly viewable issue, so that only specific comments are visible?

[Florian PEREZ · Accepted solution]

I think you get the article wrong!

By selecting a group or a project role into the field visibility of the comment only people in the group can view the comment.

So when you want to communicate internally you can add a specific group or project role and when you want the communication to be public you can just leave the comment visible for every one!

[Deleted user]

Ah ok, so for internal comments I need to add those internal people into a group, and only those people can see the comments.

Thank you for the explanation & help.

[Florian PEREZ]

Hello! 

There is two kind of comment into a jira issue.oucan select the kind of comment into a specific field after the comment:

https://confluence.atlassian.com/jirakb/add-restricted-comments-on-jira-962353957.html

Every private or restricted comment will be only visible for the people allowed by the restriction!

Hipe this help! 

[Deleted user]

Hello. Thanks for your reply.

The link you sent seems to suggest it is possible to hide comments from users who are in a group....however I won't know which users will be viewing the issue, so can't add them into a group.

The use case for this is a customer reports a defect. The dev team triage it and can post comments to that defect (jira issue) to ask our support team for more details on it, or  request repro steps etc. and we need to keep those comments internal.

Our support team want to publicize the link so anyone can search for it outside of our company to see if the defect has already been reported, but to keep all the internal comments hidden from it. 

During the dev cycle whilst that issue is being fixed & qa'd, we still don't want the customer to see any comments on it, however once that issue is fixed, we need to notify the customer that the issue is fixed, and in what version of the software the fix will be available in.

Hence the need to have a public issue with some hidden comments on it (but not all, as we have to be able to inform the customer which version of our software has the fix in it).