Is there a way to not become a collaborator when just moving a task to another project?

We have a workflow where tasks where the project they should be assigned to is not known by the creator are all dumped in one project. Then a person with deeper knowledge of the topics moves the task to the correct project.

The act of moving the task seems to make the person a collaborator which then in most cases makes him receive notifications about updates on the task (depending on the notification settings of course) - this is very irritating as it drowns notifications about tasks this person is actually involved in,

Is there a way to not automatically become a collaborator when “only” moving a task?

Best regards,
Ron

2 Likes

Hi @Ronald_Findling, thanks for reaching out!

I tested this on my end and I’m not added as collaborator when I add a task to another project. Are you manually multi-homing the task or are you using Rules? and when you mention you are moving a task to another project, do you mean you click the three dots in the top right corner and select “Add to another project?”

Please note that if you are the task creator, you will always be added as collaborator.

Looking forward to your reply!

2 Likes

Hi Emily,

moving a Task for me means removing from one project and assigning to another one.
Adding a project doesn’t make me a collaborator - but removing a project makes me a collaborator of the tasks (just tested again).

Best Regards,
Ron

1 Like