Hello,
Our resources tend to move from one project to another, and so we use the dates in Project Allocation accordingly.
However even after the end date of a user's allocation has been reached, they can still log work on their "old" project.
Scenario:
- User works on project A from January 1st to March 31st
- User works on project B starting from April 1st
=> we allocate User to A with an end date = 31/03
=> we allocate User to B with start date = 01/04
- When User opens Timesheet for April, they still have an open Assignment on activities from project A, and can continue to log work on it.
Yes, often users enter work long time after their working time.
So we cannot block this instantly.
Just close the assignments, it will block input.
Yes of course we need to allow entering the work at a later date, otherwise it will be too many problems !
However perhaps there could be a validation added when saving , to make sure that the user is allocated to the project when trying to add work on this project ?
I do notice that the v10.3 allows "multiple edit" with the Assignments view, so that can be a great help and should be enough.
Thanks for that new feature 😀
To clarify on the proposed evolution : idea would be to add a validation control when saving real work, for the following scenario.
- I was allocated to project A from 01/01 to 31/03
- I am allocated to project B from 01/04
- I log in on April 20th , and open Timesheet to log work
- I can log work for 31/03 on project A
- I cannot log work for 31/03 on project B (because my allocation is not open before 01/04)
- I cannot log work on 01/04 on project A (because my allocation is closed for 01/04)
- I can log work for 01/04 on project B
Should help for consistency, it's a nice to have.
Cheers
Your request is too restrictive and will lead to blocking situation is some (frequent ?) cases.
Is is possible to delete allocation with assignments still active... (we tried to enforce this control on older version and has to disable it)
It is possible to assign a Team of a Pool, without ensuring the resources are also assigned.
A resource can be able to enter work on tasks "he is responsible for", without specific allocation needed.
OK, thanks for analyzing end providing the explanation.
Keep up the good work 🙂