Why this propoerty doesn't work on workfliw "create" transition:
jira.permission.create.denied
I was hoping it would prevent users from creating issues for that particular workflow.
Theoretically this should be possible
Try to set the property as follows:
You could just grant the create permission in the permission schem to the correct role, group or users off course.
This option would only fit if this relates to a specific issue type creation in the project
Thanks @Marc - Devoteam
Strangely this one doesn't prevent issue creation from users who are not members of the group (I know i could use another method, but I am exploring)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Mikolaj Umiastowski did you try to set the group name instead of the id?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Kai Becker
just tried it, same result.
Perhaps I am missing something. Or perhaps it just cannot work?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I'm not sure, but in theory.
I'm not able to test it on my end now.
But the group value, should just be the group name, e.g. jira-software-users.
Bus as I said if this is general for the project, use the permission scheme to set this, grant only the role, group or user that needs to create issue the create issue permission
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.