GitLab Plan Stage, 28 Jan 2020

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Plan | FY20 Q4 Stage Walkthrough

Description

GitLab Plan PMs review the end-to-end Plan stage capabilities to surface areas of improvements.

A

Hey everybody gaben Kenan, for in the plan stage, product managers, we are going to do a demo according to the definition in our handbook, which is a script to recording and the attempt to influence buyers, given that this is for the okay, our cue for the product organization to get lab, but we're gonna do this, but also with some slight commentary. Added as we go through things, I'm gonna try to cover the full plan stage, see how the benefits awesomeness and from start to finish from all the features.

A

So first thing: you'll notice, as we are in here. This is a demo group, so we're gonna start from the assumption creating a top of a group. It's actually gonna be subgroup just for licensing purposes, and the first thing we're gonna do here is create a new subgroup as if you're setting up get lab for the very first time, so we're gonna go ahead and create a new subgroup product demo called that will go ahead and make it public. So we want to make it public. This is a.

A

Prokta MS I, don't know if we mean Avatar right now, but you can add one pretty great, so we'll go ahead and create project itself is organized into the group subgroup project structure or you can have a project that lives with any group or subgroup and I think up to 20 subgroups within a parent top-level group. So now that we are here, we have the ability to look at epics, which we don't have any um and.

B

Before you go to that yeah, what would be your clear delineator between when I should create a group versus when I should create a project? I? Don't.

A

Know good question: I think Jenna goes back and forth. Typically, people organize I've noticed people and customers have organized groups and subgroups based on how they want to organize their project repositories. Mostly, there are various ways you can do it. We could do it from a portfolio standpoint which I suppose we do like to go ahead and that wouldn't be like to set a portfolio from scratch within an organization I think that makes sense yes, cool. Okay, so now we have a top-level group. I think. The next thing that I would do is understanding.

A

Let's say: I have three different kind of portfolios of products: three different kind of value streams within my organization. The first thing I'd probably do- is go ahead and create dedicated subgroups for each of those. Maybe we'll call this portfolio one and go ahead and make that public as well we'll go ahead and create hot back up to the main demo. One thing I didn't notice. We have a ton of space right here for our crimes, but we're like limiting the amount we're showing because there's not enough space, but there is enough space.

A

That's bothering me a little bit always I, don't know why, when I create a new subgroup for my portfolio to second value stream, sorry for the bland names, but you know it is what it is going up to our top level group again we're gonna create another sub group for a third one, we'll call that portfolio three now we think it lab is the way our labeling system works. Labels created the top group level will inherit down to their children.

A

So a lot of what we recommend doing is going in and creating standardized group labels at the top. So we're going to do that in a second and then we also, as you can see, everything from your sub groups will roll up into your top-level groups, I think maybe before we go ahead and create stuff with them top-level group, you can just create a couple placeholder projects here.

A

Let's call this a mobile app and make this public and initialize this with a readme. One thing that I thought would be great. I always thought this is that when you're creating a new project, we should have a little bit more wizardy type walkthrough. A lot of people, don't realize that you can turn the project repository off and just have issues management if you want to do that from the settings. So maybe for this one we'll turn off our repository and just have our issue.

A

The kind of cool thing that I noticed when I was doing this before, is that, if you turn off your repository, you go back to your project overview. It'll actually show your wiki is the default, but there's no way to specify if you want your wiki default, Lin major. If you want your Rico to be the first at both are enabled. So that's one thing: I thought was a little interesting.

A

Wiki's are outside the purview of the plants age, so we won't kind of get into that, but popping back up now we have a project within portfolio three. Let's look back at the demo here: we'll create projects, a portfolio two and maybe we'll call this the API, but make that public as well and then we'll create one more project inside the top-level portfolio. One subgroup I.

A

Don't know about you can but I've always kind of wished it. There were we'll call this the since we have an API mobile, app live web client navigating between groups and subgroups via web crap, like this structure is kind of annoying. Sometimes suppose you can do things like well. I can't really get back up your parent any other way other than this. So that's that so we have portfolio. Each of these can contain multiple projects, different varieties. You can add members directly this top-level group, which will then cascade the permission, was downstream.

A

So I'm gonna go ahead and add you can Keane in Keith's Nerd Herd. There you go and we'll make you a maintainer. Is that so now that you have access to that, you should get a notification, email, letting you know that, and you should be able to now jump in and see and have access to at a maintainer level, everything within the prog demo group and subgroups. So that's great, we'll jump in next to go.

A

Maybe top level we want to create a objective is kind of a epic and we'll call this improve I, don't know what do we want to improve.

