Release Notes: v1.0.88

Release Date: 21 June 2019 9PM UTC+10:00


  • New Configurable Risk Stages

  • This update is to increase the number of Risk Stages created at both, Project and Portfolio level.  Listed below are the new Risk Stages:
  • Planning WIP
  • Commenced
  • Progressing
  • Completed
  • Removed
  • The configuration for the Risk Stages will be available within the Company Profile below the Risk Category section.


  • The additional Risk Stages will be released with the default as ‘OFF’ / ‘unticked’. Users with access to the Company Profile can select which Risk Stages to enable to be available via a dropdown list to users when creating or updating risks
  • For Data Migration purposes all existing Risk Stages will be flagged as enabled so not there is no impact to current Risks.  Below is the list of current Risk Stages:
  •  Identified
  • Analysis Complete
  • Planning Complete
  • Actions in Implementation
  • Under Control
  • Retired

 

  • Project> Schedule 
  • This update applies to users where project schedules are based on Effort consumed rather than Duration consumed.  The purpose of this change is to incorporate the standard PM practice which holds the Actual Effortdata entered by a user to be the constant key. The Actual Effort value will remain unchanged and not impacted when changes are made to other effort values.
  • The following changes in the calculations will apply:
  • If a User elects to update the project schedule via Effort fields the following applies:
  • Changes to increase or decrease Task Effort (Forecast) data will lead to an update in the calculations for “Remaining Effort” and “Percentage Complete”.  Actual Effort will not be updated.


  • Previously, when Effort (forecast) is changed, Actual Effort is also changed based on the %Complete. According to the standard PM practice, which hold the Actual Effort as key and its value does not change when forecast effort is changed. In the current scheduler, when "Actual Effort" entered greater current “Effort” (Forecast) field will automatically increase the "Effort" and “Percentage Complete" to match.
  • Parent Task calculations
  • If the parent task has a minimum of one child task with “Effort”, the “Percentage Complete” Progress Bar will be calculated from the effort fields (Actual Effort/ Effort) * 100.
  • “Actual effort” and “Remaining effort” values are the sum of the data values of all direct child tasks.
  • If a User elects to update the project schedule via Percentage Complete fields the following applies:
  • Changes to increase or decrease the Percentage Complete data will lead to an update of  the "Actual Effort" and "Remaining Effort".  “Effort” (Forecast) will not be updated.
  • Project> Schedule> CSV Export/ Import
  • Export – All effort values calculated as per above are available.
  • Import - All effort values can be imported with the exception of “Remaining Effort”.
  • Note:  Parent Tasks effort fields are auto calculated based on the child tasks effort data. E.g If Parent tasks effort values are imported with incorrect values in CSV import, it will override any calculations from the CSV import file and correct calculated values based on child tasks effort will be updated.
  • Project> Schedule> Overall Project Progress
  • This change applies to the Schedules Overall Project Progress Bar calculated from effort calculations.
  • For Project schedules which have at least one task with an Actual Effort value, the Overall Progress Bar displays the current Percentage Complete of the overall schedule based on the total of Actual Effort percentage complete. i.e. (actual effort / effort * 100) rounded to the nearest integer
  • For Project schedules with no tasks with Actual Effort values, the Overall Progress Bar will continue to display the Actual Percentage Complete based of the percentage complete column values, i.e. (Sum Percentage complete * duration) / total duration) * 100
  • The Portfolio pipeline management schedule will continue to display the Percentage Complete based on the percentage completed as displayed in each of the individual Project Schedule Modules