How to disable editing for closed Jira issues (cloud)

[Dreymann, Thomas]

Hi all,

after a ticket has been closed, i would like to prevent users from writing new comments and editing their own comments.

I read tons of article and saw many solution for server like changing parameter in our workflow i.e.: jira.permission.comment, jira.permission.comment.user, jira.permission.edit.denied. But I could only get it working that you can no longer edit an issue, the comment always remains editable. 

Hopefully there is one with a new idea of solution?

Best Regard
Thomas

[Sanjen Bariki]

Hi @Dreymann, Thomas ,

Welcome to Atlassian community!

Could you please go thorugh the below document to for the resolution..?

• Disabling edits in closed issues 
• How to disable comments creation/editing for closed Jira issues 

Kindly check and let me know If you have any quries.

Please accept the answer If it helps you.

Regards,

Sanjen Bariki

[Dreymann, Thomas]

thanks for helping me - these documentation I also found and I made ff. changes to our configuration:

the result is, as I mentioned above, that nobody could edit this issue and make a new comment after closing this ticket. But, if I have make a comment before, I can edit this comment after closing the issue.

Maybe the server solution is different to cloud? 
Regards,
Thomas

[Joseph Chung Yin]

@Dreymann, Thomas -

Based on my understanding and experience, editing existing comments when the issue is closed can't be controlled.

Here are additional WF properties for your reference - https://support.atlassian.com/jira-cloud-administration/docs/use-workflow-properties/

Sorry.

Best, Joseph Chung Yin

Jira/JSM Functional Lead, Global Technology Applications Team

Viasat Inc.

[Marc - Devoteam]

Hi @Dreymann, Thomas 

I use the properties as well.

I usually set the following properties depending on the use cas.

If I want to make sue an issue can't be edited on the final workflow status I use:

Key jira.issue.editable with value false

If I want to make an exception, lets say for group jira admins, I use:

Key jira.permission.edit.user with value jira-administrators

[Dreymann, Thomas]

thanks all for helping - this was the solution for me.