GitLab Plan Stage, 4 Feb 2020

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: Plan | FY21Q1 OKR - Competitor Walkthrough Part Deux

Description

No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).

A

A

Cool alright can Gabe here playing PM's we're going to do another demo today, this time we're going to walk through JIRA software, classic projects, I think before we do that, there's one thing we'll highlight I think we missed it yesterday. There is a your work section up here in the top and it looks like it has all the stuff that you viewed stuff.

A

That's assigned you and things that you starred and you can make this your new to your home page, which I just did just great, we'll see how this evolves as we setup our next project and how it gets populated. Another thing to highlight too about the projects area overviews. You can see your different types.

A

You can also filter by types where you have your service desk projects, which would be tied a service desk, and then you have your core projects, which is the business projects and I think this is Jared cords built for HR recruitment, project management, more, it's the non software team focused projects and each of the service desk and core are separate JIRA products.

A

So we're not going to evaluate them as part of this, but that's how kind of all their different products rolled into one sort of interface, which is JIRA software cool. Let's go ahead and create a new project and we're gonna call this one. The classic project see this is controlling consistent across many teams is why you would pick this full feature: set advanced configuration, set up and maintained by admin, admin so has locked down, but who can do what versus the next gen, which we did yesterday where anyone could set up and maintain this?

A

There is no roadmap on classic so I'm interested to understand why they made a decision. Maybe we can figure out. It is compatible with portfolio for JIRA, which I guess next-gen is not card layout custom asian, which can't do it they just update. This did anyways there's a ton of stuff that you can't do a next-gen. You can do a classic, which is what we're gonna explore.

A

We'll just call this a classic and share settings with an existing project. We do that. So it looks like if there's another project, that's set up. You can go ahead and start from there we're going to start from scratch. Just see how this goes. It's only a classic project. All right, yeah yeah got looking for easy setup and reimagine features. We've reimagined, it's awesome, I think we're looking for classic. We can do bug tracking scrum Kanban.

A

These two options were what was in next-gen bug tracking was not do you have a preference on this, or we can also do a business setup. We could do a project management process, control document approval, recruiting content management, lead, tracking or procurement. What do you want to be Canyon? You can pick.

B

Project management all.

A

A

And we have our classic view that looks oddly similar to you. We looked at yesterday, although there's less buttons on this table or this board it's the first thing they want me to do here with the flashing orange is creating a new issue. So I'll go. Do that our first issue, I was so much I could do slack emojis in title. So I'll be brief.

A

So we've gotten that you have in progress done I, don't know how to set this board up, there's no way to configure it or change lanes.

A

So we'll just poke around the different tabs till we figure it out. Let's see activity, that's two issues. This one is in to do I.

A

Guess issues statistics is right. There we've got some more issues over here. I can wow that's interesting. A gear icon for refreshing cool, got that issues and filters. So this looks like the a search view that we saw yesterday. It's just a little bit different reported by me created huh key.

A

Last few, that's just a quick way to go through all of your issues. There's an advanced search here.

A

The resolution status, which is interesting.

B

Cool so yeah yeah that one you can that lets you differentiate between different types of closed statuses right so you can have like close done. Closed, won't, do close duplicate, that's what that represents. I! Think yep thanks. It's.

A

A

Think this is the same same editor that was in the other JIRA next-gen, so we won't go there. We have basic fields as well time tracking components, I'm, not sure what that is we'll get into it, and then we can go ahead and start so. I can change my workflow right here. Something I really wish we hadn't get laughs is just like set of labels. You just can drop this down, go to different workflow step, convert this to sub tasks and go ahead and log my work just time tracking.

A

This is all stuff that we kind of demo guess today. So let's go back to the project. Let's look at some reports and I. Think.

B

We also looked at a lot of these reports yesterday. Well so the difference. One of the differences here, though, is that there's 20-plus reports available for classic, but when we only had the four basic reports for a sprint based project and in a new version, um and that's one of the items in the comparison when you say, although they did have a lot more gadgets than they said pretty.

A

B

Yeah and so I think that's the I think one of the one of things to note is they might be. It looks like they might be moving a lot of these reports to that dashboarding view and keeping this sprint specific ones, or at least you know, iteration specific one's yeah word stabia.

A

