Hi @annag ,
You can do this by adding a property on the workflow. On the Status that you wish to block the editing go to properties and add:
jira.issue.editable = false
You can block them with workflow properties.
See https://confluence.atlassian.com/adminjiraserver/workflow-properties-938847526.html
but in this case, find the status that is "closed" (one or many), edit the workflow and add jira.issue.editable
= false to those status (you might want to do the same for comments and other permissions)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
On that page, there's mention of how you can do the same for comments.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@annag ,
That would be through the jira.permission.* property.
Without duplicating all the information here there is an elaborate article about this on:
https://www.j-tricks.com/tutorials/permissions-based-on-workflow-status
The one you are looking for I believe would be:
jira.permission.comment.denied = denied
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
It's a bit older information (2011) but the information should mostly be accurate.
If they no longer work let me know and I'll do some testing myself :)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Will this work on next-gen projects within JSD?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Looking for a way to do this in a Behaviour...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.