IV97838: WORKING HOURS WITHIN A TASK ARE NOT ALWAYS BEING CALCULATED CORRECTLY
Closed as fixed if next.
If a task has a calendar and the 'Planned End' or the 'Actual End date/time' field values are updated, the Working Hours are not calculated correctly This problem can be seen by doing the following: 1. Open a new task 2. Name and save 3. Attach an availability calendar if the host project didn't already have one 4. Add planned start date 5. Add working hours 6. Save 7. Add an actual start date using hours different than the planned 8. Add actual end date 9. Note that the working hours do not seem to factor the calendar hours
Task working hours are not calculating correctly. The issue was the values for the calendar fields (Year, Month, Day, etc) were not being correctly set. The fix is to set the Calendar fields exactly as we do for the other calculation methods.
Resolved a task record/Gantt chart issue where actual working hours and actual working days were not being correctly calculated when an actual end date value was entered. This is targeted to the 1h2017 release.
Reported component name
Reported component ID
NoSpecatt / Xsystem
Last modified date
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Applicable component levels