Leaving Project Behavior + Unassigned Tasks Request
Only re-assign open tasks upon leaving a project. Left the sample project and had to re-assign all my tasks it seems. This isn't very good for historical tracking of tasks.
Perhaps NK needs "unassigned" tasks and all open tasks would be dropped there. Because picking just ONE user for all (or even all open) might be overload. The project could re-shuffle the deposited unassigned tasks on it's own schedule.
Unassigned would also be a great place to put things anyone was free to complete.
Perhaps NK needs "unassigned" tasks and all open tasks would be dropped there. Because picking just ONE user for all (or even all open) might be overload. The project could re-shuffle the deposited unassigned tasks on it's own schedule.
Unassigned would also be a great place to put things anyone was free to complete.
1
person likes this idea
I like this idea!
Tell me when this idea gets some attention.
The more people who like this idea, the more it gets noticed.
The more people who like this idea, the more it gets noticed.
Create a customer community for your own organization
Plans starting at $19/month
-
Inappropriate?It is actually quite a critical part of our design that a task is always owned by one person. We found that orphaned tasks can cause a lot of friction within teams.
You can see more about it on the Principles page on our Wiki.
I’m confident
The company thinks
this is one of the best points
Loading Profile...




EMPLOYEE