Hi Team,
When we resource lock a task to the ISP bucket (resource lock and date&time lock), and afterwards we try to commit it. We see that this task then gets committed to today (ie sysdate), and not to the day that it was originally planned (and date&time locked). This creates issues and great risk and impacts ISP bucket implementation deployment.
Steps to replicate issue :
1. Task is unallocated.
2. Try to allocate task to ISP bucket by resource lock and date&time lock to ISP bucket resource.
3. Commit the task.
4. Task gets committed to today instead of actual date when it was planned.
Can some one please help on this urgently?