Do you see single-level group by report groups by particular field, so yeah we're pretty extensible reporting? It looks like we can come back this. We want to explore anything once we create few more issues like that advocate report. That's a hint! That's a handy one yeah. I.

A

Don't want to go here.

A

So this is the setting. So, let's see if we can change our board here.

B

It's I think, it's in down in workflows, alright, cuz it down. Oddly I.

A

Notice this, like you, can't change your project type once it's created, so that's bummer, major people here. So by that you can straight forward rolled. You can be an administrator of this summary.

A

Alright, so here's where we get into some and versions of creative version, it's interesting. These are all in project settings like creating a version in project settings, 1.0, 0.0,.

A

Ga baby and we'll release this default date is 2018. I ain't. Don't know why I don't see.

C

Here start this: one January 1 will release it from our Gianna March.

A

Alright, so this is similar to the view we had yesterday.

A

Back to the summary, yes, this will show all the lists of versions, but it's not interactive. What is a component can be broken down. A component CG database user interface issues can then be categorize against different components.

A

Some of our customers use this and they also say this is one of the most mules and JIRA music I've used abused. Yes, we're like it's four different functional areas, but people are using it for all sorts of other organizational slices. If that makes sense,.

C

A

We'll create one for back here component lead. Can you be the component lead for the backend sure, like all.

B

A

So I guess you can create a leave for this component, which is a component, a team.

C

A

Don't know what do you think.

B

I'm trying to get in there so I can poke around giggles right, quick JIRA component.

A

Subsections of a project: what exactly is it.

A

So G R components are sub sections of a project they're used to group issues within projects into smaller parts. We take a look at managing the opponents and defining cons for more information.

A

The stack, OS, GI components and services component tends to be an object whose life cycles managed usually by a component framework such as declare services component, may have any of the following features in combination or alone.

A

Started stopped this we consider active component, so that is also an informal term. A component that doesn't need to be started or stopped is called passive, publish itself alone and they bind to or consume so here simply ways the categories work in a project cool, okay. So it's sort of like what we do. You know where we can create another one for UX I, guess you could use it for, like funk, shirt, features to or something like that.

A

Okay, so we got some components: let's go back to settings.

C

Summary, let's see.

A

Cool rolls Legere enables you to allocate particular people. The specific roles are fragra rolls are used when defining other settings. You project roles.

A

Can you customize the roles.

A

We'll go back to that if we find it somewhere, permissions allow you to control, you can access your project work on issues default permission scheme, which is what trouble use of permissions helper to discover why user does not have rights to certain permissions cool.

C

That's interesting.

A

So it's fairly extensible.

B

Yeah I think you have since you're the admin I think we looks like when we have tasks and subtasks as issue types on this project, and that might just be the defaults because we pick the project management. One.

A

All right, so here are all the different roles that we actually have uncovered this you can grant permission to, like, let's say, administer projects to a project role, an application process, a group user custom field, value service, desk customer portal, access reporter current, so any single users, your Project, Lead or group custom value field.

A

So you can pretty much do whatever you want.

A

And now I don't took that popped me into my overall look like in since admin. You see all that stuff.

A

A

Notifications that again, there are schemes for these things. It's like for all I think within this everything kind of has a basic scheme or schema, and then those get you define. Those looks like in the instance, admin area which is here so I can look at all the projects to your settings default.

A

So, where I go create like a new.

A

Locations- maybe in here Oh male patient over.

A

That's kind of funny like find out type their name to find out why they can't get notifications.

C

A

Gets so complicated.

B

Yeah I mean so far, it seems like the next-gen. Build is meant to consolidate and simplify things. Yes,.

A

I think so well, looking notifications later screens where here's workflows, let's look at.

A

A

Ok, so here we go, this is a this is a I guess. Another key difference, use like any of this stuff that you want to change, has to be changes. The admin level. So, like all of your schemes, you can't really edit any of this double you. Can you just have to go somewhere else to do that so I guess I can in here they'll edit the issue layout.

A

A

Okay, so I can I, can kind of customize I guess what fuels don't want to show up on my issue at the project level workflows see here at a workflow.

A

Can't really edit these here we'll go, look at the workflow builder in a little bit.

A

How can I just one directly, so this kicks me into JIRA admin.

C

As well yeah, so we'll go look through the admin stuff for a little bit. Fancy fields.

A

