Skip to content

Trigger Epic events after transaction has been finished

Nicolas Dular requested to merge nd/fix-epic-transaction-issue into master

What does this MR do and why?

Ensure to trigger the epic creation and update event only after the transaction is done. This way we can guarantee that regardless of which other Service calls the Epics::UpdateService or Epics::CreateService, we always perform the job after the transaction finished.

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.

Screenshots or screen recordings

Screenshots are required for UI changes, and strongly recommended for all other merge requests.

Before After

How to set up and validate locally

  1. Enable epic_creation_with_synced_work_item
  2. Enable validate_epic_work_item_sync
  3. Create/Update epics
  4. Watch the log tail -f log/epic_work_item_sync.log to make sure we log correctly
Edited by Nicolas Dular

Merge request reports