This issue is occurring specific for sub objects of projects like Change request, Risk, Issue etc. Some project (ie. projectA) and risk in some other project (ie. projectB) are having same internal ids and risk is having some locked attributes. Then we cannot create risk in projectA. The application code is not properly checking the data.
Steps to Reproduce:
Expected Result: Change request is successfully created for this project
Actual Result: Change request is not created, and we get error: OSF-0005: Changes were not saved as at least one attribute is locked. To see the locked attributes, reload the page.
Resolved in Clarity 13.3 Generic Patch. Reference TEC605767
Resolved in CA PPM 14.1
Release: ESPCLA99000-13.2-Clarity-Extended Support Plus