Okay effect, burn effects, versions is on two screens, it's on the default screen and the Kanban bug screen the assignee is on so this is where you can kind of see your default field configuration.

A

Create issue that issue it so these are your screen. Schemes probably like keep different views and they apply to these issue types. So that's how that maps together I.

C

Have the order fields new set for elevation types of projects like issues have consistently across project locations.

A

See this is what I'm scared of like people want custom fields and get loud, but and I know why? But this is what ends up what you end up with yeah like.

A

Alright, let's go back over here, so we like diversions already the grazing component I, don't know how do you I.

B

Just changes the the things on a board like.

A

So I think if you go to the board and.

B

Well, wherever you can configure the board I, don't.

A

Know where that is but I can put in progress. Oh wait now looks like.

B

Someone is in the middle of editing, this workflow, so I think the board I'm trying to remember it's been a while since I've built these out durab but I think board pulls directly from your workflow set up, so that diagram you had with like the open and progress clothes and the directional lines. I think that ends up defining your board structure, all right. Let's.

A

Let's explore okay, we're now in the JIRA administration's areas. The things that we do here relate to all projects so, like I, think the basic gist is you create schemes? Projects can then adopt schemes for different objects, whether it's custom fields, we're closed so this here we see issue types we can edit this bug if we want to change a universal description and change the avatar or the icon, I, don't know why they call us an avatar for a non person on personal project.

A

Looking at his schemes, let's create one I think we created one yesterday is test schema, let's go ahead and associate this not to our classic demo.

A

So if we now see here and go back open another tab, let's go look at our projects classic demo and we create a new issue. We should.

A

Be able to change this type to yeah now we have bugs here. We have stories, tasks, epic, so these are all the issue, types that were shown up ahead and then all these things are hidden based on the label or the custom field configuration not to show above the fold unless there have a valid value, so cool. That's how projects classic projects inherit issue type schemes.

B

A

B

A

Right, maybe I missed that. So that's what what is interesting is like a creative project, but it created a new issue type scheme.

A

The associate is where I said: I wanted the classic demo project to use this scheme, so I'm, multiple schemas to the same writer, no I, don't think so, because if I sign it associate it back to this one, it will see issue type migration for you steps one of four.

A

This was also interested in seeing how they handled some issues have issue types that are no longer applicable. You'll need to move these issues to another issue. Type you'll need to move each issue type for each project need to move each issue type for each project, individual all right. So this one class right change, colors, if you don't do anything in a hover, select a new issue, type for issues with current story, project issue, type I,.

A

Guess you can't make a sub task type, so we're going to migrate all of our story, issues in their classic demo back to this type thing, and then I'll field values will retain the same C way. This is this foster routine original field values where the original value is valid with target. This can be achieved by checking the checkbox associates require field, so.

B

I think it's because we don't have any custom fields set up for the individual flows, probably yep.

A

Well they'd say at least they were thoughtful and they let us do the little migration.

A

You talked about that with like milestone types and we're gonna simplify for now, but if we ever introduced that- and you transfer a issue from one group sub project to another group, so project that doesn't have the same- let's say labels or whatever configured right now, we're just making assumptions about things and duplicating labels or just removing them. But it would be nice if we let people like control that through migration or something all right.

A

So now that we've migrated that back to this, so I think if we go back here and just associate it, we don't have to do migration because there are no fields.

A

So you can go back and forth and I think this is where issue types kind of look. That I think you can even add translation for this I'm guessing name the United States just go back.

A

So you are in charge of your own translations I'm, assuming wait.

B

Hold on you know, go back to that. Is that, where you can, maybe is this like a this allows you to well I can't read it. If you do that. Sorry.

B

So this override translations that may exist for the food constraint and language resource ball, I, wonder if people.

A

A

If people use this to hack the you for like the fields that they can't change themselves, I was.

B

Gonna, ask actually like is it? Could you use this to customize like in calling you could set bugs to be default or defects? If you want yeah.

A

I guess you could do this for English, let's see what happens, but I don't know if you I think if you look inside of the settings, see your issues issue types you can just change the name of it. So we can change this from bug defect. Oh you're,.

B

A

C

A

And I, like this I like being able to real able the UI based on like what you call something like it's a big thing for teams like.

B

Blue team's operating off different frameworks- or you know, you've acquired somebody and they use something you don't want to completely disrupt. It are transitioning from one to a little another, and you want to make it.