A

Let's see increase adoption rates.

A

Customers and our target markets.

A

Epics are pretty flexible, you can use it to track work and each epoch can have a series of sub epics to think up to five nested deep within the ultimate ear, and then you can also have issues that are attached to an epoch at any level. So, typically, we encourage folks to use maximum three tiers of epics just because it gets a little confusing if you get further than that. But let's go ahead and say we address you increase the adapter rates of customers on target market goals, increase and drive revenue.

A

To capture our Sam, which is our serviceable addressable market, and just to keep with it, I call this like an objective.

A

For the key results.

A

Increase conversion rates- and, let's just say it's 2% now to 5%, increase ARR from let's say you have 10 million right now to 15 million, so we want to increase it by 50 percent.

A

Typically, when you're doing things in the top-level portfolio, don't want to dictate how you want to dictate what the outcome should be. So this is a pretty good example of that notice. At this point, we haven't set up any labels. We can go ahead and create a new group level here or we can manage group labels for the sake of it, I'm going to go ahead and set up some basic workflow labels and some basic hierarchy structures.

A

So we'll call this one thing about: P will do scope labels and we'll call this an objective, or maybe from portfolio playing standpoint theme and top-level epics of all things for our organization that color, maybe the next teardown, will create one called P epic house, that epic level initiatives or a portfolio, so each portfolio then will define their own epics. That map up to the objective and then we'll create another one for features and the cool thing about scope. Labels are mutually exclusive, you'll see how that works later on, but more or less.

A

You can never have anything that just pre fits with the P : :. You can only have one of those labels on the issue at any given time. If you have a new one, it will automatically replace the old one.

A

Work items or a project.

A

And I think we'll go ahead and create a few labels for issue types. We'll call this all feature we'll call this a user story, maybe just a story short make all these punch, and then we can create a new label for T bug.

A

Maybe one tea back in or call tech demos up, he's really flexible, you can mix and match, but typically, if you want to have standardized processes, scope levels a great way to do it. You can map into your issue boards and workflow.

A

So now that we have our epic levels defined as labels, we have our each basic issue, types, maybe bug story, tech, debt and then we're going to go through and add a couple workflow labels. They will do a backlog like all these green.

A

A

Will keep it simple and progress.

A

And we'll create one for review, we'll just call review.

A

I'm gonna have another step, maybe we're gonna do release stuff or it moves through the different environments and whatnot okay. So now that's there. We have the one epic we created I'm, going to go back through I'm, going to pick up our game label, which is great. You can either from here, create a new epic and keep all of your ethics in the support group or if you want to have more controls and not allow anyone in your organization.

A

Let's say you wanted the executive level to operate here and you want your director level to operate at the portfolio like individual sub group portfolio level. You can do that and it will roll up. So what we'll do here we'll go ahead and hop over to our first portfolio that has the web client in it, and maybe what we'll go ahead and do here is create a new epic that will let us.

A

Optimize the conversion phone.

A

And we know that this goal here um go ahead. Make this an objective is to optimize the conversion from one we.

B

Could show that, as you know, increasing a sign-up rate as well as increasing net conversions, yeah.

A

So key results increase conversions and then what would you say? The other one was the side of break so.

B

If we're optimizing, the funnel at the top of it is gonna, be a net new signups. If you increase.

A

The number of signups in then.

B

You can work on crease, increasing your conversion rate, so.

A

Yeah and that new signups increase conversion into paid customer.

B

We could add a third which would be a you know, increase the individual value for each sign up, but that could be a different epic in and of itself we'll.

A

Just with this, for now we're gonna go ahead and save these changes that are there, and maybe this top level. We think hey, let's go ahead and add an issue for one of our projects or crew, go ahead and create a feature. Epic I guess we'll do that first and then create a new epic here and it's going to say see identify they will one do for new signups that.

A

And you sign up stare at the top level and then create another one for increase to pay customer. So we have a pretty clear separation concerns here, which is great. So if I happen to this one now wait. I guess I forgot to add our label. Here we can make this a epic level, because it's only subgroup and then we can hop into our paid conversion epoch and make this maybe a teacher sure. Yes, it also would be and I think this is where it kind of breaks down a little bit.

A

But for the sake of it and we're in here and we're gonna go, you can either add an issue here or if you want to go back up to the top level, actually I, don't think you can. You add an issue now and put it into one of these children epics. Yes,.

B

You can oh yeah.

A

Let's see how that works, I'm.

B

Gonna, create it and then drag it under.

A

