Converting Idea to Project with OBS access fails with PRJ-10012

Products

• Clarity PPM SaaS
• Clarity PPM On Premise

Issue/Introduction

Idea to Project conversion for a user with access that is provided via an OBS fails when there is someone on the Staff/Team.

We have resource who is trying to convert Idea with to a Project, however getting an error PRJ-10012: Attempt to add/update record failed.

 

Steps to Reproduce: 

 

1. Please make sure that there is an OBS which is associated with Projects, Ideas, and which is being used for access rights. This setup can be done by navigating to Administration -> OBS. Also have the attribute created due to this association API enabled

2. Note that the behaviour is reproducible in both Modern and Classic

3. Create an user with the following access rights:

a. Provide below Global rigths:

Idea - View - All

Idea Management - Navigate

Ideas - Create

Ideas - Navigate

Project - Benefit Plan - Edit All

Project - Cost Plan - Edit All

Project - Create from Template

Project - Enable Financial

Project - Financial Plan - Submit All for Approval

Project - Risk, Issue, Change Request - Delete - All

Project - Risk, Issue, Change Request - Edit - All

Project Management - Tiles Navigate

Project Management - Navigate

Projects - Navigate

Resource - Navigate

b. Lets assume that OBS rights are being given to Organizational:Administration

 

-- OBS Rights --

Project - Edit Management Organizational:Administration

Unit and descendants

Project - Edit All - Status Report Organizational:Administration

Unit and descendants

Project - View Management Organizational:Administration

Unit and descendants

Project - Create - Status Report Organizational:Administration

Unit and descendants

Project - Edit Financial Organizational:Administration

Unit and descendants

Idea - Edit Financial Organizational:Administration

Unit and descendants

Idea - Benefit Plan - Edit Organizational:Administration

Unit and descendants

Idea - Edit Organizational:Administration

Unit and descendants

Project - Edit Organizational:Administration

Unit and descendants

Project - View All - Status Report Organizational:Administration

Unit and descendants

Project - View Organizational:Administration

Unit and descendants

Idea - Budget Plan - Edit Organizational:Administration

Unit and descendants

Idea - Cost Plan - Edit Organizational:Administration

Unit and descendants

Resource - View Resource Pool:All Groups

Unit and descendants

Resource - Soft Book Resource Pool:All Groups

Unit and descendants

-- OBS Rights -- 

4. Create an idea and assign at least one resource on Staff tab. 

5. Populate the Idea's OBS attribute with "Organizational:Administration"

6. Create project template and ensure there is no OBS attributed populated.

7. Submit the idea for approval. Approve the idea from an admin account.

8. Convert the idea to project and notice error and idea is not converted.

 

Note: if OBS populated at the project template it is working as expected.

 

Expected Results: it should allow to convert idea to project.

 

Actual Results: it is not allowing to convert idea to project when there is at least 1 resource assigned in the Staff.

Resolution

DE80464

Resolved in Clarity version 16.2.2.1 and 16.2.3

Additional Information

Consider below behaviour change when managing access rights via OBS:

1. To handle this while copying the value from project template, we are now checking if the instance already has the value from idea then we are skipping copying value from template.

2. If Idea has no value then we are copying the value from project template.

3. We also considering scenario, where both project template and idea has no value for the OBS attribute but user has selected the value in the create popup while converting the idea. In the case, at the time staff copy project instance has no value for OBS as both template and idea has no value.