Differences

This shows you the differences between two versions of the page.

--- disabling_state_properties [2017/05/09 10:10] – added new option pawel
+++ disabling_state_properties [2026/02/01 12:29] (current) – external edit 127.0.0.1
@@ Line 3: / Line 3: @@
 You can disable certain properties at certain states, for example if you want to disable all users from being able to comment on an issue in a "done" state, you would go to the workflow step in the edit mode, select the "done" state and click Properties.
 ^ Functionality ^ Property Key ^ Property Value ^
-| Disable all users from commenting | jira.permission.comment.denied | jira.permission.comment=denied |
+| Disable all users from commenting | jira.permission.comment.projectrole | {PROJECT_ROLE_ID} |
-| Disable all users but assignee from commenting | jira.permission.comment.assignee | jira.permission.comment.denied= |
+| Allow Jira Group to edit at state | jira.permission.edit.group | {JIRA_GROUP_NAME} |
+| Allow projectrole to edit at state | jira.permission.edit.projectrole | {PROJECT_ROLE_ID} |
+| Disable projectrole to Work on Issues at state | jira.permission.work.projectrole | {PROJECT_ROLE_ID} |
+| Allow projectrole to Assign Issues at state | jira.permission.assign.projectrole | {PROJECT_ROLE_ID} |
+=== Example ===
+{{:only_allow_projectrole_10001.png?600|}}
+==== Links ====
+[[http://www.j-tricks.com/tutorials/permissions-based-on-workflow-status|Permission Based Workflow]]\\
+[[https://modem7.wordpress.com/2013/01/15/editing-closed-issues-without-reopening-in-jira/|Editing Closed Issues]]\\