A

That's right and right now, I think it's only. It only happens at the JIRA classic at the admin level, but I think with JIRA next-gen. You can change the.

A

Field names on a per project basis. So if we look at this one and we go into our project, settings and issue types.

C

Look at bug we just edit. Oh no, oh yeah! There you go defect so.

A

It's on a per project basis. I can rename this it's nice nope.

A

All right, subtasks, I, don't add a sub task issue type. Here we get into.

A

Sub e call me sub e.

B

Translate manage well now we have two types of subtests yeah.

A

So you can create, as.

B

A

You want of that.

B

A

Then here we in the workflows- let's add one- you want to build one from scratch: yeah all right, I also found you can import them from the marketplace. So looks like people are air focus prioritize. What to do and easy to use scoring system make better decisions, visualize priorities, so this is kind of cool to get crowd-sourced yep story close.

C

C

Back here we'll come back we're trying to workflows a.

C

B

Mashup name yeah, you like that what like it's mattered, gabion gaben on hey I,.

A

Like yay baby, alright, so we have something in here called open. This is what happens. I can drag this thing around school, great.

B

I think that's just start like start point, so you create a issue and it goes into the open category. Yeah.

A

So the circle, but I can click on the line. Options, properties, nice so.

B

A

Actually, just fine.

B

Yeah, you can define transition properties. Why did I get kicked out in the different screen? Look.

A

What is a transition property? Oh I, don't remember.

D

Been a while, since I've had to do this.

D

D

B

A

All right cool- um let's go back to that! So now! Yes,.

A

B

What the so so that they're, never screens allows you to customize the individual like view you get when you interact with an issue, so I think if we go like, if you hit yeah click default screen.

A

Post function creates this this issue originally. What would it create an originally.

A

Reindex an issue to keep indexes in sync with the database.

A

Wasn't it happen automatically fire an issue create event that can be processed by listeners, looks like there's.

B

Editable items over like there's an edit option: yeah like what oh, so this is, if you have like your like, have a bit listeners that you need to what you can actually yeah. You have been since bushing yeah.

A

It's the work, its work, it's like I, just from wondering, like these things all seem like they're.

B

A

Only users with create issues permission can execute this transition.

A

So it looks like you can lock this down just transition down to some sort of permission, just cool.

A

I'm kind of lost a little bit, though, because we have our start create open right. You properties.

A

Canada, if we built or closed in to get loud, please don't ever do this. Don't ever do this either yeah.

C

That's support each other now.

A

Let's go back and some foetus and we have our post function, so this is what happens after it gets fired. I'm sure that validators make sure that it's a valid operation that like this is permissions thing well.

B

And I'm and you can set like make sure these fields have been blue.

A

Yeah, let's see if we can do that, except something that people have been asking for, we get lab. Is it like in custom fields required custom fields yeah, so it's at a validator.

A

Let's say the date compare date window compared to date. Fields I think time span in days, so.

B

I set third one yeah field required field required. Add.

B

Then you can choose one field.

A

Points where's points or are we gonna say? What do we want to say a.

C

Description is required field, a.

B

I would say a label there's a label option in there. I saw do you have to put some label in there so that it gets yeah a.

D

Reporter or request site, what's a request type guess we'll find out there.

B

You go still very points, negative, a.

A

Story point estimated story points maybe like before and after it might be you what about team.

A

And the weird thing times: men, okay, but some so you can create a custom error message for each of these so like. If we want to do one required field per and then we could customize their message so invalid required.

C

A

Labels story points reporter for team.

A

Alright cool, so we got that in there. Let's go back to our gate, workflow I guess I got kicked out of the like pretty editor and let's.

B

A

Gram under what there's a tab- oh yeah text diagram got it. Thank you for that. That was helpful. Open, allow all status transitions to this one. How do we add a status? What's the next one backlog, I, don't.

B

Know hit the drop-down zoom again building closed done.

A

In progress, it's good it to do, do allow all statuses to transition to this one yep, and we don't want to like any of them. Do we.

C

B

You connect it, you can on the diagram, you can click on one of the dots and connect it.

A

New transition says from open to SAS to do name.

B

Well, it should be a you know, open to to do right because they were naming the transition yeah.

A

Just default screen.

A

C

A

What's uh what do we want to have after this.

B

