I would like to lilmit who can transition an issue's workflow.
Is it possible to allow only the current assignee to transition the workflow and anyone in a paricular group? So both criteria could change it.
I want all users to be able to view all issues.
I've looked into Issue Security but its not clear if you can limit the transition ability. Possibly a transition validator?
Thanks.
Actually, workflow properties are overkill and over-complex for this.
If you look at a transtion, you'll see you can add "conditions". These allow or deny people to perform transitions based on all sorts of rules.
The really easy one is "only allow current assignee". "Only allow if user is part of a group" is another. You can glue them together with AND and/or OR statements too. You can do roles, reporter, project lead, assorted permissions, field contents etc etc etc. And write your own!
In fact, you should ALWAYS place at least one condition on every transition, even if it's just "person must be a member of jira-users", otherwise anonymous users can do stuff.
Is there a way to have a 'blanket condition' for an entire project workflow? I don't want to have to add a condition to every single transition in my workflow, that is very prone to input-error.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
If you want to restrict the movment of an issue, you'll need to set a property on the step in the workflow. Go to the workflow step and click View step's properties. Then set a property, something like jira.permissions.move.user= user_name , jira.permissions.move.group = group_name , or jira.permission.assign.assignee to "granted".
This link http://www.j-tricks.com/1/post/2011/02/permissions-based-on-workflow-status.html is still a good source for more on this. You might also check https://confluence.atlassian.com/display/JIRA/Workflow+properties
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
"Only allow current assignee" is not an easy to use option.
It fails when you add the Assignee field to a transition screen: If the assignee sets a new assignee before confirming the transition, the transition with a permissions error.
https://jira.atlassian.com/browse/JRA-60940
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes, that's why you don't put it on the screen.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.