Assign issues to multiple milestones
Maybe there's a better way to handle this, but lets say I have a version 2.7 maintenance release with its own branch, and I'm working on a 3.0 development release on master. An issue comes up that affects both 2.7 and 3.0. I would like to be able to assign the issue to both milestones, e.g. 2.7.1 and 3.0. It seems like I can only assign issues to a single milestone.