After fixing DE48284, the functionality to post time against an NPIO through an incident is not working properly
STEPS TO REPRODUCE
1. Create a group and add every single access right except Resource Soft Book All - Resource Hard Book all rights
2. Create a user Res1 and assign him to the group above.
3. Ensure the Res1 resource is Open for Time Entry and Track Mode is PPM
3. Locate an incident on the system that is set for time entering and has got an NPIO associated, let say an application
4. On the incident click on the Enter Time button
5. The timesheet for the current week is shown and the incident-application gets added.
6. Submit, Approve the timesheet
7. Run the Post timesheet job
8. Timesheet is posted
9. Check the application where we posted time.
Expected results: As per DE48284, the timesheet is posted and the resource is added to the application team
Actual results: The timesheet is posted and the resource is not added to the team.
(If the resource who submits the timesheet has got Resource Soft/Hard book rights, then is also added to the application team)
10. Navigate to the Classic UI timesheets and locate the timesheets for Res1.
11. Click on the Add incident button
12. Filter for your incident-application, select the NPIO and click Add
Expected Results: The NPIO task to be added to the timesheet
Actual Results: Error 500 - Internal Server Error. The server could not retrieve the document due to server-configuration or other technical problems. Contact your site administrator
((If the resource who fills the timesheet has got Resource Soft/Hard book rights, then you can add the task and post time timesheet)
This is caused by DE55837
Clarity PPM 15.8
This is currently being analyzed by Engineering
If the user who enter time against an NPIO through an incident has got Resource Soft/Hard book rights, then the time entering and posting works OK.
A user who enters time should not need booking rights as additionally it gives the user the capacity to add/remove team members to/from investment teams
Therefore this is not a valid workaround.