Logging time on creative projects

Overview

The time log feature allows you to track the time spent on a creative project.  

The creative project list in the production module has a "time spent" column that displays the total time spent by your creative team on a creative project.  Note that you may need to customize the production module list to display the time spent column.

mphq_timelog_1.png

 

You can display the detailed time log by putting your mouse over the "more information" icon.

mphq_timelog_2.png

 

 All users with the "Manage production" permission can log time by clicking the "Log time" button and filling the form.

mphq_timelog_3.png

 

 Also, a user may edit/delete its own time logs.  But may not edit/delete the time logs of other users.

 

Automatic triggers

The system has 2 automatic triggers to log time to help users not to forget to log time spent on a creative project.

  1. On correction done.
  2. On status change.

Both triggers can be used simulatenously.

 

On correction done automatic trigger

This automatic trigger will propose the user to log time (no. 2) when flagging a correction as done from creative project list in the production module (no. 1).

mphq_timelog_5.jpg

 

Follow these steps to configure the trigger:

  1. Go to the "Administration > My account" module.
  2. Click the "Edit" button
  3. Check the "Show log time on correction done" checkbox as shown in the following screenshot.

mphq_timelog_4.jpg 

On status change time log automatic trigger.

 This automatic trigger will propose the user to log time (no. 3) when changing a from given status (no 1.) to another status (no. 2) from creative project list in the production module.

mphq_timelog_6.jpg

 

Follow these steps to configure the trigger:

  1. Go to the "Administration > Creative project statuses" module.
  2. Click the "Edit" button
  3. Check the "Show log time on change" checkbox as shown in the following screenshot.

mphq_timelog_7.jpg

 

 

 

Have more questions? Submit a request

0 Comments

Article is closed for comments.
Powered by Zendesk