 Hey everyone, John at GitLab again strategic marketing I wanted to share a little bit about how you can get insights out of GitLab and and how your issues are tracking and being managed It's been a challenge a lot of people have asked me about and there's some really cool ways You can do that in GitLab And I want to show you at least one of the ways we're doing it in our team Looking at the status of work and the type of work. It's called GitLab insights Let me dive in and just show you exactly what it is and how to get to it GitLab insights is a part of analytics if you look at it in the under the project An analytics also exists at the group level as well But I'm gonna focus on the project level for the sake of our discussion quick discussion this morning So first off it's under insights if I click on insights it brings up the insights page And I'm gonna collapse the sidebar I don't want to look at that for the moment and you can see it's a series of charts and graphs we can have Bart stacked chart bar charts bar charts a whole host of different views I'll show you a line chart in a second. This is a view of different issues that I've did on an earlier video where We're looking at the status of work in a workflow from new requests to triage to assigned or backlog to when it's actually completed And in product marketing our team is managing a number of different kinds of work And and so we wanted to look at the kinds of issues that are coming in and so we're looking at just new issues coming in and how many issues the team is getting on a Monthly basis and you can decide divide this up monthly daily weekly Those kind of slices and then we divide the work further down. I'm gonna skip this these two here We divide the work into detailed and I like scope labels each of these are scoped labels One is work on the web work on collateral events Each of these scoped labels and if you learn want to look about scope labels scope labels basically mean you can have only One of this group of labels in an issue So if I change it if I add a different scoped label, the other one is removed So it's a only one of those labels So this gives us a way to divide up the work and to understand who's working on what different kinds of things We're working on based upon issues Well in order to summarize that we wanted to break it down into internal versus external We've created a rule we created a rule and we implemented that using the triage bot that says look everything It's web or collateral or events or AR or PR or sales is external We're working on things that are external and there are some things that we work on that are more internal of helping the team It's messaging its decks its research enablement. And so when we did that we were able to then to Assign some new scope labels and and the capitalization matters So I put the capital M there because I wanted to just make it different This is external versus internal other and now we can see the ratio of the work We're doing and we can also see it in a bar chart and this is the bar chart view of this And I thought well, that's awful interesting. What if I wanted to look at it from the perspective of What are the different kinds of things that we're doing focusing on external? So we looked at it a different view So this is the external and the other thing is you could toggle these on or off and see them or not But here is this this is a view of external initiatives and the distribution of things We were working on again really interesting and really helpful in leading and managing the team So the next thing you might say is well, that's great, but how do I set that up? Well, the first thing you do is you go search and get you go to the GitLab documentation on insights Insights is available as a feature and you can use this to look at and to slice and dice your data And as you go through it you can configure this it's configured in a YAML file And I'll show you ours that we're using in strategic marketing, but it's very straightforward to do Let's go take a quick look at that and we'll wrap up okay, it's in our repository under files and It is a file under the dot-git-lab folder and it is called insights.yaml and it is a structure where it simply is Defining the different things you want to look at so you see the Query with the different labels of what type of thing you're going to look at whether it's a merge request and its status Whether it's closed or open and then what are the subsets? What are the buckets you want to look at how frequently you want to group it? So this defines one chart real straightforward real simple this section up here It defines the sections of the chart that you want to show So all of it is defined in this in this YAML file saved and committed and then when you go ahead and run GitLab insights It reads the file and builds charts for you pretty awesome I'm real excited about how it helps us do our work and how we're working using it to get things done We're improving this all the time. It's a minimum viable change one step after other makes it better So if you're interested in learning more, here's a quick link that will take you to the documentation on GitLab insights If you're interested, I urge you and encourage you to go play a lot play with it and try it out but with that that's a wrap and have a great day and Please please contribute everyone can contribute if you want to give us feedback on something open a merge request Help us make GitLab better. We're all in this together trying to get the most out of GitLab and make it as good as we can Thanks very much and take care everyone