William progress they're doing no progress.

A

And what other should we have in progress? Well, I'm, gonna done done or.

B

A

I think, let's look, it done cuz and then closed cuz. There's teams that I've talked to you who don't use closed, is done because they hand off the issue to someone else, and so they can never use like burned ads. You can get lot because of that. You know so like we're. Gonna have to figure out itself for this too. So now, let me like.

C

Alright, so to do.

A

Can then issue go from yeah you can have or like we're options open to closed yeah I'm. Sure, probably, do that and then say closed won't. Do.

A

To do in progress.

C

A

A

Reviewed, we can say the transition is reviewed, maybe.

A

And then we're gonna add one back up here to closed, say.

C

Completed that.

A

You can say, maybe bear fight or something I, don't know.

A

Alright cool, so should you ever be able to go from him progress back to to do.

B

Yeah some people put a reopen option in there, but we're.

A

About from in progress done to in progress.

B

Yeah I mean, if you think, if it gets bounced from reviewed, you could argue it goes back to to do something get pulled by the next person or you go back in progress because it's a high priority I mean I. Think it comes down to your team workflow, whichever one you prefer.

A

A

So this is pretty cool like it seems really complex, yeah or tough, but also I, guess not super complex in one sense, like I, like the simplicity of like vigilance and being able to like set the workflow automations, which I think is something that's pretty powerful, it just seems like it would be hard to like. If everybody has their own thing, it would be hard to figure this out. You know.

B

Right but that's the whole reason that this is locked as an administrative action right is that the ad that's the acceptable workflows means can choose which ones work for them alright. So if this is here, how do we.

A

Turn this active, like you, do we have to save anything or the.

B

Scroll down is there anything at the bottom like saver, it might just be an active because it's not assigned in all right. Well, let's so expand inactive! That's like a carrot, yeah ooh, all right! So there's, okay, all right! So holy sign! This we're close schemes.

C

Big active classic demo.

B

So yeah, where did you? Where did we're able to assign it to the demo? That's the might be a project level setting.

A

All right, let's go look at the project.

B

Project setting.

B

Yep and so then, on the switch scheme, maybe.

A

I, don't think we define a scheme I think we just define a new workflow, okay she's from existing okay. Here it is alright, it's the next sign to issue type. So you get, you can have different workflows for different issue types, which is make sense.

C

Why are you shooting arrows what's wrong with this or.

B

Well, you gotta, you got a hold on there for Ben, for.

A

Workflow to remain active in your project, it must have at least one issue type assigned to it. If you assign this issue type to this workflow, you will be deactivating another workflow and we're moving it from this project. Okay, so I'm overwriting an existing workflow cool. So now that that's there, let's see if we go back to the board now what you're gonna publish it up top oh yeah, there I'm close changement polish.

A

Current Steph's each issue needs to be changed. Those kepada with any workflows, oh migration,.

B

There's only two issues: mm-hmm.

C

A

Guess, there's no way around migrating, though, if you like, update something in the middle of right with a bunch of other things using different mm-hmm.

B

And, depending on how large your your list of things are, that can take quite a long time. Yeah all.

A

Right, let's check us out there, you go sweet in progress, closed done.

B

File is it if you click and drag like a issue over if keep going, see how you you are not able to drop it in there because of the workflow. We don't yeah.

B

Yeah drop it and drop it to in progress, and then you get yeah so then you get the opportunity to update field. So this is the screens stuff that was talking about. So you can actually define a set of parameters that need to be inputted into an issue before it can transition states. So if you think about you have, if you have like a review column, you can send.

C

B

You know that it's assigned to you know somebody or you know whatever here, yeah, that.

A

Makes all sense and then click start I.

A

Can't move it in the close because to do.

A

So, yes, that makes sense, but here we're back to the same problem and I guess the way that they structured things is they put their, but their scheme for the workflows in the admin level project can say we're gonna adopt the scheme like as a project, but that's like you can get lap. There's projects that lots of teams work in, so the team would all have to agree to a workflow.

A

Maybe like that's the constraint that we just have to accept, but it also feels like not ideal. I, don't know, yep, alright, anything else that you want to see. I think that was like the big thing. No.

B

That's the big stuff for them. I've actually got another color gonna hop on so alright.

A

Thank you, and thanks for joining us for our wonderful walkthrough of JIRA, classic that.