v 1.39 : 12 Jul 2018

This release includes significant improvements the task assign screen and a vastly improved calculation of future resource burn on a project. There are also plenty of minor tweaks and bug fixes. Read on to learn about all the new bits..

Please contact  support@projectworks.io if you have any questions or feedback. 

Main features of this release 

  • The Task assign screen has been reworked, with a new option to allocate a certain number of hours per week to a person
  • The resource burn calculation used to project the value of resourcing has been improved for greater accuracy
  • See notes on API Updates included

People

  • Profile: The posting panel now also includes the Job Title (Job Title and Position are both shown).
  • Upcoming: The upcoming screen can be filtered to include or exclude Leave (as there can often be a lot of leave making it harder to spot the other items).
  • Upcoming: Events have been tidied up and are showing correctly:
    • Employment Starts: Date of the first posting for a person.
    • Posting Change: Date when a new posting starts .
    • Work anniversary: Every 12 months from the start date of the first posting.
    • Employment Ends The end date of a posting, if no new posting exists.
  • Leave: Bug fixed - can now apply for leave from your phone (were unable to enter/change the hours of leave).
  • Bench: A bug has been fixed where the "available numbers" for a person were showing incorrectly if filtering by Manager.

Projects

  • Adding a Project: The Office for the project now defaults to the office the client is assigned to.
  • Modules: Active filter has been added.
  • Tasks: You can now assign a task to a person if their posting hasn't started.
  • Tasks: The Modules table at the top of the Tasks page has been fixed. When filtered to "active only" the totals were based on active tasks only. Now, regardless of the filter, the totals are always the total of all tasks (active or inactive).
  • Resourcing: You can now resource a person if their posting hasn't started.
  • Timesheets: A sub-total of hours/cost per module has been added and a new Module Overview section at the top of the screen shows the total hours and cost for all modules with work effort duding the month.

Task "assign" screen redesigned

The assign tab on the task add/edit screen has been reworked with a new option for allocating hours to people. Hours can now be allocated to people in two ways; simply as a total number of hours, or as a certain number of hours per week.

Pro Tip: If you want to continue allocating hours like you always have, select the "Total" option and nothing will be any different for you.

To facilitate the new "weekly" mode, the task must have a start and and end date. This is needed to calculate the duration of the task so the hours can be distributed accordingly. 

Allocation Modes

Total Mode

Allocating a "total" number of hours for a person is the most basic way to assign hours. The number of hours will be allocated to that person and will not change if the task duration changes.

"Total" is the only option if a task has no end date (is open-ended).

 

Weekly Mode

The new "weekly" option allows for hours to be allocated at a set amount per week for the duration of the task. In this mode, the allocated hours will be updated if the task duration is changed; more hours will be allocated if the duration is extended or the hours reduced if the duration is shortened.

Behind the scenes the weekly hours are calculated by. If a task is for less than a week, the weekly allocation is prorated based on the number of days in the week the task is "active".

"Weekly" allocation of hours can only be used if the task has an end date.

Redesigned "Assign users" tab

 

  1. Graph showing the amount of time that has been recorded in timesheets (green) against the number of hours that have been allocated (yellow). Its an easy way to see how much of the allocated hours have been consumed.
  2. The duration of the task is shown, the number of working days between the start and end date.
  3. Allocation mode: Indicates whether hours have been allocated as "total" or "weekly" Note that both modes can be used on the same task.
  4. The number of hours that have been allocated per person and the value of the allocation.
  5. Toggle the allocation mode by clicking the button and selecting the required.

Task duration - how it is calculated

If a task has an end date the duration of the task will be shown. The duration is based on the number of working days from the start to end date of the task (inclusive).This provides another way for tasks to be managed (and will link really well to the schedule should you choose to show the tasks on the schedule).

  • Duration will be calculated when an end date has been set on a task. 
  • The duration is the number of working days from the start to end dates (inclusive).
    • End date will be populated if a duration is entered.
    • Changing the end date will alter the duration (increase if date pushed out, or reduced if date brought forward). The start date will not be updated by changing the end date.
    • Changing the start date will alter the end date (push it out or bring it closer). The duration will not be updated by changing the start date.

Note: You can still leave a task open ended by not adding an end date.

Resourcing

  • Project & People Resourcing screens now show 10 weeks or resourcing instead of 12 weeks. This is in preparation for a new "task balancing feature" that is coming soon.
  • Project & Person resourcing screens no longer include people that haven't been resourced in the previous 2 weeks.

Resourcing burn calculation improved

  1. Rate Card: If the project is using a custom rate card, the applicable rate for each person will be used.
  2. Task Rate (Weighted): Calculated based on the rates of the tasks they are assigned to, weighted by the hours they are allocated on the tasks. Ensuring you have allocated hours accurately for tasks will greatly improve the resource burn calculation.
  3. Posting Rate: If there is no rate card in place, and a person has no tasks assigned, the rate on their posting will be used.
    1. if a posting rate is used the the rate will come from the current or first future posting (and be used for duration of the project).

Pro Tip: Allocating hours on tasks for each person accurately will provide the greatest accuracy projected of resource burn rate when "Task Rate" is used for the calculation.

 

Shadow resources: The rate used for a shadow resource will be the first rate greater than $0 that is located.
The rate that is used for each user is shown, with a hover showing if the rate is from; a Rate Card, Task Rate or Posted Rate.

  1. The value for each person for each week is calculated as Rate x Hours (A x B)
  2. The value for each week is the sim of each persons weekly burn rate.
  3. The value of resourcing for the month is the sum of the value for each week. (Note: If a week spans a month the value is pro-rated when calculating the monthly burn)

Client

  • Risks: Can now be filtered to include or exclude inactive risks, and the the CSV export is based on the filter.

General

  • Custom Fields are now included when exporting the People and Projects directories.
  • Modal windows: Modals are no longer closed when you click outside the modal

API Updates

The following updates have been made to the API, making it easier for integration with other systems.

  1. There is now an endpoint to get Billing Contacts with multiple filter parameters that can be passed in.
  2. Responses for GET requests that accept query parameters will now include the following response headers:
    1. X-Total-Count
    2. X-Page-Count
    3. X-Page-Size
    4. X-Page-Number
  3. API GET endpoints that have query parameters now accept page and pageSize parameters. These will default to 1 and 100 respectively.