Sidehistorik
...
Advarsel |
---|
Notice that "jira.permission.assignable.group" etc. is only working for a (re)assignment in the step. If the issue was assigned in a previous step (or during creation), this does not block a transition.... that must be done in a Validation |
Property | Values | Comments | Location |
---|---|---|---|
jira.permission.comment.user | true or false (Default=true) | Put on a Workflow Step to prevent comments. | Step |
jira.permission.comment.role | Id of a Role | Enable commenting only for a Role | Step |
jira.permission.comment.group | Name of a group | Enable commenting only for a Group | Step |
jira.issue.editable = true/false | true or false (Default=true) | Put on a Workflow Step to prevent editing (typically in Close/Resolved/Done). | Step |
jira.permission.editable.group | groupname like "jira-administrators" | Put on a Workflow Step to define a Group that can edit the Issue (and non-members cant). This will also block comments if edit permission is not available. | Step |
servicedesk.customer.transition.active | true or false (Implicit false) | Set to true if the transition should be available in the Service Desk (Web) Portal. | Transition |
jira.permission.work.denied | denied (Default = "") | Link | Step |
jira.permission.assignable.role | A number representing the role | Step | |
jira.permission.assignable.group | A group name | Step | |
jira.permission.work.denied | Step |
...