Where always get tripped up so I cancel that that would be if I wanted to add an existing link, but I want to create a new issue, so we're gonna. Do that and the first thing I think we want to do is run a be first thing identify where things are breaking down and signup flow.

A

Maybe I'd select a project here, put that in the web, client that's created and then how do I get it inside this one I.

B

Think maybe that might still be behind a feature flag. You might have to add that manually, these okay.

A

So you can do is if you I just copied the link address for this. It happened to this first one. Actually, the second one and I'm gonna add an issue here, so that will reassociate it from this parent epoch down into this one. So if we go back to the parent, epic abyss, you can kind of see how. Now we have that issue, sorry, there's, but with magic Mouse's.

A

um We can see that there, and so the other thing that we're going to do here is add this parent, whose epic we created within the portfolio up into the can get up into the top level objective. So if we go here to the list, we can see the increase that trace of a theme we're going to go ahead and add this epoch here and so, as we can see now, we have all of our epics have rolled up that we created from our subgroups and I, didn't add one here to the net new signs.

A

We should go ahead and add this as a feature called the future level thing and close that out and refresh this we can see. We have some epics, we have a theme, a feature and an epic and then the feature tied to it, which is great bubbling all down. It'd be nice if this kind of was in the hierarchy view, but we are working on that for the roadmap. One of the things to note is right now, there's not showing up in the roadmap because we haven't set you due date.

A

So why don't we go back and manually set something right now and starting at the theme level. Let's say that this is gonna, be a start date of.

A

This past Monday and we need to get it done. I, don't know, I think.

B

At the end of the quarter mark.

A

March so January through March there.

B

A

You can start this in the game. Of course, consistency sake, so we've mainly set these due dates here. So if we hop back over the roadmap now we can see that shows up. In our quarterly view. We can drill down in the roadmap two months in two weeks. We need more and do that, just great we'll, keep it the quarter view and there's also a filtering here. As we get more complex, we can kind of show how that works.

A

So now that we have kind of our top level date set for our theme, we're gonna hop back down and let's look at our next epoch and let's put some due dates. Those is you can kind of see here, which is nice. You can view the hierarchy of your epic tree in the sidebar, so it's easy to hop back up to your parent and no matter how deep you are, which is great and we'll set a due date of this.

A

Let's have this one start this week and let's say we want to get it done by the end of February so great. We have that and then we'll look at children and I guess: they'll probably follow a similar type date. Where maybe we'll start this one on Monday.

B

A

Third and we'll have it due on the fourteenth 21st. Why not hopping back over into our signups?

A

This one's probably gonna, run a little bit longer. Let's just go ahead and plan for that out and we'll start at February 3rd and we'll have it go until March 6th. Why not great? So now we have some due dates if you hop back over to our roadmap you'll notice. Here we can look at the roadmap for this and we have the conversion funnel, which is the parent, and then we have the two below it, which are the conversions in the paid customer.

A

Let's say if we just want to show the epics on this mucus, a label is epic up there and then run that, and it will filter things down to just show us those epics. So you can kind of view it that way. It'll be really nice. When we get the nested kind of being able to drop down and view the hierarchy within the roadmap, I think that's going to be each one I'm excited about it.

A

You can also do filtering by start date by due date, and you can also view things by open and closed and coming shortly, I believe in twelve, eight you'll build CV progress of an epoch as it's linked to issues.

A

Now, let's hop back over a list within this project, and let's say we know we want to increase net new signups. We have an issue here for identifying things that are breaking in sign flow and just as I similar to epics. You have your markdown editor. Here's description great, we can even add tasks. If you want pull data, you know as data and then determine gaps, create follow fun, experiment issue and you can save that what's nice is our description should be version controlled.

A

So if we were to edit this again and say here is another edit and say the changes directly will show you the differ. Maybe that's not enabled for this demo group. It's not it's behind a feature flag, but it's coming soon. So you can be look at the diffs of thing, which is great and within the issue you can do all the great things. There's these things called deduce.

A

So, let's say you're mentioned in a comment and I say: hey Dee Weaver, what's not and say that it will automatically create a deep to do for me. So I can go over my to Do's and I should be able to see that I address myself on issue one, and this is a good call to action. I exclusively used to do so. I, don't use email notifications. We need to do a lot of work here and I spend some time demoing it, but you more or less have different types of juice.

A

On your objects, you want, you can look at who the author was, so you can scope it down to a project or a group, and you can also see what the action was. If something was assigned to me, I might get it to you if something I was mentioned or if I was directly dressed and directly addressed is when the G Weaver comes first or if I wanted to say hey. This is a cool thing and then I say add G Weaver. That is in mention, so there's the difference between the two.

