Skip to content

Sync legacy epic dates when work item hierarchy changes

What does this MR do and why?

Sync legacy epic dates when associated work item hierarchy changes, by adding/removing or editing child issues/epics.

related to #450302 (closed)

MR acceptance checklist

Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.

How to set up and validate locally

Prepare

  1. Enable feature flag work_items_rolledup_dates
  2. Enable feature flag sync_epic_to_work_item
  3. Enable feature flag sync_work_item_to_epic
  4. Disable feature flag make_synced_work_item_read_only

Test steps

  1. Create a group with a project
  2. In the project create a milestone with a start date
  3. Create an issue A and associate the milestone
  4. Create another issue B without a milestone and add a due date
  5. Create one epic using the URL http://localhost/groups/GROUP_PATH/-/epics/new
  6. Visit the legacy epic synced work item using the URL http://localhost/groups/GROUP_PATH/-/work_items/EPIC_IID
  7. Add issue A and issue B as child issues of the work item
    1. Visit the legacy epic again and its start date should equal issue A milestone start date
    2. Legacy epic due date should match issue B due date
  8. Visit the work item again http://localhost/groups/GROUP_PATH/-/work_items/EPIC_IID and set fixed start date and due date
    1. Legacy epic start date and due date should match the work item dates
Edited by Felipe Artur

Merge request reports