Update issue milestone when closing merge request milestone updated (and also reverse)
- We want to keep issues and associated mrs in sync.
- This is hard because issues and mrs are not one to one.
- Besides having the benefits of synching between issues and mrs, this would have an immediate impact on connected epics too! So when you update a mr milestone, the issue milestone gets updated, and then the parent epic's dates get updated, and even it's parents dates will be updated too. https://gitlab.com/gitlab-org/gitlab-ee/issues/7332
- This is extremely powerful since a change at the code source of truth (merge request), bubbles up and reflects the high-level planning (epic) source of truth. It is one source of truth, there are no inconsistencies.
Also considering the reverse (https://gitlab.com/gitlab-org/gitlab-ee/issues/7475#note_103183999): When you change an issue milestone, automatically change any mr's milestone that closes that issue.
Edited by Andrew Winata