Staffing: Allocation by Investment (summed total incorrect)
search cancel

Staffing: Allocation by Investment (summed total incorrect)

book

Article ID: 279294

calendar_today

Updated On:

Products

Clarity PPM On Premise Clarity PPM SaaS

Issue/Introduction

On MUX, when Unit of Measure is set to %Availability, on the Staffing Workspace under the Allocation by Investment tab, the Allocation summed total is incorrectly displayed, if a multi-geography Calendar is being used.

STEPS TO REPRODUCE:

  1. Standard Calendar setup: Create a calendar having 7 hours and mark it as Standard. Name this calendar as Base - United Kingdom. Setup some non-working days for Dec 2023 & Jan 2024
  2. Create a calendar having 8 hours and name it Base - India. Setup some non-working days for Dec 2023 & Jan 2024
  3. Create two labor resources and associate the above calendars to them respectively. For example:
    1. India_user, calendar: Base - India -> 8 hrs
    2. UK_user, calendar: Base - United Kingdom -> 7 hrs
  4. Create Fiscal monthly Periods
  5. On MUX create a test project and staff the above-created Resources with multi geography calendar. The allocation period should be from 25th Dec 2023 - 21st Jan 2024, for each resource.
  6. From the Settings menu set the Unit of Measure to %Availability.
  7. Note the Allocation Totals is 200
  8. Navigate to Staffing workspace and access the tabs: Staff , Allocation by Resource. Ensure that the Unit of Measure is set to %Availability
  9. Note: The allocation totals are correctly shown on these tabs
  10. Navigate to the Allocation by Investment tab of the Staffing Workspace

Expected Results : The allocation summed total, for the resources on the Allocation by Investment tab should match with the Staff , Allocation by Resource tabs and with the Project Staff tab


Actual Results : The summed allocation total is incorrectly shown on the Allocation by Investment tab:

The total is being shown as 220.63, instead of 200, when the unit of measure is set to %Availability

Environment

Clarity 16.1.3 and 16.2.0

Cause

This is caused by DE78994

Resolution

This is fixed in 16.2.1