Description:
A Project Risk is not deleted when user has instance or OBS rights directly assigned or assigned through a group. Only the Global All right works as expected.
If end-user has Group or Instance rights assigned to delete risks, the risk is not deleted, no error message or warning is presented to the user on the Clarity application UI and an error message is generated in the APP-NIKU.LOG file.
APP-NIKU.LOG ERROR:
RIM_DELETE Incorrect project context for delete or insufficient rights to delete. Delete operation aborted.
Steps to Reproduce:
GROUP OBS RIGHTS:
- Login to Clarity as an 'admin' user
- Admin Tool > OBS
Add a 'TEST' OBS Unit to an existing Project OBS
Example: OBS Unit = 'aaa/TEST'
- Admin Tool > Resources
Add a new Resource 'Resource1'
Do not add any rights at this time
- Admin Tool > Groups
Create a new 'Risk Delete' Group
Go to Group: Resources and add 'Resource1'
Go to Group: OBS Unit Access Rights
Click 'Add' button
Select the 'aaa/TEST' OBS Unit
Select the following access rights:
- Project - Risk, Issue, Change Request - Delete
- Project - Risk, Issue, Change Request - View
- Main Application > Projects
Create a new Project 'My Risky Project'
Assign 'Resource1' as the Project Manager
Select OBS 'aaa/TEST'
Create Risk1, Risk2, Risk3, Risk4
- Log out
- Login as 'Resource1'
- Navigate to 'My Risky Project' > Risks/Issues/Changes tab
- Select 'Risk1' > click 'Delete' button, click 'Yes' to confirm deletion
Expected: Risk should be deleted
Actual: Risk still appears. No error message.
DIRECT INSTANCE RIGHTS:
- Login to Clarity as an 'admin' user
- Admin Tool > Resources
Locate 'Resource1'
Go to Resource: Instance Access Rights
Click 'Add' button, Object = Project
Select the following access rights:
- Project - Risk, Issue, Change Request - Delete
- Project - Risk, Issue, Change Request - View
Select 'My Risky Project'
Remove Group: OBS Unit Access Rights
- Log out
- Login as 'Resource1'
- Navigate to 'My Risky Project' > Risks/Issues/Changes tab
- Select 'Risk1' > click 'Delete' button, click 'Yes' to confirm deletion
Expected: Risk should be deleted
Actual: Risk still appears. No error message.
DIRECT OBS RIGHTS:
- Login to Clarity as an 'admin' user
- Admin Tool > Resources
Locate 'Resource1'
Go to Resource: OBS Unit Access Rights
Click 'Add' button
Select the 'aaa/TEST' OBS Unit
Select the following access rights:
- Project - Risk, Issue, Change Request - Delete
- Project - Risk, Issue, Change Request - View
Remove Resource: Instance Access Rights
- Log out
- Login as 'Resource1'
- Navigate to 'My Risky Project' > Risks/Issues/Changes tab
- Select 'Risk1' > click 'Delete' button, click 'Yes' to confirm deletion
Expected: Risk should be deleted
Actual: Risk still appears. No error message.
GROUP INSTANCE RIGHTS:
- Login to Clarity as an 'admin' user
- Admin Tool > Groups
Locate 'Risk Delete' Group
Go to Group: Instance Access Rights
Click 'Add' button, Object = Project
Select the following access rights:
- Project - Risk, Issue, Change Request - Delete
- Project - Risk, Issue, Change Request - View
Select 'My Risky Project'
Remove Group: OBS Unit Access Rights
- Log out.
- Login as 'Resource1'.
- Navigate to 'My Risky Project' > Risks/Issues/Changes tab.
- Select 'Risk1' > click 'Delete' button, click 'Yes' to confirm deletion.
Expected: Risk should be deleted
Actual: Risk still appears. No error message.
Solution:
WORKAROUND:
Assign Resource: Global Access Right 'Project - Risk, Issue, Change Request - Delete - All'.
STATUS/RESOLUTION:
Resolved in Clarity 12.0.6 Generic Patch. Reference TEC522707
Resolved in Clarity 12.1.0
Resolved in Clarity 13.0.0
Keywords: CLARITYKB, CLRT-52752, CLRT-57236, demand, itl, risk issue management, clarity12resolved, clarity1210resolved, clarity13resolved.