Define target branch on Milestone and apply filter on merge request dialog

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Close this issue

Proposal

For our Git Project we have multiple actively maintained release branches. Each of them typically has one or two open Milestones defined.

For example:

• branch: master, Milestone (2022.1.0)
• branch: release/2022.0.x, Milestone (2022.0.1 & 2022.0.2)
• branch: release/2021.0.x, Milestone (2021.0.5)
• ...

All of these are currently in Status "Open" and we obviously have then more in Status "Closed" When a new merge request is created against master the expected Milestone to be set is 2022.1.0 in this example

Since currently all Open Milestones are beeing available on the Merge Request edit Dialog it regularly happens developers choosing the wrong Milestone. For example target branch is "master" but chosen Milestone is "2022.0.2". This currently requires manual checks to validate the correct Milestone set Before Merge Train is started and can easily be missed.

For us the best option would be:

1. when a Milestone is defined a target branch can be selected
2. AND in the Merge Request edit Dialog only Milestones for the selected target branch are available.