 Hi everyone, my name is Victor Wu. I'm a product manager at GitLab. Today, I wanted to show you a new feature It's called scoped labels. So what you see on the screen right now is a bunch of labels on this labels screen And you can see that there's a scoping for these purple labels It says platform double colon Android, Ubuntu, Windows and so forth and then same with state with these blue labels So you can already see what I mean by scoped labels is that there's a scope and then there's a value So all these belong to the same scope because they share platform double colon not because they're the same color I could actually use different colors, but the scoping will recognize The the word platform, but I'm getting ahead of myself Let me show you how to use scope labels before coming back to talk about how you manage and create scoped labels So one way to use scope labels that is very interesting is you can use them as effectively like custom fields So again going back to this This example here with the purple scoped labels. This is essentially a custom field That say you wanted to assign any number of issues merge requests for you in epics to say that you associate with them a Custom field that says identify it as what operating system or what platform So what you can do here is that say this particular feature that you're working on represented by this issue You wanted to say that it belongs to iOS and so what you can do is you can assign that to iOS and then Right away it gets that label and it does exactly what you would expect it to do And then you see the nice system note here as well, and it also even says as you know scoped label Now say now I'm looking at this issue and now I've decided that oh, I actually added the wrong label Or it's actually not iOS. It's actually Android. I put in the wrong custom field as a work what I could do now is actually click Android and What happens is that now Android the Android labels apply platform to record Android and iOS is automatically removed So that's precisely how scoped labels work Given this object this issue. It can only contain One scoped label of that given scope namely platform colon to be more specific the correct logic is is is Put into place when you actually apply the label that's when the logic is adhered to but in any case you can see how this You've been able to use this platform double colon as a custom field So say you have any if you have any use of a custom field with an enumerated number of options This is a great way to use this feature another way to use Scoped labels and now that you understand that they're essentially mutually exclusive labels is for workflow states And so you can see these states, you know development review production Ready represent workflow states, so I've already set up a board here and so you can see Here you have these workflow states represented up top in this agile workflow board So if you've been using gilab for a while, this should seem familiar and some of you might even use State colon something and we purposely chose double colon because we looked at our user data And we found out that double colon is not being used very much. So we thought that would be a good way to release this feature For for something that's not being used or that the title in particular delay title But anyways back to the feature So how you could use this is exactly as you've been using issue boards before you can drag this issue over one at a time As you see so at first this doesn't seem like it's anything new and Indeed, there's nothing new with this particular view You're able to judge issues one over the other in this workflow board But what's really super relevant is when I actually go on to the issue itself and you can see that it went into development and then went into ready and then went into review and What's important is that when it went into these stages gilab automatically removed the previous Stage so prior to this feature if you wanted to use labels to represent states in a workflow It would work very well in this case because when you drag an issue from one state to another state The previous labels removed in the new labels added But if you try to do the same thing here, you would have to do it in two steps You would have to add the new label and then remove the previous label and some of our users were saying that that's very cumbersome It's not very intuitive but now what you can do is if you're in this issue and you're not looking at the workflow board So maybe you're a developer Maybe you're a QA engineer and you're not looking at the workflow board all the time But you're just looking at one particular issue and you want to change the state advance the state If you want to go to review all the way to production you can do that And once you put it into production It automatically removes the review state for you as you see the the system note right here And so there's no confusion. There is only one mutually exclusive Workflow state I'd use as you set it up So how do you create these workflow? Labels are Steve's I started these scoped labels in the first place and what we've done in good lab to design This feature is something we think that's very interesting and to make it very very simple We haven't added any additional menus or additional UI to make it complicated. All we've done actually is just Asked our users yourself as if you're watching this video just include the double colon by including the double colon a Label becomes a scoped label. That's all that happens. That's all that's required So once you click edit here So pretending I'm creating this label for the first time and I added this double colon And there's this nice new little help Text telling you about that This will automatically become a scope label. So the moment I remove the double colon and do say like a dash It's no longer a scope label. So I click save and I go back and you can see this little helpful question mark Is not there anymore Indicating that it's not a scoped label. So I'm going to go back click edit Changing back double colon and now it's a scope label. So that's all I did I didn't have to click any checkbox or anything. You know that recognizes. It's a scoped label simply by the double colon So that's really all that there is to scope labels. It's it's really simple and we really like it So this feature is available On the premium tier. So that is For self-managed instances of GitLab and for GitLab comm which I'm showing you right now It's available for silver and above. So if you're using gilab comm this feature is already available And if you have a group on gilab comm with a silver subscription or a gold Subscription and you create any labels in that particular group or in the subgroups or projects of that, you know group hierarchy Then you will have access to this of functionality if you're not in one of those tiers and you use the double colon syntax GitLab will just ignore it. It will just be used treated as a single as a Non-scoped label a regular label. So again, if you're on gilab comm It will be available for silver and gold subscription for self-hosted instances This will be available for the premium tier and the ultimate tier And this feature will be made available In October 22nd. So that's 11 days out in GitLab 11.10 And again, that's on April 22nd for self-hosted instances, but if you're using gilab comm it's already available Thanks for watching