Restrict issue editing when issue.status = Backklog and user = Developer

[SPACE coders]

Is it possible to restrict the issue modification depending on the status of the issue and who is modifying the issue?

[Dirk Ronsmans]

@SPACE coders ,

You should be able to do this with "workflow properties"

https://support.atlassian.com/jira-cloud-administration/docs/use-workflow-properties/

These properties can be set on a status and specifies who can change the issue. You can go very specific or allow/deny all.

[Rilwan Ahmed]

Hi @SPACE coders ,

If developer a group, then use  property jira.permission.edit.denied.group = developers Or  if it is a project roe, then use jira.permission.edit.denied.projectrole = (ID of developers role)

[SPACE coders]

@Rilwan Ahmed 

I have added these properties. But it doesn't work correctly. Because now I am not in the role of a developer, but I cannot update the task in the Ready status

[Rilwan Ahmed]

Hi @SPACE coders ,

jira.permission.edit.denied.group is same as jira.permission.edit.denied. It will block all users/groups/roles irrespective of them mentioned :(

The other solution is to add only roles who needs the edit. 
i.e. jira.permission.edit.projectrole.1, Value = role ID first role who needs the access. 
jira.permission.edit.projectrole.2, value = role ID of second role who needs the access and so on.