MUX - Task Module is not reflecting task name as locked when it actually is.

Products

• Clarity PPM SaaS
• Clarity PPM On Premise

Issue/Introduction

Task Module is not reflecting task name as locked when it actually is. For example, we have a task shows that the task name is not locked and can be changed when looking at it in the task module. However, if you look at the task w/in the project, it shows as locked and the task name cannot be changed/updated.

Steps to Reproduce: 

1. Lock task name attribute in the prior version using process.
2. Once upgraded to version 16.2.0 navigate to MUX->Task module.
3. Go to Details flyout for one of the task for which task name is supposed to be locked.
4. Notice it is not locked and user can change the value.
5. When navigating to Project->Task and check details flyout for the exact same task it is showing lock icon and it will not allow user to make any changes to Task Name.

Expected Results: It should not allow to make changes to Locked attributes under Task module.

Actual Results: It is allowing to make changes to Locked attributes under Task module.

Resolution

DE79596, Will be addressed in the future release.

Workaround:

1. Use blueprint rule to not allow editing Task Name.

2. Reach out to Broadcom Support for one time correction script.