A

So if I go back over, my dues now I can see. I was mentioned and I wasn't directly addressed. So this creates a lot of confusion. We're gonna work on fixing this up in the near future. Some people aren't really sure what the difference is between being mentioned and directly addressed. It's not intuitive unless you just know it and use it regularly, but it is what this cool, so we have our epics. We have an issue. I think the next thing we'll do and is look at our project itself and set up an issue board.

A

Actually we're gonna set up issue boards at the group level, because that way, all issues from your projects within a group or a subgroup roll up into your um an issue board that you can create and manage there. So you can look at cross-functional projects manage work across lots of different spaces more or less, and we're gonna go ahead and do that and there's some defaults here and I'm gonna click on this just for Sid, because he's been wanting me to change it right now.

A

This works you can automatically, it will create to do and to do and I think this should have created some labels for me automatically, which is great so in the in the base case. This works great I think it might break down a little bit if we I don't know if how it will work, we maybe leave one. We go back to our boards. This guess works see how I delete the label it automatically deleted. The list so I think we should probably work on that ik. Some more validation and kind of safety checks.

A

The label management. There's been some people who have said things like hey, I, delete a label and there's somebody delay the label I created in it like messed up my whole workflow and I can't undo it, which is bad, but it is with this. So let's go ahead and create a new board and let's call this Gabe and within when you're, creating a board. You can scope it to a milestone which we haven't shown yet we'll get to it, which is a time box kind of constructed thing get lab. It will track you.

A

You know all the issues in it merge requests that are associated with that, giving time box and then also show you burn down, chart soon to be burning chart, and you can also scope this to labels if you wanted to so. If I only want to see things show up here that are a feature or a bug or a story or tech debt or in a certain workflow process.

A

You could do that as well or you can filter by assignee or wait not sure why somebody would filter a board by weight, because it would only match anything with one single weight. But it's there note self investigate that. I have.

B

Seen a I've seen a user used that to identify a board urge build a board that would identify issues that needed to be broken down further, and then they set up workflows if they like here's, a largest, let's break it into you, know, front and back-end versus most militias.

A

Fascinating, that's interesting. One of the things I thought was interesting about is because we just created a new board, it and I think I. Don't know it was because we deleted label, but that, like Little Helper thing to get started quickly, disappeared in the middle now and not just some list. But that being said, we'll go ahead and add some labels, labeled issue lists based on our workflow, and we can kind of click these to quickly, add them all, and then we can drag and drop.

A

We have a backlog in progress, will review first before we release and then it will go to closed, which is create from the issue board. You can see a couple things that are in flight. You have the ability to filter again, that's pretty standard across the application. We can show and hide labels, which is nice. If you have issues that kind of labels, you can always edit it and you can add lists on the fly, mixing and matching these three different issue list types, whether label, assignee or milestone, and then from here.

A

You can also do things like adding work-in-progress limits, which we just launched and thank you twelve. It's not fully launched it's behind a feature flags though, but it's enabled here so let's say we want to limit the work in progress for our backlog to ten, because we don't want too much and then you can easily escape key by the way to get close that window, which I recently learned. It's been a pretty big time saver and in progress, we're gonna limit, that's a three press ENTER to save and then I review.

A

Let's go ahead and do the same thing when that two three and say that and then our release will just leave, because it is what it is from this view you can directly add issues if you want, so you can given this as a group issue board, you got to specify what project do you want to map things into? One thing that I would love to see is like here.

A

Your your project search looks kind of like this, but if you look back at your epics, for example, when you go into add an issue or create an issue, this drop down is a lot nicer and prettier it's easier to read than like a long mangled path. So I'd like to see that nice UX treatment come into our issue boards in the near future.

A

But that being said, we're reloading and then, if it's sucked, one of the big things were working on this year and it's gonna be a year-long effort- is making everything in get lab more real time, including issue board. So you don't get stuck with loading spinners like that, you don't really need to shouldn't and also if I were to move. This Keene is looking at this board and I were to move this issue over. He would not see that change unless you manually refresh the view which is kind of like yeah.

A

You know not great a nice thing to just highlight real quick. You can minimize your issue list. If you don't want to see the noise you just from a look at a subset but back to the demo, go ahead and create a follow-up issue to run an ad experiment.

A

And we're gonna create that in the web client project submit that, since it's not ready yet and that's a follow on we'll put here, put below whoa what just happened. There.

A

Yeah, that was interesting, wonder if we can recreate that put here that bug.

A

