Dates inconsistencies in new advance task wizard and schedules #4079
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.
What
This PR addresses two bugs:
Incorrect Duration Display in Schedules Table: The issue was with the
event.duration
getter, which incorrectly included weeks in the duration calculation, leading to inaccurate duration displays in the schedules table.Start Date Issue in Task Advance Wizard: The problem is from using
moment.day()
(which returns the day of the week) instead ofmoment.date()
(which returns the calendar day) when setting the start date for a new task, resulting in incorrect start dates.Why
These fixes ensure the application's scheduling and task management functionalities work as intended, preventing confusion.
References
GEA-610
Checklist