fix(calendarSegment): SLA escalation date incorrect with calendar #22678
+256
−18
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
The execution time was systematically set to 00:00, instead of following the schedule defined by the calendar.
Example
Case 1 — Ticket created on Monday at 10:00
SLA deadline: Monday at 14:00
Escalation execution: Monday at 13:00
✅ Expected and correct behavior
Case 2 — Ticket created on Monday at 17:00
Remaining time on Monday: 1 hour (until 18:00)
Remaining time carried over to Tuesday: 3 hours
Expected SLA deadline: Tuesday at 11:00
Expected escalation execution: Tuesday at 10:00
❌ The escalation level is executed on Tuesday at 00:00, instead of 10:00