Nope um copy link address we'll, go ahead, open this one. So what you have to do right now to work with issues and issue boards? You have to open them in new tabs or you have to click through, and click back and wait for everything to reload. You can kind of pick your poison either. It's a really good experience, but here's a follow-on issue that we created, save that change and, as you can see, it's got annotated down to the issue number, which is kind of nice.

A

You see the title and then you can see that here. We can also add this as a linked issue which relates to- and you could say this blocks this other issue, so we can't run this until we run the ID experiment until we identify where things are breaking and we have some data on it. So that makes sense it's blocking this. So if we hop over this a/b experiment issue each grade, you can say it's blocked by which nice way to go. We just released blocking and blocked by features in twelve seven.

A

So this is great I think it's still behind a feature flag too so and is generally available. Now it all get loud that work and should be generally public to everyone in the water community by twelve, eight or school and lots of things. Also, an issue to note you can give thumbs up thumbs, um add a custom reaction and where this comes into play is, if you go to your issue list, you can sort by popularity, which is your thumbs up or thumbs down label. That's great!

A

You can also sort by last updated created mouse on due date label, priority which haven't gotten to that yet manual and wait. This is another view and your issues if you don't use boards, you can also use this kind of issue view and it also supports school called manual serving which, right now a be experiment, is below there's a lower like relative order and priority.

A

Then the first one, but if I were to go over here and move it in above and in terms of priority order and go back to my issue board, you can kind of see it was automatically updated by specially I. Think if I drag that down here and I go back to my list, it see I reordered the priority and then carried across both places. This is a good thing. A bad thing, I think a lot of people get confused by this, especially when you know teams that maybe share labels and have overlapping priority orders.

A

Things could get out kind of quickly. One of the things that we're looking at doing is making it so that, on an issue board, you can manually set the priority order and ignore the global party. So that way like you, whoever is on this issue before managing it can set what the order is, and it will maintain that that's interesting I added my default list, but this just showed up again.

A

Is that because the label is gone, hmm I think so yeah that happens if I click add default list, so I guess I had to back interesting. Why didn't that option show up, though, when I was on my other board, pretty my liver, they were my. They were good.

A

Oh here's, a problem I was in the web. Client I was creating that one I think this is the.

A

Yeah, so here's the board I created for that development. This is one of those wonky things. Well, it worked on the project, I guess I hopped in the project here and it realize it and then I went over the boards and.

B

So for clarification, you can have separate workflow boards at the group and project level. Yes,.

A

You can also duplicate the labels right now, I believe so you have to do here which this is a project level label and then, if I go into now, this issues inside this project I think, if I look here, my labels we have to do doing, but I guess to do is not flowing down, not sure it's worth investigating. um As you can see, yeah it's a little interesting I get lost, sometimes I've trained myself to go and look I write the boards at the group level.

A

Only so usually I will go up here and I. Look like get lab work and I'll go over the side and click boards. That's where the issue boards are the itraq. But yes, you can't have project level issue boards, group level, issue boards and labels that flow downstream, and you can also promote a project label upstream, so we're on web client the project if I go to labels believe this is you can kind of see. This is a group label. This is a project label and- and let's say, I want to what happens.

A

This is interesting experiment if I go into portfolio, one I create a.

A

Doing label- and this may get green, listen color, so I do doing here and then I hop back into my project.

A

We go to labels.

A

This is kind of one of the things that's interesting is you have a doing group label and a doing project label it's the same name. So if I go to my issue, for example, and I want to this is a yeah I say: I have two doing labels now, which I don't know which one is which, let's we need to probably address that rather quickly.

A

So that's not great experience but I wonder if I can, what happens when I promote a label up my project label or promote to group label will make it available for our projects as I get live. Hopefully one is just seeing project labels. The same title will be merged, promote.

A

So now I have just a single group label, so that's one way to clean it up. It looks like which is nice and I. Think if we go back to our portfolio one and look at our labels, yeah we're great. You can also filter by your issues- merger class epics directly. If you want to look at that here, which is kind of nice, all right we're on portfolio one, we have a couple issues that are living technically within a project. We have an issue board that we set up for a basic, workflow and I.

A

Think the other thing we might want to set up is Mausam, which is kind of a time box I'm going to create a new one and we'll call this sprint one and we're gonna say this started ten one day and it's gonna in here and we're gonna, create that milestone and we'll go ahead and create another one for Sprint two. Just because you know that's gonna come up next, it's gonna start next week on Monday and it's gonna be over in Friday. We're gonna create that milestone.

A

