Project Change Request in Project - need guidance on PCR Reason dropdown choices

[Lisa Winder]

On the Project Form there's a Project Change Request Related List tab.  Our IT Gov team has requested a change to the list choices to be vendor independent with the ability to identify the vendor that caused the need for the change.

For example, we currently have several vendor specific reasons to select from:

1. Vendor XYZ extended schedule due to resource availability

2. Increase in scope due to Vendor XYZ

3. Infrastructure delay due to Vendor XYZ

The above isn't the best design as the list continues to grow as we add more vendors. Stakeholder is requesting that specific vendor names be removed from choice selections, however, they still have a need to track which vendor caused the change and are asking for a new field to be added to select offending vendor. Is this the best approach for satisfying this need?

This isn't a simple change as changing the drop-down has ramifications on existing queries including reports and custom list view filters.

I'm looking for any recommendations/insights for best way to go about satisfying the requested requirements. Solution alternatives (if any) and how we would go about ensuring reports and custom list filters are still working. Is there anything else we need to consider related to impacts besides reports and custom list views?

[Namita Mishra]

Hi @Lisa Winder ,

I agree with your approach of not configuring the list with the vendor names.

Can you try configuring the contract.vendor field on the project change request? 

Thanks,

Namita Mishra

[SasankaV]

Hi @Lisa Winder , I faced a similar use case in the past. I considered the below steps to configure the best design:

- Update the PCR Reason Dropdown:
- Navigate to `System Definition` > `Choice Lists`.
- Find the choices for the PCR Reason field.
- Replace vendor-specific reasons with generic ones, such as:
1. Extended schedule due to resource availability
2. Increase in scope
3. Infrastructure delay

- Add a New Field for Vendor:
- Navigate to `Project` > `Change Request` > `Fields`.
- Add a new reference field for selecting the vendor.
- Ensure the field references the vendor table or similar.

In addition, consider potential impacts:

- Check for any custom scripts or business rules that might rely on the old PCR Reason field.
- Update any automated processes that reference the PCR Reason dropdown.
- Ensure that historical data remains accessible and understandable.

Give this a thought. If you wish to discuss my approach in detail, I'd be happy to assist.