Transcript for:
Lecture on Jira and Agile Methodology

subscribe and click the bell icon to turn on notifications in this video we'll take a couple minutes to understand exactly what jira is and what it's used for simply put jira is a project management and issue tracking tool as a fun little fact the name jira actually comes from gojira the japanese name for godzilla now there are a lot of different ways that companies organize their projects waterfall six sigma prince2 and so on some of these methodologies or ways of organizing and getting work done are similar to each other some of them are quite different from each other overall the methodology that a company uses to organize and get work done can determine the tool that they use to organize all of that when you're using jira it will assume that your team is using the agile methodology now i've worked with teams who are using jira and they're not using the agile methodology there are apps and plugins that you can get in order to have jira organize things in a different way but by default without any extended capabilities jira itself is an agile tool this course is not really designed to be a deep dive into agile methodology but there are a lot of agile terms and concepts that will come across inside of jira so that's why it's important to take the time to understand some of those core agile terms and concepts now if you're already familiar with agile then great you can skip over the next few videos but if you're new to agile or if you just want a quick refresher then i'll see you in our next video where we'll get a crash course on the basics of agile methodology in this video we'll get an overview of agile methodology now before we begin i want to point out that this is not going to be an in-depth look at agile there are tons of great courses and workshops out there that do take a deep dive into agile methodology but if we were to try to do that in this course there wouldn't be any time left over for jira as we learned in an earlier video though before we can understand how jira works there are some things about how agile works that we need to understand first because jira just assumes that we already know them so that's the purpose of this video to give a crash course on agile in a single video for our purposes today the term agile refers to a methodology that software development teams around the world use to get stuff done it's a methodology that promotes adaptive planning evolutionary development early delivery continuous improvement and encourages rapid and flexible response to change now jira certainly is not the only agile tool out there there's quite a few of them in fact i've worked with teams that prefer to use a simple whiteboard on the wall in the office with something like post-it notes instead of using a digital tool at all but of course physical whiteboards won't work for everyone there is no right or wrong tool when it comes to agile it's more about what's right for your team or your organization with that in mind jira is something that some of the world's largest companies and organizations are using for their agile workflows because for a lot of teams it is a lot easier to see things using a digital tool like jira to organize our work using agile methodology one of the most important tools that we'll use is an agile board and that begs the question what is an agile board on an agile board will have different columns in agile sometimes they're called lanes in jira they're called columns think of these as the steps you need to get a project done in the simplest project there's going to be at least three columns to do or not started so the project hasn't even been started yet in progress it's currently being worked on and done it's complete of course boards can get even more complex than that in ninjira you can customize it to add in whatever sort of columns that you want but this is just a simple example of an agile board now underneath agile there are two primary ways to organize projects there are different workflows for how your team tackles those projects and the process that they use to get them done one is called scrum and the other is kanban the differences between these could be an entire course in and of itself but for our purposes today there's really one key difference to keep in mind and that difference has to do with something called a sprint and again that begs the question you can start to see why some of these concepts that are we're going to see inside of jira doesn't really explain them so what is a sprint well a sprint is a predetermined amount of time where teams determine what work is going to get done in that time this might be easier let's walk through an example of this just to explain so let's say our team has decided we're going to work with a two-week sprint so what that means every two weeks our team is going to hold a sprint meeting in that sprint meeting might look something like this start by discussing the last sprint a lot of teams that i work with they prefer to go around each individual team member and go around and say what went well for you in the last sprint what didn't go well for you in the last sprint are there any roadblocks that you came across or things that we can try to work better this goes back to that iterative and continuous improvement what can we do better in the next sprint and then as a team discuss and agree on the work and again usually teams that i've worked with they'll go around individually each team member discuss and agree the work that's going to be completed in the next sprint what's the highest priority thing to do in the next two weeks and then day-to-day workflow will be taking those projects so let's say these are the three things that i need to get done in the next sprint and again if there's a priority level to these then of course that would be something that will be discussed in the sprint meeting if there's not then it'll be up to me to determine which ones of these i need to get done we just know that we need to get those these three things done in the next two weeks so the process for this is to take a single ticket and drag it all the way from left to right before you bring another one on you don't want to have multiple things in progress if you can help it you take one all the way over to completion until they're all done then after another two weeks you're gonna hold another sprint meeting and in that sprint meeting just like the last one it's going to go around and say what went well were you able to get all the tickets across the board if not what what sort of roadblocks did you come across that kept you from being able to complete all of those things that we had said needed to get done what can we do better to make sure that we're able to hit those in in the future or is there better communication between teams and as a team leader it's really helpful to hear some of these roadblocks that your team is having to be able to fix those so that more work can get done and then again discuss and agree the work is going to be complete in the next sprint and keep going now with that said not every team works best with these blocks of time for their project with these sprints sometimes it might be better for your team to work on projects on an ongoing basis and that is where kanban comes into play so in a kanban workflow the board's gonna may look very similar but the workflow is going to be different where you take your ticket and you drag it over again you're still going to try to get that all the way to completion if you can but as you're working on things new issues new tickets may be added to the board at any given time because with kanban it's more of an ongoing thing you're working on the projects on an ongoing basis okay so to recap we have the agile methodology that's made up of two primary ways to organize and get in the process for getting our projects completed one is scrum which has a sprint where your team will sit down and figure out all the projects that your team needs to get done in that predetermined amount of time then there's kanban where there aren't sprints but your team works on projects on an ongoing basis and as i mentioned at the beginning of this video there's a ton more depth that we could go into when it comes to agile but we're ready now to move on to some of the key agile terms that we'll find inside of jira and we'll learn more about those in our next video in this video we'll look at a couple of agile terms that will come across a lot in jira stories and epics so this is a screenshot of what it looks like when we create a new issue in jira and this screenshot right here is one of the most common reasons why i get this question from folks who are new to jira why does this say story what this is referring to is a concept inside of agile methodology called user stories so a user story has a formula that goes something like this as a blank type of user i want blank some sort of goal so that blank some sort of reason here's an example as a web developer i want to be able to add users to jira so that my co-workers can report bugs or another example would be as a driver i want my car's dashboard to be voice activated so that i can get directions safely while driving or as a cashier i want to have the total calculated for me so that i can give the correct change back to the customer these are just examples not all user stories have to be done exactly like that but you can see the wide variety here kind of using that same formula and generally speaking user stories and agile are how developers around the world break up their work you'll notice that there's no technology mentioned it's done this way specifically to leave all the technical stuff out of it that doesn't matter the person driving the car here just wants to be able to get directions safely while they're driving it doesn't they don't care how you get the gps to be voice activated they just want it to work as a developer figuring out the technical stuff to achieve that goal is your job and that brings us to epics so probably the easiest way to think of epics is like a big massive well epic sized story not every story needs to live inside an epic but if you have something especially if you're using scrum or you're working with sprints like the example in our last video where we have a two-week sprint if we're working on something that's going to take longer than two weeks to get done then that's going to be an epic and we want to break that down into smaller projects essentially into smaller user stories that can be tracked in the epic so the hierarchy can look something like this where you have multiple stories all linked to that epic so here's an example let's say the epic is the core functionality for note-taking apps say that we're building probably not going to be able to get that done in a single sprint but here are a few stories that we may be able to get done in a single sprint so we can work on one of those and then the next print we can work on another and we can start to see as we track the epic have those stories linked to it being able to track the overall progress in the epic is a really great way of being able to break down big projects big epic projects into smaller ones to get them done okay so to recap when you see stories in jira it's referring to user stories and epics in jira contain multiple user stories or other issue types as well but we'll get to that later on in this course oh and i should probably mention if you're using jira for more than your dev team stories don't really have to be written out that way every time because jira is created as a dev tool stories are basically the default method of organizing your projects inside of jira now i've worked with marketing teams and graphics teams that all use jira software and they just use stories as whatever project they need to get done in their sprints but that probably raises another question because user stories and epics sure sound a lot like the projects that you need to get done at work and i've even mentioned that you know they're the projects you need to get done and they are but jira also has projects too so what are those because that's a different thing that's the exactly the sort of thing that can make jira so confusing when you first jump into it so now that we're familiar with what stories and epics are let's clarify some jira terminology by moving on to our next video where we'll learn about some jira terms we need to know in this video we'll look at a couple more terms we'll see in jira issues and projects now at first these terms seem very straightforward we all know what issues are and we all know what projects are but what does jira mean when it's using these terms because it might not be what you think let's start with issues issues are the heart of what you'll be tracking in jira issues are containers for fields and fields hold all of your data so things like the description the summary who it's assigned to a due date attachments comments all of those things are fields on issues one of my favorite ways to explain issues is to think of them like post-it notes the note itself is really just an empty container you can put any sort of information that you want on it you can even color coordinate your notes to help organize that information better just like inside of jira you can have different issue types now you can also have custom issue types but it does come with some pre-installed like stories and epics like we learned about in the last video maybe on the story issue type you want to have the summary description a due date maybe on the bug issue type you also want to have the os or the operating system so it's easier to know where that bug took place so it can be fixed easier all of this is customizable of course it kind of depends on what sort of data you need to track but you can start to get a sense for what jira means when it's talking about issues and how you can have different fields on different issues and that brings us to projects now as i mentioned earlier in this course projects in jira probably aren't really what you think of when you think of a project by that what i mean is when you start a new project at work that does not necessarily mean you're going to start a new project in jira to track it so let's go back to our example of of the post-it notes here we have these different projects all of the issues in the top row are in the web dev project all of the issues in the middle row are in the marketing project all issues in the bottom row are in the customer service project those issues actually live inside of the project and in the project settings is where you can tell jira what types of issues will live in there right and of course as we learn the issues contain the data and contain different types of fields so let's say in the web dev project we want to be able to have bugs so we can track those in there but the marketing project doesn't need bugs so we're going to hide that from them we're not even going to show them bugs because they don't need to see that you can start to get a sense for how you can customize this to fit your organization's needs so they can see the information they can track the information that they need and anything else that just would end up being clutter and hinder productivity they don't even need to see okay so to recap as we learned issues are things like stories epics bugs those are types of issues in jira and of course you can create your own custom issue types as well if you don't want to or if you want to add to the ones that are the built-in pre-built ones that come with jira and issues hold the fields that contain your data now projects are where the issues live inside of jira and you're not necessarily going to be creating a bunch of projects all the time okay so now that we have a good understanding of some key concepts let's actually hop into jira so we'll do that in the next video in this video we'll start getting familiar with jira by looking at its interface now when you first log in by default jira will send you to this area called your work right now you can see there's not really a lot here because we haven't done a lot of work in jira yet but as we continue throughout this course we'll see things like the recent projects that we visit will show up here items that we've worked on issues that we've worked on issues that we viewed or things that we've viewed here issues that are assigned to us or any items that we've starred or favorited bookmarks same same sort of concept but for now let's get an understanding what we're looking at here and start by moving from the top up at the top left hand side so this is the app switcher and in here we can switch between the different atlassian products that we have so you can see if we had confluence which is atlassian's wiki tool for documentation knowledge base things like that if we had that then we would see that actually right here or we could start a trial if we wanted to of course the key thing to keep in mind here is starting the trial or actually subscribing to this since i'm using jira software on cloud that would be another subscription so in order to do that we would actually have to have administrative permissions which means access to the billing information as well to be able to set that up or down here at the bottom we can actually if we have again if we have administrative permissions we can customize this so you may see some different things uh just adding in different links i've worked with teams that add links to a different intranet or specific documentation website things like that just a quick way to link that and being able to see that up here very very quickly directly inside of jira next to that we have the jira logo here depending on your organization this may be your company's logo the jira administrator has the ability to customize this but by default when you click on this it's going to take you right back to your work where we were when we first logged in so at any point if you get lost in jira you can click on the logo up here and that will take you back home after that again we have your work but here we have quick access in the menu to some of the things that we would see on this page but as we're working in jira sometimes it's faster to not have to navigate to this page fully so we can see the recent things that we viewed you can see some recent dashboards or filters that we've viewed we can go to the your work page it's probably faster just to click on the link up here as well as being able to see recent boards that we've looked at and don't worry we're going to look at agile boards and these boards later on just know that this is where you can access a lot of the recent things that you've looked at and then moving along a lot of these just start to make sense as we're going through this course because we'll be looking at what the projects and filters and dashboards are i know we got a sense for the concept of projects previously but we'll actually see them working inside of jira so it'll start to make more sense but for now just know that this is where you're going to access all of those things so you can see i have a project that i've starred here and actually we can come in and if we remove it from the star then we'll see this update let me go ahead and refresh and we can see it's no longer starred it's recent so as we view more projects this one will eventually get kicked off this list in the menu or we could come in and we can star that to make sure that it is always there in this menu as well as of course as you can imagine finding it under all of our start items on the your work page next to the projects we have filters now essentially in a nutshell filters are saved searches and like projects you can star your favorite filters if you want to to make sure you can see them up here for quick access you can view all the filters that you have or you can start building a new one through advanced search and again we'll look at that in more depth later on in this course next to the filter we have dashboards so a dashboard is essentially a quick way to access things that we're working on or build charts things like that but one of the big differences between this dashboard and the your work section is your work is just focused on you the user that is currently logged in a dashboard can be customized you can add in different gadgets different uh reports different i mean you know pie charts things like that and then share them across different users multiple teams can have the same same dashboard so everybody sees the bugs as they come in things like that as opposed to everybody going to their own your work page which is going to change as you know different users are seeing different things so that's just one thing to keep in mind one thing i would like to point out with this is depending on your version of jira if you're using an older version of jira then the dashboards are the default place that you go to when you log in the your work section is relatively new in the last year or so around 2020 i believe is when they started to migrate over to the your work section being the default place where you where you log in next the dashboards we have people so this is where you can find other people in your organization you can start a team we'll look at this later on in this course but it's just a place where you can get a collection of people together to work on on things and being able to see what other people are working on very quickly and then of course we have the apps and mentioned this in the last section the atlassian marketplace where there's a lot of functionality that you can add onto jira throughout this course i will not be using any of these apps or add-ons this course is specifically designed that way so i won't be using those extra third-party things that you won't have access to without paying but you can explore the marketplace and you can find new apps in here moving right along we can click on the create button to create an issue and don't worry we'll be looking at this screen and we'll be using this quite a bit throughout this course just know that's where you can create an issue here and then up at the top right hand side we have search so searching for issues or boards or things in our jira installation we can search for those here i do want to point out that we can get to the advanced search which is the where we can go to create our filters so again under filters you can see the advanced easy shirts going to the same place just another way to get there or we can see all of the issues in our jira installation all of our boards projects filters or people one thing i do want to point out here has to do with the permission levels so going to all the issues if you are a jira administrator you're going to be able to see everything if you're not a jira administrator you're going to be able to see all of the issues you have access to so that might be a specific project but you might have access to the web dev project but not the marketing project for example that is going to be set up those permissions are set up by your jira administrator and then over here we have notifications so this is pretty straightforward you'll start to see uh notif numbers pop up here when you have notifications like when someone comments on an issue that you're watching or when someone tags your username somewhere in jira this is just a quick way to hop to wherever those notifications come from you can see down here it's saying hey there's notifications in chat apps right you can connect your jira installation to slack or to teams to get notifications in there you can get notifications through email as well but then all of the notifications that you see in any of those other integrations you'll also see here inside of jira showing up up at the top right hand side here and then we have help this is pretty straightforward but i do want to point it out because if at any point as you're following along with this course if something doesn't make sense make use of this atlassian has some super detailed and incredibly helpful documentation that can answer just about any question that you have and not only for this version of jira but they have it for previous versions as well so if you're using an older version of jira server and you see something that i'm working on that is a newer feature that you don't have access to then you can do a search for it and see if there's a workaround or if there's something else that you can do in there and if the help documentation doesn't have what you're looking for atlassian's support team is amazing even though i am not associated with atlassian at all i've interacted with their support team a lot over the years and they've been really helpful to either fix a problem or even if it's just someone to bounce ideas off of for the best practices say hey this is what i want to do what's the best way to set this up and organize this inside of jira so take advantage of the help if you ever get stuck and we have our settings so if you're a user you'll have limited options in here you won't have access to things like your organization's billing details and all of that information as well as adding users that's something that will increase the bill so depending on your permission level that will determine what you see in here but at the very least you'll see things like your personal settings so you're you know managing your time zone managing your email notifications that you get directly from jira things like that your profile information stuff like that and then of course last but not least we have our personal settings same as pretty much coming in here changing profile things like that pretty pretty straightforward stuff as far as the personal settings are concerned okay so that is a look at the user interface in jira i know i threw a ton at you there and of course as you've seen throughout this video as we choose things from the top navigation then all of this area here is going to change to show whatever it is wherever we're navigating to as you would expect that primary work area changes and we'll get familiar with all these different areas in jira as we start to dig into things but for now i would encourage you to take some time in between videos click around in here and just start getting accustomed to where things are at and how the interface changes when you click around and don't worry you can always get back to this your work area by clicking on the logo up here and that brings us to an end of this section in the next section we'll start by getting an understanding of the two types of projects inside of jira team managed projects and company managed projects see you there before we dive into learning about team managed projects we'll take a couple minutes in this video to learn what team managed projects are and how they compare to the other type of project in jira company managed projects so let's start with our team managed projects team managed projects were introduced into jira in 2018 as next gen projects and then they were renamed in 2021 to team managed projects the primary reason i want to point that out is because jira's first release was in 2002 so team managed projects coming in at in 2018 is relatively new so depending on what version of jira you're using you may or may not have access to these now one of the key things about team managed projects is that they do not require any jira administrative permissions to create them and the reason for that is because all of the entities live inside the project and by entities i mean things like the issue types so any issue types that you create inside of a team managed project lives entirely inside that project by comparison the other type of project the company managed projects they used to be called classic projects and they were renamed in 2021 as well to correlate with the team managed projects a company managed project requires jira administrative permissions to create one of the key reasons why jira admin permissions are required for company managed project is because entities can be shared across other company managed projects so those entities things like issue types and statuses and resolutions if you for example if you create a custom issue type in a company managed project any other company managed project can use that so you have to have jira admin permissions across all of those projects to be able to assign those issue types to those different projects on the flip side the team managed project if you create a custom issue type in a team managed project it only lives in that team managed project no other team managed project no other company managed project has access to that particular issue type i mean i suppose you could create another issue type if you created an issue type called bug in one team managed project you could create another issue type called bug in another team managed project but from the back end as far as jira is concerned those are two different issue types they just happen to both have the same name okay so to recap team managed project have project scope entities so things inside the team manage project entirely live in that project for that reason or because of that there's no special permissions to create a team managed project when you create one you become the administrator of that project and you can everything that you create lives inside of that project that makes them very fast and easy to set up and maintain because any team member in the organization can create one and they can then maintain that project they can invite other users to it and these the team can work together company managed projects on the other hand because they have global entities that are shared across the entire organization across the entire jira installation that means that requires that they have to be created and maintained by jira admins so for that reason they can be more complicated to set up and maintain because these entities are shared across multiple company managed projects and we'll be looking at the more complicated company managed projects and digging into those later on in this course but for now let's move on to our next video where we'll learn how we can create a team managed project in this video we'll look at the process of creating a team managed project unfortunately this process is very simple all we need to do is to come up to projects create project now we can pick the project template so this would go back to some of the concepts that we learned about in the last section is our team using a kanban workflow a scrum workflow with sprints if you're not familiar with these terms we covered them in our previous section just the concepts these are agile concepts or maybe we just want to bypass agile altogether and manage a list of issue types like tasks and bugs or over here on the left there are a lot more project templates that we can pick from i do want to point out that depending on our version of jira we may not have access to all of these templates so let me show you what i mean if i come into service management and let's pick let's say the it management one here at the top notice there's a lock on this template that's letting us know we don't have access to this yet because i'm using jira software for this course and this template requires features that are in jira service management now if we have admin permissions with access to billing because that is a different product with different billing uh we would have to have access to that we could unlock that now and the same goes for a lot of these templates if we see this lock basically it means our current jira license doesn't have the features that we need for that template now there are some templates that we could use let's say let's go into design and let's pick this one here for project management you can see this is using jira work management as a product but we have access to this template the reason for that is because i'm using jira software and jira's software is basically jira work management with the agile software development features built on top so i have access to the jira work management templates but let's go back to software development i'm going to pick the kanban template and we can see what this template is doing for us it's going to create some issue types for us the epic issue type story bug task subtask it's going to give us a workflow here with the columns on our board pretty simple to do in progress and done let's go ahead and use this template now the key thing to point out here is really this part right here i want to mention this because when we create this project if we create it as a team managed project we cannot switch that to a company managed project later on we have to create a whole new project to do that and the same is if we create a company managed project we cannot switch that to a team managed project later on so we have to know which one we want to do at the point of creating so let's select our team managed projects since that's what we're working with here today and let's give this a name this will be our website 2.0 give this a key so this key is going to be on all of the issues so if we say this key is web so all of the issues will be web dash one web dash two it'll just be a sequential order for all of the issues that get added into our project then once we're happy with this click on create and our project gets created all right so now that we have our team manage project created let's get familiar with how it is organized here in jira and we'll do that in our next video in our last video we looked at creating a team managed project in this video we'll continue right along and look at how to navigate around that project so right away we can see by default we're taking to our project's agile board and this is a kanban agile board based on the project template that we chose in the last video so the workflow for this is to take issues from left to right so let's create a new issue here let's say this is our let's just say build flowchart for website functionality there we go once we have this created we can see a few different things here so one we can see the project key this is something again i pointed out in in the last video when we created this project this is the first issue so we can take this and we can left click and drag throughout the throughout the different columns right so that's the basic process that we're going to do take the issue from left to right as work is completed now we can customize this let's say you know what we actually need a new column here for qa so we can track that so once we create this we can you can see how the cursor changes to a hand i can left click and drag the entire column to organize this and you know what before this is actually done we need to run this through qa to make sure that this this has been done and then once that's done you can actually pull that in now up here at the top we can filter any of the issues so if we wanted to filter those issues say just show the ones that have to do with the flowchart you can see how it's highlighting that of course we only have one issue on here so it's it's pretty simplified uh but we also have the ability to see who is in this project and who uh really filter by that so only see the issues that are assigned to me right so right now none of the issues are assigned to me let's change this here select this in the assignee right now it's unassigned let's assign this to me and now we can see this issue has been assigned to me and we can start to filter those issues that based on who those issues are assigned to within the project now we can take that to another level if we want by grouping them so we could group by the assignee or by if there's subtasks let's see what this looks like you can see when we group this it creates in agile this is called a swim lane and so basically what this does is it gives another way of viewing and filtering out the issues if you think you know we have a lot of different issues on this board being able to group them is really really nice way of doing that and see okay these are the issues that are unassigned which maybe we need to assign that to somebody and make sure that that gets done so work isn't slipping through the cracks of course in this example we only have one issue and it's assigned to me so we only see this one but actually you know what let's change that let's look at creating more issues and get a better look at that screen that we saw when we assigned that issue so let's move on to our next video where we'll do that in this video we'll look at creating issues in team managed projects so there's a couple ways that we can create issues including the one that we looked at in our last video here on the board just to clean this up i'm going to go ahead and switch this back so that we're not grouping it by the assignee so we can come in and create an issue let's say maybe this is our ux plan for web app whatever our issue is hit enter on the keyboard and we have our issue created now another way that we can create an issue is using the create button up here at the top or by using the keyboard shortcut c for create so when we hit the keyboard make sure i'm not actually have that selected there we go hit the keyboard shortcut c and we can see it's going to pop up this window where it can create an issue now the key difference here as we can see is we have a lot more fields that we can fill out when we create the issue this way so let's give this a title there we go now this little red asterisk here of course means that this is a required field the summary is kind of a special field in jira so if you look on the board here you can see that's the summary and so it's displayed in different places inside of jira that make the summary a required field really across all of the issue types we can add whatever we want to these fields but i do want to point out this little check box down here this is just a little tip from my experience it's saved a lot of time because as soon as i hit create this window will close but if we're creating multiple issues then sometimes it can be just time consuming to hit create and then it closes and then we have to open it back up again so if we check this little create another box when i hit create this window is going to stay open so we can create another one whatever we want our summary to be and we could just continue doing that continue creating those we can see our other issue has been created i can uncheck this and now when i hit create that window's going to close out and we can see those issues have been added to the board another little tip when creating issues let me hit c to get back to this here is if we don't need all of these fields sometimes especially again if we're creating multiple issues sometimes it can be annoying to see all of these fields and have to scroll up and down if we don't really need to so we can configure the fields and customize this to only show the ones that we want you know we want to show an attachment show how it's flagged if we want to add in labels however we want to customize this we can configure those fields that we see just to make it a little bit faster to fill up fill this out and create our issues now it is worth pointing out that we can customize this and add or remove fields from this list and we'll look at that in our next video when we're configuring this project but before we do that there is one more thing i want to show so let's create this issue here the design there create that so all of these issues here we can see a difference between these issues and this one right here who it's assigned to so we can assign these to different users even if we didn't fill these fields out when we first created if we create it on the board and it just creates creates the issue right away like we saw for this one here as soon as we click on the issue it's going to open up this screen where we can see those fields and you know assign it to somebody else if we want to assign it to mary on our team and then once we close out we can see this is assigned to mary right and this one's assigned to dan and these are unassigned so again if we go back and we can group these we can start to see how all of this works together and how we can use these issues to really start to filter down to only what we need to see so when mary is working maybe she only wants to see the issues that are assigned to her because those are the ones that she really needs to focus on so she can filter those out similar to what we looked at in our last video when we're getting familiar with the layout okay great so now that we've seen how we can create issues and gotten some tips and tricks there we've gotten more familiar with the fields that are on the issue by default let's move on to our next video where we'll look at some of the ways that we can customize our team managed projects see you there in this video we'll look at some of the ways that we can customize our team managed projects so let's start with issue types and how we can add in a new issue type before we do that i'm going to hit c on the keyboard just so we can see right now we currently have two issue types in here we have our task and our epic so let me cancel out of this and let's add in a new issue type so i can go into project settings issue types and then add in a new issue type over here you can see that jira has a couple of them that are suggested that we can add right so we could either add one of these in add that and now if we create a new issue we'll see that there's a bug in here as well or what we can do is we can come in and create our own custom issue type so maybe let's call this an idea let's change the icon to the light bulb here create that and now we have our own custom issue type that we've created in our project and you can see right here where we can customize the fields that are on that issue so again if i create this we can see kind of how it looks on the other end if i switch to a bug let me show all the fields i had that filtered so we can see the fields that we have on this issue type now if we switch this to our new custom one we can see these fields and we can customize these so let's say you know on the idea let's give this a due date on actually you know what we could even come in here and say let's give this a drop down actually let's do this on the bug let's do that on the bug save this on the bug we'll come in and do a drop down and this is going to be location on sites and then fill in the options that we want in the drop down so maybe it's in the the header the body or the footer right make sure to save the changes now if we create a new issue and we have this as a bug we can see we have this drop down that we've added and this is just a really great way to be able to organize everything to be able to say you know what the bug is actually in the footer on the site and then we could start to fill this in and start to you know add in more descriptions to that but on the idea we have a due date we that cus that field that we added in we have that we don't have the location on the site field so hopefully this starts to get kind of the gears turning in your head you can start to see how the fields are on the issues and and like i mentioned earlier in the last section how the issues contain the fields that are going to contain your data and you can come in and start to create custom fields or add in some pre-built fields basically is what jira has for some of those like the due date it's really just kind of a pre-built field that is a date field right that's automatically created for us okay so now before we wrap this up i want to kind of go over some of the rest of the settings that we can customize team manage project customizing the issue types is probably going to be one of the more popular things that you're going to do that's why i wanted to focus on that quite a bit but let's go through some of these other settings that we have to customize our team managed projects so head back to our project settings here so in the details these are some of the settings that we picked when we created the project we can change that here things like the name of the project the the issue key that you can see here as well as choosing who the default assignee is going to be so when we were creating those issues they were assigned to nobody we could choose instead you know what i wanted to be assigned to the project lead which we can set right here so if this was set to project lead when i create a new issue unless i assign it to somebody specifically then it will be assigned to the project lead in this case dan and what that's going to do what i've done in my experience with teams here is to set a point of contact on the team to have any issues created assigned to that person so that person is kind of in charge of making sure that nothing slips through the cracks anything they will then delegate to who it needs to go to or if it's something that they need to do then of course they can take it take control of that as well we have the settings for our board so in here we can come in and add in new columns that we looked at we can reorganize the columns if we need to we can customize our board however we want now you'll notice we have the columns here but we also have the statuses right so this is something that's kind of cool i'm going to take this let's add this here and let's come in and delete this column so now we have two statuses on a single column watch what happens when we do this i'm going to come back to the board here now if i group this by nothing so okay so now if i come in here and i click and drag this i can say you know what i can either take this to in progress or i can take this to qa so those are statuses right so if i click on this you can see the current status of this particular issue i take this and drag it to qa that takes that issue and drag and puts it in the qa status so that's really what's going on behind the scenes if we head back to the settings here we can see that's really what's going on behind the scenes is we have the columns in the board and then when we drag an issue from one column to another it's changing the status of that issue now in my experience there are a few different reasons why you might want to do something like this but probably the most common that i've come across is the simple reason that some teams have a lot of different statuses for issues and if every single one has its own column then you might have to start scrolling left and right to see all of the columns that you have on your board putting multiple statuses into a single column can make it a lot easier to see everything at once okay so let's go back to our project settings and look at some of these other settings that we have here we have the access so we can control who can see our board or who can see basically our project so right now we can see anyone that has access to the entire jira installation can access and administer this project and depending on what plan we have what license we have to jira will allow us to unlock more control over who has access to this project and we have the issue types we looked at that already coming in here and customizing the issue types in this project we can control the notifications so when somebody creates an issue right now anybody who is watching that issue who it is assigned to or who has reported it which in jira the reporter is the person that created the issue the user that created that issue then we can come in here and customize this if we wanted to to control who gets the notifications but by default usually i found the defaults here work pretty well then we have the features so we can come in here and turn on or off some of the features so if we go back to our project we can see we have a road map here and we'll look at road maps later on in this course kind of what those are but we can turn that on or off if we wanted to so if we turn that off and come back and we can see that's no longer there same with the code it kind of depends on what we're using this project for some of these things are set up with the project template that we created right so because we created one from software development it's going to automatically turn on code where we can link in some of our other development tools like bitbucket or github things like that and then we have the apps and we've looked at apps before some of some of the apps in the marketplace i should say i've you mentioned where you can go to discover and find those apps similar to up here i do want to point out the automation automation is something that we will look at later on in this course as well but this is where you can come in and start to automatically tell jira to do things think of tools like if this than that or zapier jira has some of that automation built in automatically and we'll look at that later on in this course when we're looking at it with a company managed project but we can also do that in team managed projects here as well the concepts between those features like the road map and automation between company managed projects and team managed projects are really the same similar to the issue types being the same the big difference is what we learned earlier where in a team managed project like this everything in here lives in this project only for example the idea issue type that we created doesn't live anywhere else but inside of this website 2.0 project that we created so hopefully the gears are starting to turn for how you can customize your own team managed projects and with that we've come to an end of this section i would encourage you to take some time between the sections now to play around with some of these features and when you're ready we'll move on to company managed projects and start taking a deeper look at a lot of the features and customizations that we can do in jira see you in the next section in this video we'll kick off this section by learning how we can create company managed projects now the process for creating a company managed project is very similar to when we created a team managed project so if you watch that in the last section then a lot of this may seem familiar but there is one key difference you have to have jira administrative permissions to be able to create company managed projects not everyone can create or customize a company managed project like you can a team manage project but if you are a jira administrator to create the project come up to projects create project and then in here just like with a team managed project with the company managed project the first step is to pick the project template so this would go back to what we learned about earlier in this course what sort of organization do we want for this you know who in this who in our organization is going to be using this project what are they using it for are they going to be using a kanban workflow a scrum workflow with sprints and at this point usually what i'll do as a jira administrator is i'll sit down with a team leader or team leaders if there's multiple teams that are going to be using this project and get a sense for what their goals are what are the things you're trying to track what sort of workflows are your teams using and the members of your team using and what are the expectations for what this can get and then from there i'll figure out which template will get me most to that point and then you know later on in this course we'll look at how we can start to customize some of the things that the template does with issue types and workflows and things like that but the templates can get you part of the way there over here on the left hand side we have a lot of different templates in here and i'd highly recommend going through and just looking at some of these different templates seeing what is available and what sort of what sort of templates you have access to because one key thing to keep in mind here if we come in here and maybe come to one of these templates we can see this template is currently locked that lets us know that we don't have access to this and that's because i'm using jira software for this course and this template requires us to be using jira service management which is a product that has features that i don't have and so this template is trying to use some of those features but i don't have the license for that now if we do have jira administrative permissions with access to billing then we could unlock that and we could pay for that that's going to be an extra cost with the license that's something to keep in mind with that but i just want to point out if you see this lock that just means it's trying to use features that your license currently does not have so let's hop back to software and i'm going to select a scrum template and we can see what this template is going to do some of the issue types it's going to bring in the workflow over here on the right hand side so if we use this template now we'll be taken to the project type and this is something again that we looked at very similar to the team managed project the key thing i want to point out here once again just to reiterate this is this part up here you can't switch from a team managed project to a company managed project or vice versa right so if we create a company managed project here in this video we can't switch that to a team managed project later on we would have to actually create a whole new project to do that okay so let's go ahead and switch select the company manage projects give this a name so this would be our say our marketing team is going to be using this project and i do want to point out so even though there's team managed project it's called a team managed project right you could still use company managed projects for the team and as a jira administrator the benefit of that would be you can create issue types or workflows or statuses that can be shared across multiple projects multiple company managed projects right instead of the team managed projects where all everything is all encompassing in that one project and once we're happy with this let's go ahead and create the project and there we go now that we have our company managed project created let's move on to our next video where we'll get familiar with what we're looking at here and how to navigate around it see you there in our last video we looked at creating a company managed project so let's take a couple minutes to get familiar with the interface and some of the features that we have in a company managed project starting with the left side menu so this first menu item is going to show us the other agile boards either in this project or boards that we have access to across the jira installation and this is important this is a cool thing to keep in mind about company managed projects that's a different than team managed projects is in a company managed project we can have as many boards as we want living inside of that project we can see all of those right here next we have the roadmap this is looking pretty empty right here because we just created this and we'll be looking at this more in depth later in this section but for now just know that the roadmap is a high level way to see all the epics in our project and their status so earlier when i was talking about the concepts of epics and stories and how they link to the to the epics the the epic itself can be a great way to see all of the stories or issue types that we've broken down to fit inside of a sprint and then the epic itself there may be more than one epic across the project so the road map is a great way to see all those different epics that then each of those epics are going to have other issues underneath them right so it's kind of a hierarchy thing and the roadmap is just a nice way to get a really really 10 000 foot big picture view of the epics in our project next we have the backlog so backlog is another agile term relating to the agile board so like we were learning earlier in this course about sprint meetings where a team decides what work is going to get done in the next sprint that work actually is going to come from the backlog then throughout the sprint as new things come up they get added to the backlog since the team has already decided what to work on for the duration of the sprint so the day-to-day is actually going to be done in this active sprint area and then as new things come up those issues can get created throughout the sprint but they're not going to show up on this board they're going to show up in the backlog for the next sprint planning meeting now i know there will be times where there are emergencies and things really have to be added but the goal of the sprint is we've decided that this is going to be the work that gets done if there's new work that comes in then we're going to have to take something else off that's just the the workflow that happens because you can't make up more time in the day we've already allocated all of the time for things to get done now under the reports is where we can find things like the burn down for the scrum board so the reports for a scrum are going to be different than reports for kanban there are some that are pretty universal uh you know the average age you know how long it's been since it's from created to being resolved for each of those issues i'd encourage you we will look at some of these reports later on in this section but i'd encourage you to take some time there's a ton of reports in here and of course all the data is going to be different the data that you know i'm using and we simply just created this right so there's not going to be a lot of data for a lot of these reports but the data that you have on your side as you're creating issues and as your workflows are going then it's really cool to see some of these and see how they can start to see where some of the roadblocks are and start to break some of those down now if we go back to the project we have the issues so this is where we can see a list of all the issues that live in a project so this is just a simple list of all the issues in the project that we can filter down by status by who it's assigned to things like that this is a very powerful feature we're going to look at this again more in depth later in this section but just know for now that this is where we can almost bypass the agile boards and see just a list of all the issues that are in this project that live inside of this project go back to the project here we have components now components are a way to group together issues that are related so let's say our website has a checkout system well that can be a component so all the stories bugs or any issues that are related to checkout can be easy to find it's just grouping all of those together next we have code so if we want to link this up with bitbucket github gitlab you can see there any source code management tools we can do that and see the see those repositories very quickly here inside of jira and start to see some of the the branches commits and the pull requests and things like that releases are similar to components but releases are think about more like versions right so you can see it's starting versioning so think of anything that is version 2.0 or version 3.0 of our website or app all that can be tied to a release can be super helpful when you're writing the change log or things like that to see exactly what bugs what stories what issues were resolved in that release so the project pages is really a link to confluence confluence is a separate app from jira so we're not going to be covering it in this course but just know that confluence is atlassian's wiki documentation tool so you can link a space filled with pages for documentation or whatever it may be in confluence to a project in jira so that's what this is for to be able to go back and forth with those very quickly and then these last two menu items are pretty straightforward we can add a shortcut so adding a shortcut either to you know a certain repository or i've worked with teams sometimes where they just want to add a short cut to maybe another intranet or specific web pages that are of reference and when you add that you can see the website address and the name it's just going to add it over here in the left side menu is a quick way to navigate to that very very quickly just a way to speed up your team's productivity and then last we have the project settings we will be looking at these more later on in this course but just i want to point out here one key thing here is you have to have administrative permissions to the project not necessarily to jira overall but to this project you have to have administrative permissions to see the project settings so if you don't have administrative permission then on the left side menu you're not even really going to see the project settings linked there okay so we covered a lot but as you can see there's so much more that we have yet to cover as we start digging into all these different features and we'll be looking at most of these more in depth throughout this section and later on in this course but for now let's move on to our next video where we'll have jira create some sample data so we have some things to work with in the past few videos we've looked at a company managed project and when we created the project it came with a scrum board however we don't really have any issues in it so in this video we're going to do a couple things we're going to look at how we can create a new scrum board in the same project and while we're at it we will also have jira create some sample data so we have some issues to work with so let's start by creating a new scrum board in this marketing team project that we've created so come over here to the board drop down click on create board and the key thing i want to point out here is we can create a scrum board come in here click this button and we'll do that here in a second but i also want to point out we can create a kanban board even though we used the scrum project template we can create a kanban board in that same project the template is really just how things are set up from there we can customize things however we want and vice versa is true as well if we created a project with a kanban template we could create a scrum board in there as well so let's create a scrum board now here we need to tell jira where we want to create this right so we want this board to be created with a new project that's basically what we did in the last video except we went the other route we created the the project with the board this is creating the board with the project end result is the same it's just a matter of kind of where you go to do that we can create that create the board from an existing project or we can create it from an existing saved filter now we haven't looked at filters yet those are essentially think of them like saved searches so we can create a board around a filter and we'll look at how filters are a vital part to boards and we'll look at those here in a little bit but for this video we're going to create the board from an existing project now we need to give this a name so let's call this our sample scrum board now we need to tell jira two things one what is the project that we want to be we want this to be based off of where do we want those issues coming from so let's say we want to be coming from the marketing team and then by default jira is going to say oh that's a project we're going to have this live in that same project we could change this if we wanted to if we wanted the issues on the board to be from the marketing team but we wanted the board itself to live in the lefeb t project we could change that so they can be independent of each other and this is where it's starting to it can get a lot more complex but you get a lot more customization of how you can organize things across these company managed projects all right so let's create our board and there we go we have this new board let me skip this so it's the same as the other board as you can see because they're both scrum boards they're both blank scrum boards that we've just created but we can customize these separately so as we're going through some of the customizations in this section just keep in mind that you can have multiple boards and different customizations for different boards living in the same project okay so now that we have this board created let's let's have jira give us some issues so we have some data to work with so everything isn't completely blank like this so to do this i'm going to come up come back to create board and instead of just creating the board i'm going to create the board with some sample data now there is something to keep in mind here when we do this it's going to create a new project right that we're not creating it from an existing project or an existing filter we're creating a whole new project that's going to create that put some issues in that project and then also create a board okay so i'm going to say we can leave this as sample scrum project that's fine go ahead and create this now jira is going to go through the process of creating the project creating the board and creating a bunch of issues for us on that board so let's give it a moment to think about that and there we go so we have this we have a bunch of issues on here and we'll we'll look at this here in a little bit kind of get familiar with what we're what we're looking at here but for the purposes of this video i do want to point out that we have this new project that's been created the sample scrum project you can see the id key ssp is is that key for that project and that's different than the marketing board or even the sample scrum board that we've created you'll notice that these don't have any of those issues so let's move on to our next video where we'll get familiar with what we're looking at here and all of this this interface and get familiar with the board itself and then we'll get into customizing the board and how we can get issues on that sample board that we created to get these issues on that sample board that we created and see those across different projects all right so i'll see you in the next video where we'll get a good overview of this screen here in the past couple of videos we've looked at how we can create scrum agile boards and company managed projects now that we have a lot of data a lot of issues on our scrum board let's take a couple minutes to understand what we're looking at here so as with everything with the left menu you can see we can hover over we can collapse or open this up that's really the case anywhere here inside of jira just give us a little bit more room to see things depending on how many columns you have on the board that's where i find it can be really really helpful to collapse that if we need to up here we have our breadcrumb so we can see where we're at right so this is the board that we're on the board lives inside this project and then this project is well it's a project so we can access all of our projects by clicking on this breadcrumb link here and then down below we can search so we can filter the issues on our board so let's say we only want to see the issues that have if i could spell properly detail in them you can see it has details in the summary so this is the only issue that we're filtering so just a quick way to filter all of the issues on the board and then to the right of that we can filter based on the user that that issue is assigned to we saw this when we were looking at the team managed projects it's the same concept here in the company managed projects if we only want to see the issues that are assigned to me to dan we can filter that or we can find any of the issues that are unassigned or if there are other people who have issues assigned to them we'll see them show up here and we can start to filter them out you can you'll notice that it's actually additive as well so we can add see any issues that are assigned to me and unassigned or assigned to me and somebody else can add that as well right here these buttons here may look a little different on your side if your jira administrator has started to customize some of this so these are called quick filters and these two right here are kind of pre-built they're built in but these are fully customizable by really the project administrator can customize these as well just a quick way again to filter things so only the issues that are mine or only the issues that have been updated recently which recently i think it's a day we'll look at these board settings here a little bit but yeah updated yeah so updated within the the past day is what recently means but you know we can customize that right and again we'll look at customizing quick filters later on in this section over here on the right side let me clear this out so we see all of the issues on the board over on the right side this is for automation so we can start to add some automation to the issues on this board we'll have a video dedicated to the basics of automation and how that works in the next section but just know that you can access some of that here directly on the board we can star this board so we looked at starring projects earlier in this course it's the same concept think of it like bookmarking or or favoriting if you were to star this let's if we go under your work under the boards you can see the recent ones that we've accessed but watch what happens when i start this now if i come here we can see it's always going to be up there i need to actually refresh for it to update there we go so we can see this board has been started so it's not in the recent anymore it's always going to be pinned essentially to the top of that menu so just a quick way to access the board if we want quick access to that to the right we have how many days are remaining in the sprint so this is going to be based on how long the sprint is if you remember from earlier section a sprint is a predetermined amount of time so if your team is sprinting for two weeks and this is the first day of the sprint you're going to have two weeks left you know 14 days left on that sprint so this is just a quick way to be able to see how much time is left to get all of the issues on the board completed then to the right of that we can complete the sprint so once the sprint is over and we're going into our sprint planning meeting in the sprint planning meeting we'll complete this sprint before we actually start a new one so that's this is where you can do that we can share the board so we can share this with anybody who has access to this project inside of jira all right so if you try to share this outside the organization and they don't have access to the jira then they won't they'll be prompted to create an account or log in or whatever it may be they won't necessarily have access to that but you can share this with your team members there and then of course we have the three dots where we can change some more board settings we'll look at that in our next video actually we do have some insights here so they can give us some quick stats about our sprint you know what our current progress is for the sprint just a quick way to be able to see how things are going without going into the full reports or anything like that just a really quick way to see that directly on the board now before we do get to some of those board settings i want to hop over here real quick because a big part of a scrum board is the backlog as well so let's look through the backlog in this interface and kind of get familiar with this you can see there's a lot of similarities so the search the filter based on assignee the quick filters the the insights the three little you know dots for the drop down there to get to the board settings all that is pretty much the same but we also have our backlog so these issues are not in the sprint actually you know what this might be a little bit easier just to walk through a sample process for what this sprint might look like so let's say we're we're working it's the last day of our sprint right so we're in our sprint planning meeting we're doing our next we're preparing for the next sprint first step would be to complete this sprint and so here jira is going to say okay there were three issues that were completed you can see these three issues are done here three issues that are still on the board that are not complete so what should we do with those three issues that are not complete do you want to move them to the new sprint which means it'll automatically put them on the new sprint to get done in the next sprint whether you know two weeks a week a month however long your sprint is or do you want to shift them to the backlog so for this let's actually add those to the new sprint so we can see what happens there complete this it's going to take us to the report we can see how well we did we can have that discussion over what well what didn't go well start to see that really start to see some of the the issues these particular issues that were done something we're not done and start to break that down more and really get into some of the details of where some of the roadblocks may have been when we're ready to figure out what the work is for the next sprint can hop into the backlog and you can see the three issues that we had that were incomplete have automatically been added to the next sprint uh if we want to filter these we can filter them based on the the team member so who it's assigned to and in order to be like you know dan these are the issues that you really need to work on getting complete in the next sprint going through each each person we can see the versions so we can see the different versioning remember we talked about what versions are where we can group together issues so we can see in version 2.0 where there are seven issues total two of them are complete and there's still a couple that are on the sprint there's some that are in the backlog we can start to filter that down if we want to we can do the same for epics so we can see all the issues that are in apex there's currently no issues in epics we'll we'll look at those more later on when we start to work with road maps and stuff but if we have epics it's the same sort of concept as the version it's just another way of of grouping those the same sort of concept as far as this display is here inside of the the backlog now because we had jira add those to a new sprint automatically we already have a sprint that's been created we could create a new sprint if we if we needed to if we didn't have anything here or we can edit this sprint if we say you know what um we're going to do two weeks or no we're gonna do four weeks we can have a custom start and end date however we want to for that that sprint and then the next step would be to add any issues that we need to so if there's any issues that are in the backlog that we need to add then now is the time to do that so either we can left click and drag to bring that up or we can use this little thing right here in order to drag it down and say how many do we want to add so maybe we want to add those three to the sprints just a quick way of doing that one cool thing to keep in mind a little little tip here is we can do this using these filters as well so let me show you what i mean let's say this here i'm going to come in and let's assign this to mary so we have a few different issues that are assigned to somebody other than myself so now we can say okay here in the backlog let me refresh this so we can see this this filter update up here so we can see okay now we have mary up here so we can say okay dan it's your turn to go through the issues that you need uh there's currently nothing in your backlog you know we could create new issues if we need to go through that process when it's mary's turn we can look at just hers and say okay these are the the the issues you need to work on let's just drag those in really quickly rather than having to select them uh and do that so it's a nice way of just being able to work a little bit faster when you're going through that sprinting process when you're happy with things that are there actually i'm going to take these i'm going to hold down shift left click and we can drag those back out so anything that's unassigned we're only going to have assigned issues in the sprint now the next step is to start the sprint confirm that yup two weeks okay two weeks from today start that sprint and now we go back to that day-to-day process of taking those issues working them through these statuses in the columns in order to get them to completion okay so to recap in this video we got an overview of a scrum agile board as well as a quick rundown of an example sprint workflow now in our next video we'll look at some ways that we can customize our scrum boards in our last video we got an overview of a scrum board in this video we'll look at some ways that we can customize that board now before we do any editing let's make a note of what this board looks like right now so some of the issues that we have on here so we have some some issues and subtasks that's this is how you can see there are two subtasks under this story that's what these are here and then we have some other issues a bug a story and another story so just kind of get a note of what we have here so when we make some changes we can see what those changes actually were okay so the main driver for what issues we see on the board is going to be the filter so if we come into the board settings come to general we can see the filter for this board and this filter query is really going to be the driver behind all the issues that we see on the board right so we can see all these issues here these are the issues that are going to be on the board you'll notice there's a lot more here in this list but you have to remember we have a backlog so let me show you what i mean by that so let's come back into our project here i'm going to open this up in a new tab so we have these issues on the board but we also have more issues in the backlog right so the board is really just a way of filtering and displaying all of the issues that are in the filter so this concept can start to get pretty confusing pretty quickly and this is really one of the biggest questions that i get from people who are new to jira is because it's a bit of an abstract concept but if you think of okay there's a project all of the issues live in a project right there might be multiple projects that have different types of issues but all issues live in a project and then a filter will filter that down it's a saved search so what do we want do we want things that are only uh maybe only in progress so now when we see things if we were to save this on the board now we're only going to see those issues that are in progress even though we had some over here before because they're not in progress we're not going to see them anymore as soon as i take this and move it it's going to disappear because it's no longer in progress right so you can see refresh there and it disappears that's because the filter is saying only show issues that are in progress so let me save this back here and then we can hop back may need to refresh in order to to bring those back oh i forgot to save it remember to save the filter there we go now we can bring those back so we can see all those issues that we had there before so again all of the issues live inside of a project a filter is going to tell jira which issues you want to see on the board and then where they display on the board will be determined by the board itself so have we actually brought that into a sprint if not it's going to show up in the backlog if it is on a sprint where on that board is it going to show that's going to be based on the status of that issue and we can customize that just like we saw in the team manage projects if we come into the board settings we can see how how this is laid out so we can see okay these are the the columns that we have these are the statuses so the statuses are tied to the issue and where do where do we want those to show up so let's say you know maybe for this let's add in our qa status and let's say we want that to be in progress okay we could add a new column if we wanted to or we can just have that in the same one and then if we head back to the board now if we take an issue and drag it in we need to refresh we go so now if we take an issue and drag it in we can say okay we want this to be in progress or qa and watch what happens so this issue is currently to do as soon as i drag this over here the issue is now in progress right so the status is tied to the issue and where you drag it on the board based on the board settings will determine what column has which statuses mapped to it now a couple of videos ago we created a new blank scrum board and there were no issues on it because it's in the marketing team project and this is one of the things that's really cool about company managed projects is you can see issues from other projects on boards that live in a completely different one so let me show you what i mean by that come over to the marketing board let's go to the sample scrum board that we created this this blank one here so this is going to have its own filter so if we come into the board settings change the filter and say okay there's no issues in here that's why there's nothing showing on the board because there are currently no issues in the marketing team project if we want to show the issues in the scrum project or maybe both of them there's really nothing in marketing but we could do both if we wanted to save this now if we head back to the board open this up in another tab again we can see now in the marketing team board we have this this project this uh sample scrum board that we created that was blank and now we have this set up so this can be completely completely different if we wanted to we can come in here and we can say you know what for this i am going to add a column and this is going to be this needs graphics right and maybe we don't have we don't have a we don't have a status created for that yet but we could drag this over and we can have that status map just showing how we can customize this head back to the board and now we can see this completely different column that we have so this is one of the huge benefit to company managed projects is we can see issues from multiple projects in one place like we are with this scrum board and the last thing i want to point out about this before we get back to some of the board settings is because the status is tied to the issue itself so this one here let's let's remember this is ssp5 right so we are on the scrum board in the marketing team now if we head back to where we were before let's head back to the completely different project this is a different board and we look at ssp5 let's say we take this and we're going to drag this over to done okay so this is now done over on this board this issue right here might need to refresh and we'll see that it will show up over here as done the reason for that because it was updated on a different board that when we did that we dragged it to the done column even though it was a completely different board it changes the status of that issue so this board here because it's still on that board this issue is still on that board it says oh hey wait a minute the status of that issue has been changed doesn't have to be changed on this board it was just changed elsewhere so now this board is going to reflect that difference all right now this video is actually starting to run a little bit long so let's move on to our next video where we can go back to the board settings and get an overview of the rest of those settings there if you're not a subscriber click down below to subscribe so you get notified about similar videos we upload to see the full course that this video came from click over there and click over there to see more videos from simon says it