This topic is related to:
However, copying milestones looks to me like having different copies of the same thing.
So I am a little bit confused: when there are different projects that rely on the same milestone, what's the best approach? Copy the milestone to each of the projects looks like one solution, but then there's multiple milestones with the same name (with the same purpose), but with different tickets (which are project-bound) attached to them. That doesn't look like a clean solution.
So I wonder if it makes sense to have a milestone that spans several projects, so that tickets of different projects can be assigned to it.
Collecting We're collecting votes & feedback about this suggestion!