Custom roles are difficult if you want some complex rules. I have a project with several rules to a custom role, and works well. It’s just complex.
- Go to project settings > Custom roles
- Add a new custom role and name it
- Your custom role will appear right below. Click on its name (“Restrictions for the role …”) > Add new project restriction
- On Restriction, select update only assigned tasks is permitted
This restriction still allows users to move tasks that aren’t assigned to them. But they can’t open the edit form. They will still be able to add comments, add links, add things. It just removes the edit form. If you want the users to not move tasks that aren’t assigned to them, you must add a new restricion, and here is the tricky part:
- Click on your restriction > Add new drag and drop restriction
- Add a restriction to each pair of columns. You dont have to create the “back” path. For instance, if you add Source: Backlog, Destination: Ready, the user will be able to move also from Ready to backlog. Don’t forget to check the “Only for tasks assigned to the current user” if you want them to only move their tasks. If you have 4 colums, you will create 6 rules if you want them to move the tasks everywhere:
After you create your custom rule, go to Permissions and assign the role to the users or groups you want
I use this in conjunction to automatic actions. The image above is an example, it did not reflect the behaviour I will write here:
Users can move any task from Ready to Work in Progress. Everytime a task enters the Ready column, it’s unassigned. Everytime it enters Work in progress, it’s assigned to the user that moved the task.
Once in Work in Progress, the user can move the task to Done or Pending, but only those assigned to them.
This way the people can grab their own tasks (the kanban thing, pull, don’t push), but once the task is theirs, no one can grab the task or edit it.