At the beginning of my workflow, tasks/bugs need to be approved before being assigned to relevant users. This is to stop feature requests and such that have not been approved by PM from sneaking into the workflow.
I need to be able to limit the permission of who can assign an issue to someone in only the first step of my workflow - the rest of the team should be able to bounce the issue around to other team members thereafter, so I cant just revoke everyone's assigning privileges in the permission settings.
Ive limited the transition, but in my experience it hasnt stopped people from reassigning an issue without approval anyway and the assignee has worked on the issue without noticing it does not have an "approved" status. I wish to avoid this. Is there any way I can limit this assigning permission on this one step of the workflow process? Ideally, new tasks should automatically be assigned to a certain user or group, and they should be the only ones who can reassign to someone else.
Thanks!
Hello,
You should define a workflow property for the status on which you have the approval process.
The workflow property would be like this:
jira.permission.assing.group=some-group
You can find more info on workflow properties here:
https://www.j-tricks.com/tutorials/permissions-based-on-workflow-status
Exactly what I was looking for! Thank you so very much for your help :)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You are welcome! If you feel like I answered your question, kindly mark my question as accepted.
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.