We are experiencing this issue as well and are also looking for a better solution. Here are some of our findings:
- The category field on the Time Cards form defaults to project_work so any new Time Card created directly (like creating from a list or from the Time Card related list of any task will be of category = project_work regardless of what task it is for
- If the Time Card is automatically created from the Time Worked field in the task for Project Tasks it will be project_work and for any other task type (Incident, Problem, Change etc.) the category it will be task_work so some logic must be executed (perhaps a script include?). This functionality is not enabled by default but we have checked “Auto fill time card with time worked entries” in our default time sheet policy. This functionality seems to be replicated in the Time Sheet Portal as mentioned in the earlier post.
Summary: OOTB Time Cards on Projects and Project Tasks is always category = project_work regardless of how the Time Card is generated but the Time Cards on other tasks types can be categorized mistakenly as project_work in two ways: Creating the Time Card manually from a list/related list or the user manually changing in the Time Card record from task_work to project work.
Since there are other task types that by design could have a Time Card created against them AND may be part of projects (stories in a hybrid or agile project) we are looking to adjust the default value on the category field of Time Card records to accommodate if the task is of type project or project task (or task’s parent is of task type project or project task_ set the Time Card category to project_work else set the time card category to task_work.
