Better planning capability

Description

We've discussed this a lot recently around the trouble we have trying to plan out longer term milestones and releases without making visible or misconceived commitments.

For example, if you have a pretty good idea that you want to do X,Y,Z over the course of three milestones, or want to target something potentially for milestone N, you generally end up setting the milestone and then having to explain to people that this isn't actually happening, but maybe happening and they must just know to only believe the commitment when they see Deliverable.

Proposal

I personally think that using issue boards would be a great way to do this. Imagine having columns such as 9.1 9.2 9.3 etc... and being able to move things around as such.

However, issue boards are based on visible labels, and this will just confuse matters more.

So what if you could basically have issue boards that are based on "invisible" labels or some other solution, that way the metadata isn't necessarily communicated (e.g. X added 9.2 label has a similar implication to a milestone).

Of course, that's a suggestion, but planning future releases isn't just a problem we have internally at GitLab, it's a general challenge with longer-term planning and a solution here would not only work well for us, but for all of our customers.