Reduce false positive mismatches for epic sync validation
What does this MR do and why?
We don't keep lock_version in sync, as it's not necessary to have the same lock_version for optimistic locking.
Add information from where the event is coming from when logging the mismatch.
Remove chance of a flaky spec.
Decrease the chance of comparing an outdated epic record with new data from the database from the work item side.
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
Numbered steps to set up and validate the change are strongly suggested.