 In 11.2 we'll be working on a feature called issue board milestone lists. This is a third type of lists inside the issue board. We have label lists, a signing list, and milestone lists. So I wanted to give a little bit more context on why we're doing milestone lists. So right now issue boards are very versatile inside gilab. When we first invented issue boards it was a way to do workflows something like this where you have a black lock of issues and then you drag them into in development, inside in review, and so in gilab we only have two stages but other organizations using agile or related methodologies you might say you know in development waiting for development in qa inside uat in code review and so on and so forth all the way to you know deploy to staging deploy to production and you have you know five six multiple stages and you drag them along the list so it's a workflow. So we invented the issue board to solve that use case and it's a great use case and a lot of different tools have that. The great thing about issue boards in gilab is that we leveraged labels to do these stages and the great thing with labels is that they can not just represent stages but they can represent just a type of issue and so that's why in addition to a workflow board an issue board can also act as a planning board. So as you can see in this case here I have a planning board that is scoped to 11.2 and discussion and I can have different types of lists associated with different types of issues according to label and so because of that versatility we already have two ways to use boards and so this is very different from some other tools where these lists represent stages and that's all you can do and you have to pre-define them because how we invented boards and iterate on boards we have this versatile way of using boards and it's a great thing. So in addition to that of course we have the scoping of the board and we have the filtering of the board but that's sort of not directly related to today's topic and so as we were thinking about how we can even leverage the board in a further way beyond these two use cases the planning board the workflow board how about we put yet another type of list and we did that in a previous iteration and that's the assignee board and so in this case what you can do is in addition to adding a label list you can use an assignee list here and you can assign people as lists as you see here and so this is an example of the discussion backend team and you can see that there are these discussion backend members and you can see the issues that have been assigned to them so now we have a board that can be used as a project management board a board that tells you what people are working on and at GitLab for example we indicate that you are working on something or you're responsible for an issue if you've been assigned to it and so this is yet another usage of issue boards so we have label lists, assignee lists and so we thought why don't we just go all the way what other attributes of issues are there there's labels there's a assignee and there's also milestones so why don't we do milestones and so that's exactly what this is and so the reason why we would have milestone lists is that you can drag issues across milestones and that is precisely a way to do planning across milestones so if you wanted to have say in this example here this mockup doesn't show it but imagine that you have 11.0 here and 11.1 and 11.2 then you can drag issues across milestones and that's a great way to do planning across different iterations and so if you look at other tools like Jero or other similar tools they have a brand new UI they have a different UI just to solve that use case and the great thing about boards at GitLab is that we design this such that or we are designing it such that it's a basic platform it's a basic tool but it allows you to do many things so this is a fourth way that we're allowing folks to use boards which is allowing you to drag issues across milestones and that's exactly the purpose of this feature here so go ahead and review the details look at the edge cases or the specific cases example for example what happens when you move from one type of list in the list it's all specified here but that's the background of boards and even furthermore what we're going to do later as you see we're counting how many issues are here and in the future we're going to count how many weights are here so there's going to be a lot more things going on with the board it's going to be pretty much the centerpiece of project management features inside GitLab it's going to be very powerful and issue board milestone list is one one huge step toward that goal so if you have any questions you know slack me and or just ping me on on this issue here and then we can continue the conversation