In some cases, when copying last week's time entries, some of the prior week's time entries may not be copied. If any of the time entries from the prior week fail validation, in the sense that they violate project or workspace time entry constraints, those time entries will not be created for the current week. It could be that the Project Admin on the project has applied a new set of time entry rules to the project or to a specific task, or that the workspace administrator has update time and expense settings since time entries were submitted in the prior week.
Some examples of this include:
- Project has been set to require notes for time entries, but one or more of last week's time entries for that project do no have notes.
- Project has been set to require that time entries are associated with tasks, but one or more of last week's time entries are not associated with tasks.
- The workspace requires that time entries be entered within the project start and end dates, and copying last week's time entries for that project would create time entries beyond the project end date.
- Time entry(s) would exceed the project hours budget or would cause the project's services revenue budget to be exceeded.
- Time entry(s) would exceed the task's hours budget or would cause the task's services budget to be exceeded.
In these, and any other cases where time entry validation fails, the project row may be added to the current week, but some or all time entries for a project / role / task may not be copied.