A better solution will be to use jira workflow properties.
Here is the link to guide you :
https://confluence.atlassian.com/adminjiraserver073/workflow-properties-861253674.html
https://www.j-tricks.com/tutorials/permissions-based-on-workflow-status
Regards
Prakhar
Thanks for the answer.
I tried to use this tricks but it seems not working (or I'm not configuring it well)
I have updated "Create issue" permission with Group-A and Group-B
In the main workflow Create transition, I set the property as follow:
Property Key: jira.permission.create.group
Preperty Value: Group-A
I've published workflow but user from Group-B is still able to create issue.
Am I wrong?
Thanks
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
reading some comments below the article i found out taht this properties don't work in Create transition.
I'm still investigating for a workaround
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Ok.
If you don't mind writing small groovy script then you can use this free add-on and write script for validator where you check the group of the user.
https://marketplace.atlassian.com/apps/292/jira-misc-workflow-extensions?hosting=server&tab=overview
You can use script runner also. If you have it on your instance.
JIRA Suite Utilities is another add-on which has built in validator for checking user's group. Although it is paid but you can at least evaluate if that works.
https://marketplace.atlassian.com/apps/5048/jsu-suite-utilities-for-jira?hosting=server&tab=overview
Regards
Prakhar
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.