This is a great question,I am a PM , confuse the same question, and i also know the others have same requires. Possiblely anyone going to modify the source code to finish it , please do it , thank you .
Blocking users from modifying or removing tasks they aren’t assignee of wouldn’t be too difficult, but would require some moderate code.
But, not sure you would want to do that, I can see blocking remove, but you really are nerfing the system if you block modify, and the results might go further than you imagine, i.e. attaching files, comments, and more…and if you get picky about what specific things to not block, you get fairly complicated.
Might want to look into custom roles, not sure if that was ever fixed. If so, might do what you need, last time I played with them, they were borked.
The filter seemd not good work. it’s difficult to modify too more code for new role.
I’m trying to make the moderate task become not link , it’s only work for the task owner and PM.
I’m actually writing a plugin for permission control of tasks, based on their tags and asignee,
Creecros mentioned custom roles for this purpose if he can explain a bit more I’m ready to write the code in best possible way.
@creecros
I mentioned custom roles were borked, last time I checked. I dont do very well visualizing what people are doing, if I cant see code, I cant really offer much advice. You could be going down a path completely different than what I may uave.
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
save
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.
Yes, there were other things too that I had to fix when I started using it. I think the “Assign to me” button on the popover was appearing and the user could assign a task to himself even with the “Update only assigned” restriction.
I said:
They will still be able to add comments, add links, add things. It just removes the edit form
I did something for someone to block a user’s from removing tasks. Even something that simple requires lots of overrides, to properly hide options from users, so doing something in depth for permissions…I’m all set. Not a plugin I would want to maintain.
Every time I look at the roles and such, I give up. There should be an easier way.