Can we add comments to issues which are not readable by the project owner?

[Klaas Klaas]

Situation:

Customer is project owner in JIRA 

Issues are entered in JIRA by Customer.

We (software agency) are accessing the issues.

We (software agency) wants to add our own comments. These comments must not be seen by the project owner.

Why? We as a software agency, wants to discuss the  pro's and con's of certain solutions to issues without the peeking of the project owner.

Is there a way/workaround to achieve this kind of modus operandi?

[Robert Massaioli (Atlassian)]

Who owns the JIRA instance? If the project owner is a JIRA admin then there is nothing to stop them from adding themselves to whatever permissions that you try and restrict them from seeing.

[Jeremy Gaudet]

You can restrict a comment to a particular role (say, "Developers") when you add the comment, you then just have to make sure the "Project Owner" isn't in the Developers role.  To set the security level of a comment, click on the open padlock icon under the comment field during add or edit.  That works for me, at least, and I'm not aware of any specific installation requirements to use that feature.

[Pedro Cora]

You can add comments restricted to a specific group. Check the documentation on https://confluence.atlassian.com/display/JIRA/Commenting+on+an+Issue

Basically, you need to make sure the Project Owner is not inside the group. Then when you add the comment, set the comment visibility to just your group.

-- Pedro