Group milestones associated with a release when downgrading plan
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Context
!43385 (merged) added the ability to associate group milestones with project releases via the API for GitLab Premium customers.
!46027 (merged) adds the ability to associate group milestones with project releases via the UI for GitLab Premium customers.
Problem
If a GitLab Premium customer adds group milestones to a release, and then downgrades their plan, do the group milestones stay associated with a release?
If yes, this will prevent the user from editing a release via the UI on the edit Releases page, because when we send their new milestones array in the edit payload, they won't be able to change the existing set of milestones that contains group milestones (the license for changing group milestones won't be enabled.)
Otherwise, if the group milestones become de-associated on a plan downgrade, then no action is needed here.
Proposal
When a customer downgrades from GitLab Premium, we should dissociate group milestones from releases. Ideally, I think we should "suspend" group milestones associations by keeping track of those milestones in a db table. This way, if the user upgrades back to GitLab Premium, we can re-associate all their group milestones with releases.