In our workflow I have added a property key of jira.issue.editable to the last several statuses in our workflow, and set it to false. This locks the card once it reaches a certain point so it cannot be edited.
I also need to do this for comments. Folks should be able to add comments whenever, but only edit them when they are in statuses in the first half of the workflow. I thought there would be a similar permission for editing documents, but I can't find it.
Interestingly, on the API page (https://docs.atlassian.com/software/jira/docs/api/7.13.1/com/atlassian/jira/security/Permissions.html) it looks like there used to be a permission called "edit_own_comments" but it sounds like its deprecated, which I find odd. I also am not sure what the full permission designation would be. I tried jira.edit_own_comments but this didn't work.
Refer to https://confluence.atlassian.com/jirakb/how-to-deactivate-comments-for-closed-issues-648217599.html on the disabling comments for a status.
jira.permission.comment.user=false
Thanks Fazila!
This is close to what I need, but not quite. There are three stages:
1. In the early statuses, comments should be editable
2. Once it reaches a certain place in the workflow, they should still be able to add comments, just not edit them.
3. Once the issue is done, comments can be completely disabled.
So from what I understand, jira.permission.comment.user=FALSE will satisfy #3, but I haven't figured out a way to satisfy #2.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.