So now we have two milestones here and you can create milestones at the project level or at the group level same idea. If you created the group level, it will be available to associate issues across all projects within that group or subgroup, which is a nice way to kind of align everybody behind a common time box or time frame for your delivery cycles. So hopping back over to our issues, and maybe this one we're going to get done in sprint one.

A

So we can identify this two yeah interesting, I guess this is getting inherited from upstream somewhere, but I have no idea, which is which what is the real sprint? One.

B

Yeah I was setting up things for you, so he's gonna speed through that, but we wrong portfolio. It's.

A

B

A

Yeah this, like it's a good use case, though, how it's easy to get overlapped with things and.

B

Then I would like to you know the story I'd like to tell is that, while setting these up both of the group in the project level, you should work with your your peers, inside of your account, to set up a and up a basic plan of how you want to structure things, because you can easily step on each other's toes yep. You can so.

A

Yes hear what Keith said he created these at the top-level group, which is great so I guess, given that we're gonna go back in and how about I delete the ones I create, since those are for you, there will align with the ones at the top level.

A

So if I go to my milestones now, I can believe I don't know if I can delete a milestone. Yes, we can't delete it and then we'll go ahead and delete this one as well. So now in our issues here, we will associate this one as sprint, one, which is great. We have two three four five six cool and then this one will associate to sprint to tackle that next week in sprint.

A

Two, you can also assign things if you were to create a let's say you want to have a portfolio level, let's say board for grooming. We can go ahead and create one for a create new board for sprint. Plane. Call that, and within this board we're going to add some different lists will add, milestone based lists and we'll do I think we're in what sprint to you know that right believe. So you just add them all. We'll call the bat and I think since sprint two is active. This is actually wrong.

A

So if you go ahead, drag these over, it will update the metadata on the issue and assign it to this various print. So if you have an open issue of backlogs.

A

Project you can also from the issue board quickly associate epics and we're gonna call this one for the net new sign up since we're kind of working on that I. Guess, epic, and we don't really know when we're gonna work on it.

A

But mostly we liar like that, and let's say this is a feature because it's gonna implement something or T is what it's called feature story, I guess, and if you want to go ahead and add weight, you can add weight here and we'll call this a five for now, edit that out it's great and, as you can kind of see here, the total weight for all the issues in a given list rolls up into the top.

A

So you can see the total issues, the total weight, which is great and so yeah there's different use case for boards. It's pretty flexible, I know some folks, it get lab use assignee boards, so they can see who's working on what within their teams, which is another helpful use case. Anything else you want to add about boards. At this point, Keenan.

B

If you want to talk about work in progress limit, oh yeah,.

A

Yeah so I think going back to our sprint board. I started playing here. The other thing you do we just want to like, let's say we're on sprint to you right now. We can go ahead and scope this to sprint to and say that so I'm not gonna see any issues that aren't in sprint, 2 or assigned to the sprint.

A

Already, let's go ahead and we're gonna go ahead and start this moving over to workflow in progress, and if we look at this me, click area is kind of monkey know why it won't open anyway, create some more issues. Issue.

A

A

Create another one free will call to search for three.

A

Maybe if we had a fourth one or.

A

You can kind of see right now how the background turned red and we are technically over our working progress on it. The only should have three: we have four if we want to maybe move the fourth back, things are happy again we're within our work in progress limits and again we're over changes, which is great, and the tribute thing about this I guess just from how we need to figure this out is.

A

It is on the board level, but you can't enforce anything at the issue level, because this is a group level board, and this is a project level issue, and so other things can influence this issue outside of it being updated. Via this board, like you, can update it via a commit or a comment on merge requests or via the API there's lots of different ways or from the project itself, and the only thing that knows about work-in-progress limits is this board and so a future?

A

It would be nice if we get to the point where literally you could enforce the fact that nothing else can have the working progress label applied to it. Like case in point, if I open this up and I go to manually, add its in the workflow backlog, I want to say workflow in progress. I can go ahead and do that here and there's no indication on this issue that it's over limit. It.

B

Results, you know there's, so it does show all of the every time you move that issue between lanes on the board. It had. It had a updated item in the Activity Feed on the issue itself. It did but.

A

B

A

So the activity feels really nice. Everything is kind of trapped here in traceable and whenever an issue is updated, you can see like let's say: I had a weight of five here. It's all captured in the system notes which is great, but the I guess the end goal is.

A

If you want to enforce a workflow, you have to prevent this issue from having this label applied to it, because it would violate the word progress limits theoretically right unless, unless everybody like in that I guess that's one of the tricky things to solve conundrums that we need to figure out just because the flexibility we go through the things. It's also made the idea of enforcing things difficult.

