Assign ressource

You assign workload to an activity, but not T0 : T0 is calculated by planning.
If an activity has a fix T0, then use a fix milestone as predecessor.

Fixing when a resource will start to work on an activity would go against planning calculation.

What is interesting is when the resource is affected to the project.

Some resources have external constraints, they can not begin until a fixed date.
Planning must take account of the start date of availability.

I agree. And that's why affectation (to project) start date is a planned evolution.
But there should not be an assignment (to activity) start date for each assignment : it would be a mess to manage, a real slowing in planning calculation, and could lead to very strange planning calculation. Let's keep it simple.

This ticket is very important.

Maybe in your case, but I never met such cases : in my opinion, no more than 2 or 3 resources should be assigned to the same activity. Otherwise, it's a mess to get planning that really means something.

It's very long to assign multiple activities many people.
There will not be a simple technique to select multiple people on one activity?

Not from the existing desing of application.
Moreover, when assigning a resource, you must select its function (may not be defined by defaut) and assigned work (may be different for each resource assigned).


Maybe you could describe your real need, because I don't get why you need to frequently assign many resources to many activities.

Thanks