Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

How can i change the comment visibility from All Users to one project role retroactively?

Issam AMARIN
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
September 14, 2018

We started an working on JIRA in March and only the IT team can view the issue details and comments. Now we would like to give all our users the access to see all the issues but hiding the comments.

I can change the default comment "Viewable by All Users" to one of the default project roles but this cannot be done retroactively, do you have a way to do it retroactively?

thanks,

2 answers

0 votes
Alexey Matveev
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
September 14, 2018

Hello,

Do you mean that you can not change comment visibility after you added a comment? You can. Just push the Edit button.

Issam AMARIN
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
September 16, 2018

Hi @Alexey Matveev,

I can change it but I want to change all the historic comments in bulk. because i want to give a public access to the JIRA issues without showing the developers' comments.

Thanks,

Like Philipp Messerli likes this
Alexey Matveev
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
September 16, 2018

You can use Jira Rest Api for it:

PUT /rest/api/2/issue/{issueIdOrKey}/comment/{id}

https://docs.atlassian.com/software/jira/docs/api/REST/7.12.0/#api/2/issue-updateComment

0 votes
Mohamed Benziane
Community Champion
September 14, 2018

Hi @Issam AMARIN

I'm afraid that's not possible in jira at least is not a native feature. When you set a permission is for the whole issue within the project.

For the future what you can do is to create a subtask and work on it with a different scheme security than the parent, you have to tweak jira but i did it once and it work well.

 

Regards

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events