A

Other things to note with an issue you can toggle on and off notifications. If you don't receive those, you can lock the issue which will prevent people from commenting ayat so except for project members, and you can also make in.

A

You can also make it confidential, which will turn the turn off and not be describable to anybody who is not a member of the project. So this is really handy, especially in get lab where we have security issues and other things that we don't want to make public until they've been patched. So it's a great way to track that other.

B

A

Yeah yeah time tracking I'm, so the way he said time is via quick actions which there are a ton of quick actions, just pop open this window to show you all them, but from the comment or the description anywhere, there's. Basically a markdown editor. You can use these quick actions. I can shrug. I can add a to-do. I can mark. Something is done to do is done, I can subscribe to the issue. I'd subscribe, close reopen. So the way you set the time tracking is with the estimate, leave estimate.

A

So on an estimate, let's say four days for this woman: it's bail four days and if I go ahead and comment that it's gonna set the time estimate for four days you can see over here it's estimated at four days and then, if I want to record it I think it is. What does it spin yeah, so I go ahead and spend I'd, say I spent 12 hours on this and 23 minutes. I can update the time spent as well and I will show you your time tracking.

A

Here we have a lot of our roadmap to surface time. Reports and time tracking, both upstream to parent epics, as well as in group level, reporting and project level, recording also from within the issue.

A

I can go ahead and I can add this to the epic if I want, which would be on increasing that new signups and the sales for that feature and I can tie it to the epic just from the issue itself, which is great so kind of go up bottom up from issues to epics or from epics and create your issues and find your shoes that way cool.

A

So another thing to highlight here is a way that you can create issues within get Labatt's called service desk on service desk is a way to have a unique email address for each project, and if you are email that email address issues and if you respond to those issues in get lab, it will email the original submitter. So it's way to interact with either internal. It's like an IT Help Desk to people who don't have get lab accounts, but need support, and you wanna do issue management for that.

A

It's also great for attaching this email to forms and form submissions for collecting customer feedback. So since this is already enabled by default, you can actually set up and customize some of things here within your project settings.

A

Let's see in customize display name those sorts things. I know it's coming, also where we can customize the URL or that the mail to address to be something a little bit more palatable and short and memorable, maybe brand based that should be coming in twelve, eight or twelve nine believe. But what this will? Let you do is hop over. You know: gonna meet email.

A

And compose a new email and we'll put in service desk, and you please help.

A

You could also use standard markdown syntax in here, and that will work. So if you want to like use a form and then take the form of contents and apply it to a markdown template before you send the email out, that's another thing to do too there's a way to kind of work around the lack of custom fields and form collection. We think it.

A

We'll see how this works I think if I add.

A

Some quick actions at the bottom of here.

A

And we can call this a T, so we have our labels that are set up now. The end user is probably not going to know how to do this. But again, this is a nice little tip that you can use for using your mail to address, embedding it into a form and then wrapping that inside the message inside of a custom template that you inject the message from the form into before. You actually send it off to the mail to address.

A

So if we go ahead and send this now, it will be sent and a moment I'll get an email back. But while we wait for that, I'm gonna hop back over to the service desk.

A

And it takes just a couple seconds for it to show up- usually oh there it is so we have automatically defaults to confident foolish, which is kind of nice, especially you know when things out of there for some one reason it did not add my bug label I'm, not sure why there seems like it should have, but you can see it did pick up this markdown form in here and if I say you got it.

A

If I might in comment on that, this will send the email notification back to the original submitter with this message in the threat of it. So I don't know if it is here yet, but we can kind of she'll be able to go down and see. Here's the original sir service desk area, I.

B

Think you clicked archived.

A

Sorry, all mail here we go and here's the response that I put inside of gitlab itself- and this is what's- was sent to the end user, who emailed in so it's a great way to do back-and-forth with people who are not good lab users and still support them with formal issue, management and tracking. So.

B

A

B

To that email as the submitter, would it automatically add my response as a comment? Yes,.

A

A

If we go back now should take just a second.

A

There we go so there's a response back, it's supposed to the state lab support, but like we're also looking at how we can improve this, so that it comes from the actual person we're more like identifiable sendee.

A

That way, we can have a better user experience within services itself for managing issues and tracking them back to the original submitter cool. So that's the basic gist of it. The other thing I guess the worth highlighting is now that we have some Mouse and setup. We can go back to our I'm, not Mouse, and we have mouse on an we have some epic set up and go back to our portfolio, one.

A

