Description:
Inconsistencies in Due Date Calculation for KPI Reporting
While utilizing assignment due date values for KPI reporting, we have observed discrepancies. Although most tasks have a duration of one day, the calculated due dates occasionally extend beyond this timeframe.
Could you please explain the precise logic behind the due date calculation? I have attached some examples where the calculated due dates exceed 24 hours from the start date, despite the task being set for a duration of one day.
Works with Evolve
Cause:
Configuration
Solution:
Explanation of Due Date Calculation Logic
In the specific scenario where the user is in +1 GMT and the server operates in -6 GMT, the due date calculation logic incorporates weekend time calculation by converting UTC to server time and excluding weekend hours.
Based on the recent update from our engineering department, it is noted that the majority of entries pertain to Mondays. If a task’s calculated due date falls on a weekend, the system ensures that additional hours are added until Saturday and Sunday have passed, resulting in the due date falling on a weekday.
If you prefer to disable this feature known as the “Business Calendar,” where only 24 hours are added regardless of weekends, you can modify the BusinessCalendar key value to false within the Setting -> Workflow section. A screenshot has been provided as a reference for your convenience.
