When a user opens a project that contains a subproject, and the user only has view rights for the subproject, there are inconsistencies in the behavior when opening the projects (depending on the data of local temporary files). The data displayed does not match the one in Clarity in all scenarios.
Steps to Reproduce:
--
Actual and Expected Results: Project Save Error (the project is NOT saved back to Clarity).
--
Actual Results: Only the subproject is opened. The subproject contains the changes done earlier (these are not in Clarity). The parent project is not opened
Expected Results: It is not possible to open the parent project in Read-Write mode.
--
Actual Results: No project is opened.
Expected Results: It is not possible to open the parent project in Read-Write mode.
--
Actual and Expected Results: Both projects are opened. The subproject is also appearing inside the parent project as a subproject with all its tasks.
--
Actual Results: A "Cannot find inserted project" pop-up is shown. After clicking on Cancel, both projects are opened, but the parent project does not contain the subproject tasks.
Expected Results: It is not possible to open the parent project in Read-Write mode.
Release : 16.0.3
DE69084
This issue has been fixed in Clarity 16.1.3 and 16.0.3.6.
For the highlighted steps (Actual Results after steps 6, 8 and 11), this will be the new behavior: A popup message will appear about the subproject not having sufficient rights, and allowing to open in Read-Only mode. Based on the selecting, the projects will be opened in Read-Only Mode, or not opened.