We can look at the epics and what is a good idea to do once you have some stuff great, is toggle on and go back to setting your inherited dates, and this will automatically set the start and end date based on the children, issues that are associated and when they will be done based on the milestones that are there. So now this is set if we go into our roadmap and we look at what was that was the optimize.

A

The conversion funnel epoch and optimize the conversion funnel epoch is now mapped to the same time boxes that the increase that new science is mapped to what's kind of nice about this is, as you build out more complex dependencies. This will automatically change based on all the children and when things are scheduled, based on how they've been assigned to which milestone and that will all bubble up through your whole epic tree up to the very top level.

A

So you can easily drill down and see like the time ranges when things are going to be done, based on, what's actually been scheduled, so you haven't flexibility of doing both top down playing where you automatically set the dates, which is great. If you want to like track against project progress or you can do the kind of more like we have to get this scope done, it's going to take a certain amount of period of time.

A

I don't know when they'll be done, but based on all the things that have been assigned below it that are associated to it. You will be able to dynamically see that which is pretty nifty so.

B

A

B

My issues and milestones in my epic associations, my roadmap, will be pretty close to a real time estimation where things are yes,.

A

It will pretty.

B

A

It is very cool anything else you think we should cover can about the analytics tab, it's technically not within the purview of plants age, but we can kind of show it lots of different analytics right now. This one is is basically issues created per month and it is interesting but not super interesting. The cooler thing that I think is this insights and I came hop over to another demo. This is the default dashboard and it kind of shows she's creative per month.

A

It she was close per month, looks great per month and another project bit I, guess demo that I had set up actually wrote a custom inside CMO file and that would kind of simulate showing things in a portfolio standpoint and rolling up. So this is like the basic roll up page, where I have issues by you know type and then I can see issues closed by type theoretically and then bugs created by week, and this is all set by a Hamel file.

A

It's in a project that you can specify you gotta create as many custom pages as you want, which is cool, there's some customers that are really digging this they're, just not digging some of the bugginess with it. One of the downsides is that like right now you can see type undefined I guess like if I don't specify the correct labels at the time. I click create on an issue. Then it just shows up as undefined. So like a lot of, like think about use case to service us some of the emails in.

A

We don't know right away. If it's bug or not we're gonna look at it. We're gonna triage it maybe a day later it will always show up as undefined here, because it didn't have labels at the time it was set up, and even though this is filtered by only certain issue types within a specific label which represents kind of like a group, it still shows up as undefined so buggy and there's some customers who really want us to like bring life into this.

A

So I think it'd be cool to get some product management support for this another quality team role, this hand roll this themselves did a great job with it. It just needs a little bit of love to kind of go to the next level, so we.

B

Really we're, as a user of this, where would I see my burnout right? Oh yeah,.

A

Your burnout, drugs, that's interesting.

A

Let's go back up here and we can go to the agile demo. We can go back to the brockton we created and then, if we look at our where we created our milestones in our top level, we can go into our current sprint and we can see a burn down chart. So right now we just opened a bunch of issues halfway through spraying or mostly way through the sprint. So you can kinda see like def in scope creep. You also can see nice things here, and this is great actually like it on.

A

The group level milestones the project the DSU belongs to and as well as like issues that have been assigned, and you can also things like merge request when they exists participants and then a breakdown of labels, you can specify the burndown chart by issue weight or by issues and we're working on improving this to also included burn down chart, so that will take up the other half of this.

A

So that way you can see a better reflection of like scope added throughout the course of this rant and so just removed or completed so that'll be good. Next improvement there, but that's where you look at your burn down, chart.

A

Yeah I think that's that kind of covers everything. I think for the most part, on the other things within the plan stage. That are of less note, is the notification settings which we would also love to work on too. So a big thing that I think if we can find the resources and time we'd be overhauling the taboos for personal management, but then also the the notifications.

A

And so, if you go in your profile, you go to settings and then you go down to the vacations I believe this technically falls within the plans stage as well, and it's like how people are notified and you can control global settings as you can see, I have mine disabled, but you can also specify different settings for each group if you want and specify custom ones, if you want to do custom ones and I think for the most part, this is not bad. It would be good if we worked on improving delivery.

A

So if you know you get it, trains actually mow for every single notification and I think some folks would like to have like daily roll ups and things so they're not like bombard all the time but yeah. This is a. This is a pretty big undertaking to fix all these things. It would be like a good three or four releases in them itself to properly handle notifications. I. Think that way everybody wishes they would so I would love to get to that I think we will at some point yeah.

B

Oh that looks great yeah.

A

Yeah does all right, I guess this ends our demo module.

B

A

Cool yeah thanks thanks.

A