Blueprint Contains Secure Attribute That Is Not Shown

Products

• Clarity PPM On Premise
• Clarity PPM SaaS

Issue/Introduction

A user with rights to edit a blueprint can add a secure attribute which the user does not have rights to view or edit, but after publishing the blueprint, the secure attribute is not shown anymore even though it is in the blueprint.

Steps to Reproduce:

1. Create a project object attribute.
2. Make the attribute 'secure'. Do not add any groups to it (or add any groups where the user who will test does not belong to).
3. Edit a project blueprint. In the properties module, the attribute is listed and shows the shield icon next to it.
4. Add to the blueprint and publish the blueprint.

Expected Results: The attribute is displayed in the published blueprint.

Actual Results: The attribute is not displayed in the published blueprint.

5. Edit the blueprint again.

Expected results: The attribute is displayed in the blueprint (edit mode). The attribute is grayed out in the list as available to add, as it is already in the blueprint.

Actual Results: The attribute is not displayed in the blueprint (edit mode). The attribute is shown in the list as available to add (i.e.: not grayed out).

6. Add the attribute to the blueprint.

Expected Results: This step should not be possible as the attribute is already added into the blueprint.

Actual Results: An error is displayed BLP-1705: Could not add field as it already exists for the same blueprint.

Environment

Clarity 16.2.3

Cause

DE156254

Resolution

This issue is fixed in Clarity 16.3.1.