User is not able to see the list of assigned resources in the 'Assignments' sub-tab of the Tasks Details flyout
book
Article ID: 382591
calendar_today
Updated On:
Products
Clarity PPM On PremiseClarity PPM SaaS
Issue/Introduction
In mux with below rights project manager is able to add assignment under task but unable to view the same assignment post addition
Global - Project Management - Navigate
Instance level - Project - Manager (Auto)
Steps to Reproduce:
Login to clarity as Administrator
Create a new user (example Test User)
Grant Test user the below rights
Global - Project Management - Navigate
Now make Test User the project manager of one of existing Project, that will ensure the Test user automatically gets Project - Manager (Auto) for that project under instance level
Now login as Test user and navigate to project for which Test user is project manager
Under the project configure few modules like Properties, Task, Assignment, Staff
Create a new Task (Example Test Task 2)
Now under Test Task 2 open the flyout and configure Assignment image below
Try adding a resource to the user
Project Manager (Test User) is able to assign a resource who are added to staff even though an error is shown which indicate user doesn't have permission
Now navigate outside task and come back to Test Task 2 and Test User (Project Manager) is unable to view the task
Same Test user when navigate under Module Assignment nothing is shown there also
Expected Results: Test User (Project Manager) shouldn't be able to assign any resource under Task Detail Fly out
Actual Results: Test User (Project Manager) is be able to assign any resource under Task Detail Fly out but unable to view the assigned resources.
Environment
16.2.x
Cause
DE156491
Resolution
Workaround: Add the Tasks 'Assigned Resources' field to the column layout or to the 'Details' sub-tab in the flyout and use that field to see and select the assigned resources. Use the 'Assignments' Module to see and add new assignments.
DE156491 is fixed in 16.3.1 (Targeted to GA February 2025) and also being targeted to be backported to 16.2.3 Patch 2 and 16.3.0 Patch 1