Unable to change the start/finish timestamp for a resource on a team under certain conditions
search cancel

Unable to change the start/finish timestamp for a resource on a team under certain conditions

book

Article ID: 130307

calendar_today

Updated On:

Products

Clarity PPM SaaS Clarity PPM On Premise

Issue/Introduction

Unable to change the timestamp for a resource on the team to a later time then 5:00 PM if the team member's finish date is the same as the project finish date.This issue doesn't happen if you are trying to change the timestamp to a later time (example 10:45 PM) for a resource if the resource's finish date on the team tab is less than or greater than the project finish date. 

For the start day/time of a resource, the behavior is slightly different, you can’t change the start time to earlier then 8:00 AM on any day that is equal to or less then the project start date. You can change it to earlier in the day (Example 5:00 AM ET) if the start date of the resource is later then the start date of the project). 

Steps to Reproduce (using Finish Day/Time):
1. Create a project in Clarity PPM with Start Date of 12/17/2018 and Finish Date of 12/19/2018 
2. Add a team member to the project 
3. On the Team list view, change the Finish attribute's Date/Time Format Scale to 'Day Time' 
4. Change the Finish date/time for the team member to 12/19/2018 10:45 PM 
5. Click Save 
Expected Results: Changes made are saved, the resource's Finish Date / Time is saved as 12/19/2018 10:45 PM 
Actual Results: The resource's Finish Date / Time is reverted back to 12/19/2018 5:00 PM 

Environment

Release: CODFSS99000-15.5-PPM SAAS FedRAMP-Sandbox-Small Environment
Component:

Resolution

This is under review as DE48542.

Workaround: 
Change the finish date of the project to be done day later (IE 12/20/2018). If you do this, then you are able to change the resource finish time to 12/19/2018 11:45 PM. However, this then impacts any future resources added to the project, as their finish date will default to 12/20/2018 instead of 12/19/2018.