Projects 'Actual Transactions': 'Task' and 'Resource' filter fields

Products

• Clarity PPM SaaS
• Clarity PPM On Premise

Issue/Introduction

The "Task" field on the Actual Transactions page filter of the Project Financials module in MUX, shows every project task in the system and is not limited to the current project. The same occurs with the "Resource" field. Every resource on the system is pulled and is not limited to the resources of the project

Steps to Reproduce:

1. Navigate to the Modern UX -> Projects Grid -> Click on any project record -> Click on 'Tasks'. Note down the number of tasks displayed here
2. Navigate to Financials tab -> Actual Transactions sub tab
3. Open the filter -> Add Filter -> Choose 'Task' filter
4. Click on the 'Task' filter drop down.

Expected Results: The filter shows only those Tasks that are present in the Project. The number of Tasks matches with the observation from step 1.

Actual Results: The filter shows all Tasks in the system, from all investments.

Environment

Any supported Clarity release

Cause

This behaviour was analyzed via DE167136.

Resolution

By design the 'Task' and 'Resource' filter fields are not restricted to show only those Tasks/Resources that belong to a particular investment.

The Views that are created in this page are carried across to all investment instances.

So, if Tasks or Resources of one particular investment are chosen, and if those Tasks or Resources are not accessible in another investment, then the Views will start causing issues.

As of 16.3.2, in order to help with the selection of Tasks and Resources that belong to the same project (as task names and resources can match across projects, two new columns have been added to the Tasks filter:

• Investment Name
• Investment Code

These columns can help in picking the right Tasks/Resources.

Additional Information

There is a design change targeted for Clarity 16.4.2 where the Actual Transactions portlet will display data limited to the current investment. This is being worked on through a user story. There is no commitment the user story will be implemented in time for Clarity 16.4.2