Time Entry Charge Code drop-down field displays all Charge Codes in the system regardless of the investment task context

Products

• Clarity PPM On Premise
• Clarity PPM SaaS

Issue/Introduction

When adding a charge to a time entry, the drop-down does not show all valid values if many investment-specific exist on the system. The list of values retrieved is limited to 200. If the values you are looking for are not retrieved on the 200 value limit, you cannot select it.

STEPS TO REPRODUCE:
1. Enable investment-specific charge codes on the system (Administration > Project Management > Settings > Enable investment-specific charge codes)
2. Administration > Project Management > Charge Codes
3. Create a few global charge codes: 5 values starting with the A letter
4. Create 195 charge codes linked to project X and values starting with the B letter
5. Create 10 charge codes linked to project Y and values starting with the C letter
6. Ensure projects X and Y do have a task that is open for time entry and a resource is assigned to those
7. Open a timesheet for the resource assigned to the projects above
8. Add the project X task to the timesheet
9. Search for the charge code for the task
10. The drop-down menu shows Charge Codes starting with A and B irrespective of whether the time entry investment has got investment-specific charge codes, but you can select the desired value as the values you can select are inside the 200 value limit retrieved by the rest call
11. Add project Y to the timesheet and edit the drop-down of the Charge Codes.

Expected Results: No investment-specific Charge Code for project Y (values starting with C) is displayed. Only values starting with A and B are displayed. The Charge Code drop-down should filter down by the Generic Charge Codes as well as the project-specific Investment Charge Codes for the task selected. Other investment specific Charge Codes should be excluded
Actual Results: You are unable to see any investment-specific charge code starting with C as those are outside the 200 limits of the rest call 

Cause

This is caused by DE68850

Resolution

This is currently fixed in 16.1.2