Transfer start and due dates data upon work item move or clone
What does this MR do and why?
Transfer start and due dates data upon work item move or clone
This code change improves how work items handle start and due dates when they are moved or copied between different locations in the system.
The changes ensure that when users move or copy work items, all date-related information is preserved accurately, and the system maintains clean data without duplicates or orphaned records.
We are only creating the DateSource record in the DB as we have triggers to also copy this data to issues table from work_item_dates_sources.
On FOSS we do not need to handle rolling up of dates.
On EE, rolling up is happening automatically after work item is created as we trigger event that is picked up by WorkItems::Widgets::RolledupDatesService::HierarchiesUpdateService.
References
Screenshots or screen recordings
| Before | After |
|---|---|
| dates-before | dates-after |
How to set up and validate locally
MR acceptance checklist
Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.