Jira Next-Gen Projects for Agile Teams | Danny Liu | Skillshare

Jira Next-Gen Projects for Agile Teams

Danny Liu, Creating digital products the agile way

Jira Next-Gen Projects for Agile Teams

Danny Liu, Creating digital products the agile way

Play Speed
  • 0.5x
  • 1x (Normal)
  • 1.25x
  • 1.5x
  • 2x
43 Lessons (3h 5m)
    • 1. 1 - What you will learn

    • 2. 2 - Why Jira

    • 3. Jira Next-Gen VS Classic Projects Overview

    • 4. Under the Hood: Classic VS Next-Gen

    • 5. Plans and Pricing: Which Jira Software Cloud license do I really need?

    • 6. Global Navigation Bar Overview

    • 7. Global Navigation - Your Work

    • 8. Global Navigation - Projects

    • 9. Global Navigation - Filters

    • 10. Global Navigation - Dashboards

    • 11. Global Navigation - People

    • 12. Global Navigation - Apps

    • 13. Choosing A Board Template: Kanban vs Scrum Boards

    • 14. Create a Kanban Next-Gen Project

    • 15. Create a Scrum Next-Gen Project

    • 16. Project Settings Overview

    • 17. Project Settings - Details

    • 18. Project Settings - Access

    • 19. Project Settings - IssueTypes

    • 20. Project Settings - Notifications

    • 21. Project Settings - Features

    • 22. Project Settings - Apps

    • 23. Project Navigation Overview

    • 24. Roadmap

    • 25. Backlog

    • 26. Board

    • 27. Releases

    • 28. Issues

    • 29. Add Item

    • 30. Jira Next-Gen Reports Overview

    • 31. Burn Up Report

    • 32. Burn Down Report

    • 33. Velocity Report

    • 34. Calculating Velocity Reports

    • 35. Cumulative Flow Reports

    • 36. App Integration Overview

    • 37. Automation Rules

    • 38. Slack Integration

    • 39. Loom Video Screen Capture

    • 40. Scrum Case Study: Building a Simple Static Website

    • 41. Kanban Case Study: Building an Online Course

    • 42. Saving Time using the Bulk Editor

    • 43. Update Labels and Parent Epics for Multiple Issues

  • --
  • Beginner level
  • Intermediate level
  • Advanced level
  • All levels
  • Beg/Int level
  • Int/Adv level

Community Generated

The level is determined by a majority opinion of students who have reviewed this class. The teacher's recommendation is shown until at least 5 student responses are collected.





About This Class

Have you been tasked by your company to figure out how to use Jira Software Cloud for your agile software or other digital projects?

Are you tired of looking for quick and easy ways to implement the best Jira features to help you streamline your agile projects in the cloud, only to find boring technical explanations with complex, hard to understand videos?

Then look no further.

Hello and welcome to “Jira Next-Gen Projects for Agile Teams”,

where you’re going to learn how to master your digital projects using the new Next-Gen project type in Jira, the #1 online agile project management system.

Im Danny, and for almost 20 years I’ve helped startups and enterprise companies build amazing digital products & services by leading high performance teams using tools like JIRA.

I’ve created this course with 1 simple goal in mind, to help you focus on the essentials to quickly master this powerful & flexible tool so you can spend more time building amazing products and services, and less time in Jira!

So let’s take a look at what’s inside!

In this course, you’ll learn how you can reap the:

  • Benefits of using Jira Next-Gen vs Jira Classic Project Types

  • How to automate your next-gen workflow to save more time

  • How to quickly create, read and take action on Next-Gen Agile Reports

  • How to build Jira Next-Gen Roadmaps & Easily identify Dependencies

  • How to create and manage Releases

  • ...and more!

We’ll also dive into several real-world project examples, so you can understand exactly how you too can start leveraging Scrum and Kanban next-gen projects.

Understanding a basic overview of agile terminology is recommended, but you can start using Jira Next-Gen even if you’re brand new to agile practices.

Whether you’re looking to save more time while building software, online courses, content platforms or any other digital product or service, then this course is the one-stop shop to mastering the art of modern project management with Next-Gen projects!

Meet Your Teacher

Teacher Profile Image

Danny Liu

Creating digital products the agile way


Hello, I'm Danny.

As a busy father of 4 little ones and a full-time technology leader, I know the importance of being productive while maintaining a healthy balanced family life.

Each course is focused on helping you spend less time consuming content and more time TAKING ACTION towards achieving your personal and professional goals.

As a seasoned 15 year career technologist, I've led high-performance teams, ranging from technology infrastructure engineering design & support to modern day cloud computing and web development. 

As an Agile Certified Product Owner, Scrum Master, AWS Developer Associate  and Lean Six Sigma practitioner, I'm passionate about all things tech with a focus on produc... See full profile

Class Ratings

Expectations Met?
  • Exceeded!
  • Yes
  • Somewhat
  • Not really
Reviews Archive

In October 2018, we updated our review system to improve the way we collect feedback. Below are the reviews written before that update.

Your creative journey starts here.

  • Unlimited access to every class
  • Supportive online creative community
  • Learn offline with Skillshare’s app

Why Join Skillshare?

Take award-winning Skillshare Original Classes

Each class has short lessons, hands-on projects

Your membership supports Skillshare teachers

Learn From Anywhere

Take classes on the go with the Skillshare app. Stream or download to watch on the plane, the subway, or wherever you learn best.


1. 1 - What you will learn: In this course, you'll learn the benefits of using Jira next-gen versus the JIRA classic project types. We'll also cover how to automate your workflow using JIRA Software Cloud Next and projects. And how to quickly create, read, and take action on JIRA Software reports. We'll also learn how to build software cloud decks, roadmaps, which will help you forecast and see where your project will go, and also help you communicate to your stakeholders where you are on your project timeline. Will cover visualizing the JIRA software cloud dependencies in epics and stories that may have dependencies on each other, as well as cover release readiness, where we'll learn how to create and manage JIRA software cloud next-gen releases. 2. 2 - Why Jira: Alright, so before we get started, it's time for a quick fun fact. So the name JIRA actually is a truncation inherited from the Japanese word go Judah, which means Godzilla. Well, even sounds like Godzilla. And the name originated from a nickname that the Lassie and developers, the team that's behind developing the Jura software, used to refer to Bugzilla, which is a name that they use for a previously internal bug tracking tool for software projects. 3. Jira Next-Gen VS Classic Projects Overview: In this lesson, we'll discuss the differences between JIRA next-gen projects and the classic project types that if you're familiar with Jira, you're already used to using. So let's talk about next-gen projects. Some of the benefits behind using a NextGen project. It's hosted in the cloud, which allows you to get started quickly. And it's very lightweight and flexible. So we'll cover some of the areas within NextGen. And you'll see, again, if you're familiar with using a classic project, you'll see that there are night and day difference is between how you can manage work in JIRA next-gen projects versus the classic project type. But if you're brand new to JIRA, This is definitely the best way to get started, especially if you're working in a smaller team where you don't need a lot of customization to your workflow. But, but just enough to keep it lightweight and flexible. You'll also be able to provide key visibility and agile reporting to your stakeholders to help shape your project without getting lost in the tool. I can't stress that enough. So many times there are tools out there that just keep you in just trying to manage the work inside the tool without actually focusing on the real work you're trying to deliver. Jira next-gen projects help solve that problem. The other thing is that NextGen projects do not require a juris server admin, or other specialized support role to manage your dura projects. Now, some of the cons are that it's not as customizable as classic project types. There's a lot you can do with classic project types, which we will not be diving into in this course. But that is something to keep in mind as you're making a decision whether to use next-gen versus Classic. And also, while there is roadmapping available, endure next-gen projects, which we'll be covering its very basic in that it doesn't allow you to do some of the complex features that the JIRA portfolio roadmapping, advanced capabilities allow you to do in a classic project types. And in a classic project, the prose that you have are that you have some flexibility on whether you want to hosted on-premise on your own servers that you own or hosted in the cloud. It's also super customizable. So if you really need that super customizable access and, and issue control, you can really get granular and what you're able to do with a classic project type. It's also made for larger-scale projects and enterprises. So if you're in a larger scale organization, it may make sense based on your organizational culture and the way that you have your reporting structures. Because it does, again give you that super customizable opportunity. It's also great for certified JIRA admins are agile product owners in Scrum Masters. As you can really focus on customizing your individual teams, your individual line of businesses depending upon how you want to structure the view of your project, as well as any custom customizations to your workflow. And with advanced roadmapping in forecasting capabilities. Using the JIRA portfolio plug-in feature, you're able to provide more robust roadmapping than you would in a NextGen project. Now the cons to using a classic project are pretty evident in that. Well, there's a higher learning curve for one. And so you need to make sure that you, you've allocated some more time in learning how to use the project, using the classic project types, as well as the longer set-up time that it takes to actually get a project up and running. So with these complexities, these are things to consider when deciding to choose between a NextGen project or a classic project type. 4. Under the Hood: Classic VS Next-Gen: And this is a great side-by-side comparison. When you create a new project, you will find these two comparisons. And so when we look at a classic project type, this is the original project type that year has been known for and has a lot of the features and functionalities that you may know and love. If you are an existing JIRA user or if you are a new user, you'll find that it offers a lot of different feature sets and advanced configurations, but that it's also got a very high learning curve. In fact, you can see here it says setup and maintained by admins. So there's a lot of gear admins out there that have obtained specialized certifications and whatnot just to set up projects. So something to keep in mind. Features that you'll see are doesn't come out of the box with roadmaps. However, there isn't advanced roadmap option using the functionality and features set of JIRA portfolio, which is a plug-in that used to be added on. They've included in their software cloud offering as a premium upgrade. Also Card layout customization. You can do a lot more with how you lay out your cards and what kind of data from your cards that you see on your boards, as well as reporting. There's a ton of reports available to you in a classroom project. Now if we look at the NextGen project types, this is really the new project type that at last Ian went to rebuild the Jura software from the ground up with a focus of making it more easier and flexibly use for teams of all sizes. But I find for small independent teams, it's probably fits best. As opposed to classic projects where you may have many teams and you need control across all of those teams. So just think about that. If you're doing, if you're using a small team, NextGen is probably your best bet to go. If you're working in an environment where you have lots of teams contributing to maybe the same goals or some overlapping goals than classic projects may be your best bet. Now the key benefit to next stem projects are that anyone can set up it, maintain it. You don't need to be a certified JIRA admin in order to do this. So really great for a small startup teams that don't necessarily want to hire at your admin when building a new product available features. So they have a nice link to their roadmap. So when you look at this and you create a new project, if you want to know what kind of feature sets are available, you can click on this link and it'll take you to the roadmap for NextGen and showing you what's shipped, what's in the works, and some other cool information to really help you understand what's available to you in the latest JIRA NextGen project type. You'll also see that roadmaps are available. But keep in mind, these are basic roadmaps. But pretty much do most of the things that you need to do for a roadmap view. Advanced roadmaps can contain a lot of different functionality as far as forecasting and AB scenarios where you actually add and remove different team members and add in capacity so that your timeline in your roadmap can be auto calculated based on your available capacity. So there's some, some cool things you can do, but you may not necessarily need for your team. Card layout customization is also something that it has some limitations with. So you really can't lay out your cards and your boards as much as you can in a classic project. And the reporting is a little lean. There's about four reports as of this recording and, uh, pretty much gives you the things that you need out of the box. So from a reporting perspective, I don't see a big difference there. Other than the number. You still will get. The burndown charts and control flow flow charts. And so you definitely have enough Scrum and Kanban reports to get started with. At estimations are only in story points only. I think there are some features Roadmap to work on adding additional time elements. But those are the key differences between your classic project and NextGen project. And keep in mind, this may change. So as you create new projects in the software cloud experience, you will see this change as well over time. 5. Plans and Pricing: Which Jira Software Cloud license do I really need?: All right, so which plan is right for you? So at last has been around for a long time and over the years they've come up with a lot of different product lines in their business. So JIRA software has no shore of options when it comes to what kind of packages you can plans you can choose from. Now, what I will say is the important thing to keep in mind is that regardless of which plan you choose, JIRA next-gen in the cloud is available to you, whether using the free plan, standard plan or a premium plan. As of this recording, the NextGen project type is not available to you if you happen to be using the self-manage option. So the self-managed option is really for enterprises or companies that really want to control the server that they're JIRA Software instances run on. So that's beyond the scope of this course. But just so you know, the different tabs that are out there on the pricing page. So we're interested in cloud and you can see, you can type in how many users you have on your team. And based off of that, you can see the pricing tiers adjust accordingly. So if I put in 20, you'll see standards goes to seven, premium is 14. But if I have ten, up to ten users, it's going to be a standard of $10 month, okay? You can also switch this from monthly to annual. And when you do annual, you'll see there is a little bit of a discount that you'll get on your, your annual subscription. So in the free tier, and this is the tier that we'll be using really to get started. You don't have to pay for a standard or a premium plan because you're going to get all the bells and whistles that you need that we're covering in this course. Some things that will highlight on are the user limitations. So ten users again for the free, for if you're learning this course that's more than enough. If you have a small team, this is a perfect number to get started with. The advanced permission sets are not available to you in the cloud version that's for NextGen projects or classic projects. But you do have all of the scrubbing Kanban boards, the reporting capabilities, and at a bunch of other things. Now just keep in mind that these features include both NextGen and classic project types. So that's the big key to understand, is that they include both of them. Now, that can get confusing, but when you get into your, your free instance to start off with, It'll make much more sense because when you create a new project, it'll ask you, do you want to create a classic project or do you want to create a NextGen project? Just understanding that there's going to be more limitations on the next-gen, Advanced Customizations and functionality will go a long way. For example, the advanced roadmaps are not available to you in either a NextGen project or a classic project if you're using the free or standard version. However, if you are upgraded to the premium version for cloud, you will get that advanced roadmap capability, but you're not going to get it in a NextGen type. So that's a big distinction to make because sometimes I see users posting questions in the forums on the last scene website. And it's really just a matter of, you have to understand which project type you're using because when you create a NextGen project, you cannot undo it. You have to create a classic project type if you want to move your issues over to that, you can't just change your project type. So understanding that roadmaps, the basic roadmaps that are available to you when you click on these links to the features, all of them have a link to it. You can get more information. So with roadmaps, you can see it's calling this out. This feature is only available on JIRA softwares and NextGen project template. So again, this is going to be beneficial to understand is as you go through the pricing page, click on and look at each of these links to see what you're going to be getting, where there's next-gen discrepancies. They usually call those out. But you will see this in the Agile reporting. We covered this in a previous lesson, get access to more than a dozen out of the box reports. And while that is true, keep in mind, you're gonna get more reporting in a classic project type than if you're using next-gen. So take a look at those on your own time to decide which plan you want to go with. But if you're just interested in learning the key concepts in this course, I suggest bookmarking this page to look at a later date and go ahead and just get started with the free plan. 6. Global Navigation Bar Overview: In this section, we'll cover the global navigation and how you can access various parts of your JIRA projects by using these quick links. At the top of the upper left-hand corner, you'll notice this little grid icon. And when you hover over it, a tool tip will pop up telling you to switch to. And when you click on the icon, you'll be able to switch to various outlast him products that you have subscribed to. So right now I have a JIRA software subscription and subscription of ops Gini, which is why it showing up here. But you'll probably only have one to start out with. And you can add other at Lassie and apps by clicking on the discover more outlast him Products link the bottom. You'll also notice there's an administration link here, and this is to access more global administrative functions to manage your various products like security and access and other advanced administrative tasks. The JIRA software load to the right of the switcher icon is just going to take you to the default homepage, which is configured for your work. It also can be set to dashboards. So in the York page, you can click on this three little dots and switch the homepage to the dashboards if you'd like. Those are the only two options as of this recording to set your default link to change in the future, but that's what you have available to you today. Now the next is projects, which we'll dive into in this section, as well as filters and the various filters and advanced and basic that you can switch through. And the various filter options you have, such as basic and advanced filtering dashboards, which will allow you to create dashboards based off of the different datasets within your projects. People, the ability to manage people within your teams, as well as any additional apps that you want to try out and install in your JIRA instance, the create button will allow you to create issues. So you can create new issues and select the project that you want to create it. And so if you have multiple projects, you can easily just create and then assign it to whatever product, whichever project aligns to that work. You'll also notice in the upper right hand corner here a search bar, a global search. And this is very powerful to help you search within all of your projects, all of your various boards and other filters. It's really, really powerful so you can just click on that and type in anything that you want to see. So for instance, if I wanted to see, let's just type in section outros. I can already see as soon as I and a few letters it starts to predict options I'd like to select sites can see selection outros are at the very top of the list k. So that's a global search. You also have notifications. So you click on notifications if work is assigned to you, if you've commented on anything, you'll be able to see those notifications right up in the bell in the upper right-hand corner of your screen. Direct is just notifications that people have at, mentioned you at. So if you've mentioned or if you directly commented, so direct messages are those that saw it as directly tagged you by using an app mentioned within the comments. Also watching, if you're watching an issue, then you'll start to see notifications pop-up in here when Activity and updates are entered against those issues. Ok, there's also a help section here. So if you're stuck on something, you're not sure about how to access or do something. You can click on this help and it'll take you to various forums and features to get up and running quickly tackling some of the questions you might have. So keyboard shortcuts are great. What's new? So features, when you click on this, it'll pop out and I'll just show you some of the documentation blog posts regarding atleast M products. So this is not something specific to Jura software, but this is just add lasting products as a whole. You also see a bell here to show you notifications for any issues that you've been directly mentioned and or any issues that you may be following. So if you're listed as a watcher on an issue, you'll be able to see anytime activity and updates get entered against those issues. There's also a help section. So if you're stuck, if you need help with a particular function in your JIRA Software instance, you can go ahead and check out some of these Help articles on. There's also community of blog forum that's really helpful as well. And few other little tips and tricks to help get you started. I'm updates, keyboard shortcuts and how you can get access to JIRA Mobile. Okay, and then the gear setting in the upper right hand corner, you can see there is a ton of options here for user management as well as your billing. So you can access those details and manage that. Change your billing information for your licensing if you have a paid euro subscription and, and more, there's also JIRA settings here so you can access all of the System Settings, products, projects, issues, apps. So as additional links here to allow you to access some of the more global settings within your instance. Hey, you also sees on personal settings for time zone language and other profile information, as well as how you can manage your email notifications and other settings for your particular account. And then in the very upper right hand you can see there's icon for your account, user account. You can access that. When you click on that, you can see that you have some options here to provide navigation feedback. So this is just kind of a way to share your thoughts with it last season to report if there's any bugs that you're experiencing in your instance, or asking questions, comments, or suggesting any improvements to help improve your product experience using the software. And again, there's some additional give us feedback, general feedback. And you can access personal settings for your account profile, where you can manage your profile, any account settings. And also JIRA cloud for Slack. There's a deep integration with that so you can click on that and that'll allow you to connect your slack account already have Mayan connected. See you don't see that auction here, but you can connect your slack account, which is great for teams using Slack for communication, for team collaboration. And you can get updates sent on your issues directly to different slack channels, which is really nice. Okay, so in the following lessons, we'll dive into each of these global navigation components and explore them a little bit deeper. 7. Global Navigation - Your Work: The first part of the global navigation is the your work navigation link. And when you click on that, that'll take you directly to some of the most recent projects that you've worked on, as well as any particular issues within those projects and anything that you viewed recently or things that are assigned to you. So anything that is assigned to you in the various statuses there in you'll see there. So if you're working on multiple projects, this is a great way to just kind of see your to-do list across all of those projects. And there's also a starred areas. You can bookmark and favorite your issues using a star and that will allow you to see everything in this view as well. And so you can see what you, what options that you have to start your work for quick access, you can start projects, boards of filters and dashboards. There's also a link here to view all projects. So when you click on that, that'll take you to the project's area where you can view all of your existing projects in your work Section. One thing to note here as well is that in the upper right-hand corner, when you click on this more, these three dots, you can see it says switch my homepage back to dashboards. So when you click on that, it's asking me why I'm switching back to dashboards because this was a new era that the added and added as an option to set as your default homepage link. So what I'm gonna do is just click on not applicable, just type a not applicable and hit Submit so that I can show you how it works. So when you click on the JIRA software may navigation link, now it's going to take me to the dashboards area. And this is just an area where you can create different widgets, graphs, some dashboards. And that was the previous default setting for your homepage, but I set it to your work. And so if I want to set it back, I would just need to go back to the your work Link. And here, go back to the three dots, click on More and switch this page to your homepage. So I'm gonna do that. And then when I refresh my screen or click the Jura software like again, it takes me back to your work. 8. Global Navigation - Projects: One link that's commonly used in the global navigation is the projects link. And when you click on the projects link from anywhere within your JIRA instance, you'll see that it'll show you the most recent projects that you've worked on. So you can click on those for quick access or you can view a list of all your projects or create a new project. So I'll click on the view all projects. And so you can see this is all of the projects that you have access to in yours, your account. Or if you want to create a new project, it'll take you through the classic project or NextGen project wizards to create a new project. Or if I wanna go back to my most recent project, I'll just click on that very top and it takes me right there. 9. Global Navigation - Filters: Next up you'll see filters. Filters are great way to search for issues across all projects and even save them as filters for quick access later on. So if we click on the Learn More link, that'll take you to the JIRA software support with some more information on how you can perform basic searches, quick searches, some of the syntax for text fields, especially if you're using some of the advanced searching features. You'll notice a lot in these articles, you'll probably see the acronym J QL, which just stands for JIRA Query language. It's a way to search for specific things within the JIRA database. It's very powerful and highly recommend once you get the hang of the basic search to test it out so that you can see the power of advanced searching capabilities. All right, it goes over saving your searches of filter in more detail, as well as working with search results and even creating filters subscriptions on a recurring period, which will allow you to get an email of a list of issues based on any particular time settings you'd like, daily, weekly, monthly. So that's a great option as well. So definitely check out that helped documentation. We're gonna go back and now we'll click on view all filters. And this shows me all the filters. So you'll see, even if you don't create any new custom filters, you should still see some for the boards that you've created. So regardless of what projects types that you have, you should still see these. So when you look at the filters that you have, even if you haven't set any custom filters up, you'll still see a list of these. If you've created a classic project by default using next-gen, there are no specific board filters that have been created on your behalf. And so this is something that you'll see again when you're using classic projects or if you're creating filters yourself within next n and saving them as custom filters. As an example, if I click on Create filter, I have the Advanced option here for using J QL advanced searching. I'm going to switch it back to basic and you can select the project. So if I wanted to search my current course development project, I can select all of the epics that are in there, and I only have two epics. And then I can click search. It's already started for me. So if I wanted to specifically target the JIRA Epics, then I could type in JIRA and search. And there we go. It only brings me one result. This is great when you have lots of epics. Again, I don't have too much here, so it's not that big of a deal. And if I want to switch to Jake QL for advanced searching, I can do that as well. Now we're going to save it and click Save as. And we'll do test JIRA next-gen filter for epics. Okay, click submit, and now have a saved filter. So if I wanna take a look at some of the details and permissions, I can do that. If I want to subscribe. I can also click on the details link and at the bottom here click on new subscription. And here's where I can set a subscription to get that daily email. I mentioned whether it's daily, couple days per week, specific days of the week, days per month. Advanced can do something more advanced stuff. So if you're familiar with cron expressions, you can select that. I don't really mess with that as you just mess with the daily days per week or days per month. And then you can also set the interval. Do you want to have it once a day as a digest, you'll want to have it every few hours. So it's totally up to you and you can select a specific time triggers as well. So very great option, especially when you're looking for for specific things within your juror projects, like updates. Maybe if you're managing multiple projects, you want to see specific updates from key people. So this is a very powerful way to get access to information really quickly without having to dive into all of your projects and click and sift through all of the work. Okay, just gonna cancel for that for now, not going to set up a subscription back to the filters. You can see now, since I've saved a filter, I have a start filter here for a filter that I've created. And the other option and filters is that advanced issue search that I mentioned. So yeah, that'll take you to here where you can click on switch to J AQL and do some advanced searching using J QL or use some of the default out of the box filtering options, such as projects, types, statuses, assign 0s, and you can even add more available fields that are within issues here as well. 10. Global Navigation - Dashboards: The dashboards link, we'll link to all of the dashboards that you have created across all of your projects. So if you've created a project dashboard, you'll be able to access and see all of these here, star them. You can search them by owner or project or group. So when you have a large organization, this is a very great way to search through all of the various dashboards that are within your company's projects. We can take a look at the sprinkles dashboard. I've got one here just created for an example, Spring goals, we can click on that and that has a few dashboards that I've set up. Just as an example, you can have a workload dashboard shows the time spent by assigning these. You can have issued count dashboards by assigning these for your team. So this is a nice way to get a pulse check on various aspects of your project to identify capacity management opportunities or just to see certain key overviews of your project. You can also create your own dashboard by clicking Create Dashboard and type in the name and type in test dashboard. Input a description in there. If you want to make it more descriptive, by default, it's going to be only private, but you can set it to the public so that other people in your organization could see it. You can access it down. So by default, the axis is private, but you can select that too. Anyone in your project, anyone in your group, anyone in your organization, or just completely make it open to the public, which is going to leave it private. And we're gonna click Save, ok. So now it says test dashboard created, it was successfully saved. So when you look at your screen, you'll have nothing here. But when you click on add a new gadget, you'll have access to a variety of different Gadget types that will surface the data in your projects into a dashboard view. And so if we click on this, we can see, we've got a lot of things here. If you don't see everything here, there should be a link somewhere that says, see more, see more gadgets or add more gadgets and you can click on that, but that you can search here and search for. I want to see a sign assigned to me. I can click on that and click close. And so I can see I can select the number of results, can do a maximum of 50, which I'll just select that. I can also select which columns to display. All right, I can select which columns I want to add here will do assignee already know they're all assigned to me, so I really don't need to see that, but this is just for demonstration purposes. And then you can click on this. I like to click on this so that it makes sure that the dashboard updates at least on a 15-minute interval. Click Save, and then there you go. You can see you've created a dashboard with all of the work that's assigned to you. So go ahead and check out those various dashboard modules and test them out and see which ones work for you. If you're working within a team and maybe you want to see all of the issues that are assigned by teams so you can click on, add a new gadget. This is a popular one. It's called issue statistics. So you can click on that. And then in here, I want to select by assignee, it's assigned by default there on but if it's not, you can click on that and do assignee no filter projects selected. So I can just type in some letters here and it'll take me there. Or I can do an advanced search. I'm just going to click on the course development. And if you have a safe filter or not, you can click on advanced search and then search for filters or other criteria such as the owner who owns the filter. So you can get really advanced with this. But I'm just going to select, again course development out of the search bar and keep assignee selected. And I'm going to click keep everything else here equal. I'll just click update every 15 minutes and click Save. So you can see here, it gives me a count of who's assigned to how many issues and how many of her honoring our unassigned. So great way to figure out how much work your team is taking in overall. 11. Global Navigation - People: The people link will give you access to search for peoples in teams. And so anyone that you have invited to you organization to work within your teams, you'll be able to find them easily by click on this link and you'll be able to manage them. So manage your users or start a team. So if you click manage users, that'll take you to the administration section of your JIRA instance. So this is part of the Global Navigation administration section that you'll be able to manage users within all of the various areas within your projects. So this is going to be a very powerful feature to add new users to your organization and grant them access to the various products that you may be using. Whether it's your JIRA software projects or any of your other subscriptions such as confluence or JIRA service desk or whatever, or whichever other at lasting products you are actively subscribe to. So we'll click out of the administration area. But that's exactly what you can do is click on that to quickly access administering your users. And there's a started Team links. So if you click start a team, this is really nice. It'll give you the ability to group users into a team. You can simply do that by typing in team NextGen. And in here you can just add mentioned people to get them in there. Or if you click on it, it should give you a drop down of some folks in there. So it only took admin and click Start, and there's a brand new team here. So that's just an example of how to create a team. Please let your team members know they'd been invited because they will need to click on the Accept when they log into their account guy. And you can see my act of teams here and another link to start a new team. Again, if you want to search for people in teams, you can do that as well. So I'm gonna type in next-gen team NextGen, and it'll take me right there. So that's how you get started with people in teams. 12. Global Navigation - Apps: The last link you'll see on the Global Navigation bar is the apps link. So if you click on that, you'll be able to make the most of your last name products by extending them with additional apps. So let's click on the Learn More button that'll take you to and about Apps page on the outlast, the inside, it'll tell you about how to manage some of your additional external apps. And what these are are essentially known as add-ons or plug-ins that other external teams, third-party teams develop to help extend some of the capabilities that your JIRA software project that may not have natively. So you can click on that and learn more about the Lassie and marketplace. We go back to the apps link. You can click manager apps. And here is where you can see all of the apps that are installed within your JIRA instance. This is a global setting, so this will be extended to any of the projects. So once you install it, you should be able to access most of your third party installed apps in your JIRA classic or next-gen projects. But pay particular attention to whether or not they're available for Jura software cloud. We're four JIRA server because sometimes depending upon the app that you select, it may only be offered for the traditional JIRA server or just the Jura software cloud project types. One thing to note about this as well is that these apps generally are paid upgrades, so they will give you a trial that you can install. But if you want to unlock additional advanced functionality or to continue to use the app, you will need to pay some sort of subscription fee. So if you want to build a new app, you can click on buildup. And then in here it'll take you to Alaska and connect. And then in here you'll be able to build a new app self. You can write them yourself if you're a coder and you want to do that, or you can just click on the Alaskan marketplace to access a paid subscription plug-in to access a paid subscription option. So in here I know if I want to, let's say schedule tasks, I can click on that and I can see that there is a way for me to maybe automate scheduling some recurring tasks by clicking on the scheduler. And that looks pretty cool. I can click on that. I can look at the overview reviews, pricing, different types of information to help me determine whether or not this is something I would like to try out. You can also see that there is a link here that shows whether it's available for cloud. It looks like it's available for cloud server and datacenter GO reversions. So it should be pretty comfortable with trying this out knowing that it works with my JIRA Next Gen projects. But again, I highly suggest you test a trial and see if it works for you. And take a look at the marketplace to see what maybe some of the other competing similar plugins offer and try those out as well. 13. Choosing A Board Template: Kanban vs Scrum Boards: Within the New Project Setup Wizard, you're going to find a couple of different configuration options. So when we create a new project, we're going to first select Next Gen as our project type. And when you click Next Gen, you're going to be prompted to enter a project name. So we'll just enter, just test here for test purposes and you'll see that there is a template. So the Kanban board type template or the Scrum template. And so you're going to want to choose one of those. So some key discrepancies between these two will cover, and then we'll get setting them up in the following videos with a Kanban board, you're going to have a few different things that are different. A combine is focused on visualizing work in progress using civil cards on the board. And so why don't we look at this. We're going to see that when we click on tell me more, it'll tell us the agile development teams can use this template to plan and deliver work in a continuous flow track work using this simple board and use the board to limit work in progress. Now if we click Change template, we'll see both options here on the next screen. And so if we click on the Scrum option, we can get more information by clicking what's in this. So Scrum is a sprint toward your project goals with a modern Board and Backlog. And the key discrepancy between Kanban and Scrum is that Scrum operates in a timebox. So you have anywhere from one week to four weeks in each sprint that you can define to timebox your work and the work that you commit to delivering. Whereas Kanban, it's a continuous flow. So there is no sprint to timebox into its main focus is managing your work in progress and optimizing that flow so that the work gets completed without sitting in one particular status for too long. And so with Scrum, if we click on what's in this, you can see this one says, plan upcoming work in a backlog, organized cycles of work into sprints, like we mentioned, those time boxes and monitor progress with a civil boards. So they're both simple boards. Alberta key distinctions are the sprints versus no sprints. And with a Scrum project, you're going to want to use point estimations on your, your scrum cards. But in Kanban, it's optional. But again, the main focus for reporting is going to be centered around your workflow and how your your issues are moving through that flow. If you wish to track story point estimation is just for your own awareness to see what you're sizing your stories at big or medium or small. You can use the point values to do that as well. But just note that those points will not be driving any of the existing out of the box reports in next-gen projects. 14. Create a Kanban Next-Gen Project: Now it's time to create a next-gen Kanban board. So taking a look at the Kanban board that I have for this course that you're taking. You can see that I have all of my lectures listed here on a board that doesn't have a sprint. So there's no Sprint button up here in the upper right hand corner, which is the key distinction between the Kanban and the Scrum boards. And when you look at the backlog, there is no backlog button here. Side left navigation. There is the option to turn that on, but four out of the box, the Kanban has everything in the backlog listed in the to-do column here. And so that's how everything is listed in my project. And the focus here is this work in progress. So I put a limitation of a max of one story in the recording and progress phase, not working on more than one. I'm just focusing on pulling one in and finishing it and moving it on to the next phase. And so this is more focused on flow and cycle time. So how long does it take for me to complete stories in recording? How long does it take me to complete them in the post-production phase and moving them to done. As I finished this project, I'll be able to see some real reports and that's something that we can dive into in a future lesson. Cumulative flow diagram will help me show how that flow is work. Am I creating more in the backlog and not getting enough done? Or is it pretty much an even pace across all of my various columns performing at a healthy rate when it comes to completing each phase of the work required for my project. You'll see you'll have the same navigations here as you would if you were in a Scrum project, you have your roadmap releases issues. And really the again, the only key distinction here is the fact that you do not have a sprint. The name of the board is called next-gen Kanban board. So there is no spirit name here, so this will not change. One thing you will notice is that there is no place to put goals because there is technically no end date to the Kanban project. You will not have a goal section to put in here. Now, I've seen some people use this because they love the flexibility with a combine board, not to have to put a start and stop date for Sprints. They can add a little bit of rigor to this and make it more Scrum bonds. So a mix of Scrum and Kanban where you can actually put in here date ranges. So if you wanted to timebox this, you could, for visualization purposes, put that 65 through 619. Let's just use as an example and there is a limitation to the characters that you can put in here. So just make sure that you are leveraging, utilizing the right amount of characters that you need. Okay, so I can call it something like next-gen combine 65 to 619. Alright, and that would just tell me that I've got that date range for completing issues. Now that again, the only challenge with this is that you're not going to ever have an NT ending date on your board here. So that's why the whole goal aspect of it is probably not as optimal as focusing on the workflow and the work that you have in progress. So key distinction, making sure you're focusing on workflow and workflow optimization. And depending upon your project, maybe you do have a lot of deadlines. You do have a minimum viable product that Scrum may fit better for you. And you may have a project where you're doing a lot of support work and that may fall better within the urban context. So to create a new Kanban project, we're going to click on projects and click Create and select Next Gen. And in the NextGen Wizard at her test, Kahneman, NextGen. And then we're going to change the template and switch over to combine. And once you have combine selected, click Create, and now you have a brand new Kanban board. I just taken a look at the project and here's where you can start entering test issues. And if you want to turn on the backlog, you can go to features here. You can click on the backlog and get access to a backlog link similar to Scrum that you can move all of your to-do items into the backlog. It's optional. I tend to not like to use it unless I'm using Scrum, but it's up to you to have that option if you want to move backlog items in to a combine backlog, and that's how you set up a combine project. But just keep in mind, as with your scrum next-gen projects, you only have a one-to-one project to board type. So you can only create a Kanban board in an extended project. And if you want to switch, you're going to need to create a new project and create a scrum NextGen project. If you'd like to have multiple boards in one project, then you would need to use a classic software project type. And that's how you can create a Kanban next-gen board for your projects. 15. Create a Scrum Next-Gen Project: Okay, so let's create our first Scrum board. If you're looking at my screen, you can see I'm sharing a Scrum board for a project called my digital business, and it has the sprint name at the top here, 20 dot 3.1a. I just used a naming convention for the year followed by the program increment or program iteration. And this happens to be the third one. And basically those are just, you can think of those like quarters of the year, first, second, third, fourth, and then there's one which is basically representative of sprint one. So really come up with your own sort of naming convention, whatever helps you organize best. But this is just a best practice that I've used within the enterprise in my day job. And just it's really a way to better align to Agile standards. So looking at the board here, you can see there's a couple of things. One is I've got this little text here and that's a, a goal sprint goal that you can see in the backlog. So each sprint has one of those, and you can see you have the oppor, opportunity to put a goal in there by clicking on the three dots here. And you can edit the sprint and you can put in a sprint goal. So maybe you want to finish a particular subset of work with some sort of key result that you will deliver By the end of the sprint. And you can identify that there and that'll help in your retrospectives. You're doing scrum retrospectives with your team to talk about what worked, what didn't, did you meet your goals in y nought? So it helps with facilitating some of that as well. Another thing to know is you have your complete Sprint button here. You have a start Sprint button if you had no spread active sprints, but this is a complete sprints. So when you're done at the end of your sprint, you can go ahead and complete it. In order to see what the complete sprint ended is, you can easily click on the three dots and edit sprints and you can see the dates here, okay, you can also, for the sake of ease of use, you can even put them in the sprint names. So 656 slash five through six slash 19. And then when you update it, you can see in the name, it's nice and updated here, okay, just make sure that they match up with what's actually the start and end dates. Or else you may have some issues with some of your reports within the Sprint board, you can also see that you can organize by epics. So if you have a bunch of epics, you can filter out some of them and just focus on issues that are related to a particular epic. So I'm gonna take that off. So you can see there's multiple Epics here. And you can also group the issues by a swimmer and you can select Epics first swim lanes, or you can select, assign 0s. So in this case it's just myself or you can do epics and subtasks. And you see I have three sub-tasks listed in here, but I like to either do none or epics. And because I have several epics in progress in this project, I'm willing to select epics edges helps me visualize what work is related to what Epic. And that's sort of an overview of what the board kind of looks like. But when we create one, we're going to go to projects. We're gonna create a new project and we're going to select NextGen and then type in your name. Test Scrum, next-gen. You can call it whatever you like. We're gonna click Change template. We're gonna select Scrum and then click create. A One thing to note is that when you have a brand new board, you're going to notice that there is only an option to have one particular Kanban or Scrum board per project. So that's a big thing to note, is that you can't have multiple boards within a next-gen software project. It's either got to be one or the other as of this recording. Whereas in a classic project, if you're familiar with the classic project, you can have multiple combine and multiple Scrum boards in your single classic project. So that's one thing to just keep in mind is little bit more limited when it comes to the amount of board types that you can have within a NextGen project. And that's how you create a next-gen Scrum board. 16. Project Settings Overview: Setting up your project correctly before you start working on issues is one of the most important steps. And in order to do this, we'll go into our project settings. And then in there you'll see there are various setting options, details, access, issue types, notifications, features, apps, and any other project settings that you have for your plugins are apps that are related to your NextGen project will show up here. So I have Ops Genie, a trial for that. That's why this is showing up. You will likely not see that in your instance unless you have a subscription to Ops GD as well. 17. Project Settings - Details: The first setting is the detail setting. When you click on the detail setting, you'll see, you'll have a few options here to configure it. So the first thing is your icon. If you have a custom icon for your project that you want to use in place of some of the default objects that are, some of the default icons that are provided. You can change icon here. So you can click on change icon and then you can drag and drop an image if you have one to replace one of the default icons that you can choose below. For our simplicity purposes, we're just going to select this little record player here and click select. And now you have a new icon. I don't forget to hit save in order to save it, we click save. You can see it says successor project details successfully updated also the course name. If you want to change that, you can do that here. We're not going to do that for this demonstration. You can also see that you can change the key as well. And the key is that those letters that are in front of each of your issues. So you'll see a cd dash, one, cd dash T2, whatever they key is, you'll see those letters in front of any of the number of the cards that you create the issue, you'll see those letters prefix to the numbers of the issues that get created. And here is the category dropdown. You can select a category if you have one created. If you don't have one created, you can click on the Manage categories link. As soon as you click on that field, there's a drop-down to manager categories. We'll click on that. And then here you can create categories based off of the projects that you're working on. So I have one here for online courses and a description I have is I publish online courses on Udemy, Skill Share, and stack commerce. And so I can associate my projects with this particular category if I have a lot of different ones that I want to group, that really helps. But you may not need, really need this. This is really just kind of for your information for later on as your projects pick up steam and you build more projects as you scale your team's. This'll be a great way to categorize projects in some relatable fashion. So you can click on add new project category and we'll just type in here, Next Gen projects, all next gen project types. This is just Thanks sample. You probably are not going to really do that since the, this is just a project type, okay? We're just using this for an example. You're likely not going to call the category next to him projects. But this is so you can see, all right, I'll click add and you can see now there's a next-gen projects category types. If I go back to my details and click Choose category, I can see now I have the next-gen projects as an option. However, I'm going to select online courses since that's what this project is related to. And you click Save Project Details successfully updated and you're all done. 18. Project Settings - Access: Within the project access settings, you can see that you have a nice simple list of all the users that have administration axis to your project. Now there's a few things to keep in mind when leveraging this area of your NextGen project. And that is, if you're on a free plan, you're not really going to be able to do much with this area Azure building a small team that may not really be an issue until you start building your team and having more requirements around who can have sitewide administrative access to your NextGen project or not. So you, what you can see here is all of these buttons are grayed out because we're on the free plan. And if you want to upgrade to a higher level plan, you can do that. And you can do that by clicking, Try it now or learn more. So I'm gonna click on try it now. And you can see you'll get a 30 day trial as of this recording if you want to upgrade. But on the current free plan, you can go back to doing that comparison to see what you have available to you versus what the standard or premium plans will give you. If we look at access and issue permissions. So we have issue permissions and project permissions is, are all related around access. You can see that you'll need to at least go up to the standard version in order to leverage those features within your project access settings. So if you don't want to upgrade and you want to stay on a free plan, then just know that anyone has access in general to your site. In this case, my site is called Lean tech creative. Anyone who has access to your site will also be able to access and administer this project. So you won't see any one in here other than the admin account that I have for this particular project. But you will see in the administration settings. Now this is where you can see. You can only add people using your site's administration settings, not your project. So this will show us who has access to my lean tech creative site. And therefore, if they access this next term project, they would be able to administer this project as well. So let's click on administration settings. And I can see here, I can invite more people to mysite. But at a minimum, what you can see up here is at the top, it says admin and it says by site name. And then here all your users. So down at the bottom you see I have my org site and admin account. I have a site admin and I have an additional member here. This is my son. We handle household tasks and chores using a Kanban board and JIRA. And so it's a nice way for him to earn some points and make it a little bit more competitive and fun for him and his brothers. But so he's got sight axis. You can see all of these accounts at site access. So that means that if I login with any one of these accounts, I would be able to administer my next-gen projects as well. 19. Project Settings - IssueTypes: The issue types setting will allow you to, to customize the issues that you have in your project. So by default, when you create a NextGen project, you may only see a few issue types. You might see epic. Epic by default will show up here, and you may only see task or story, and you might not see both of these. So if you want to add an additional issue type, you can click on the plus attitude type button and that'll allow you to add any issue types that are not currently available in your project settings. So this one is the only one that's not available. So I can click add and this will add the bug issue type to my available create issues. So if I create a new issue here, I can see create and I can see in the drop-down box here, the issue type will allow me to create an epic story or bug for this project. I really don't care about having bug issue types. So I can click on that. And at the three dots here up next to the lock, I can delete issue type, and now it's removed from my project. So if I go back to create and I see the issue type is here. When I click on that, I no longer see the bug optioned for creating a new issue could cancel. Now, in the main section here in the center, you'll see this will show you the features. And in the center of the screen you'll see depending upon which issue type you have selected, it will provide a view of all of the available fields that can be customized by the issue type. So if I click on story, I can see there's another set of description fields in contexts fields and as well as task that'll give me the ability to customize based off of issue type what I want to see and what I don't want to see all my issues. So taking a look here at stories, I will see that the description fields there, the summary field is there, and those are by default, the context fields here below will be able to add or drag and drop where these are laid out on your stories. And you can add additional fields that are available in the left pane to your stories. So we can see here if I wanted to add a custom field here, I can create a field, drag a field to the left area to create a custom field for your story swap. If I wanted to put, let's just say a checkbox, I could do that. And let's say I want to put that right under the status. And I could enter this field name and say, is this critical? And I can add an option. I can say that option one is yes or option two is no. And we could put a description here. Define critical stories versus non-critical. Okay, so now when I save changes, this check box is going to be available on my issues. So if I create a new issue, I can see here I'm in tasks, so it's not showing it. So I'm going to switch the story. And I can see right here, is this critical? I can select, Yes, and we'll do test Issue type configuration. And let's just click Create. Okay, so now I can see up here little notification pop-up for where my issue has been created, but I'm going to go right to the backlog. I miss the window there to click on that link on the notification. So I'll go right to the backlog at the very bottom here I can see Test issue type configuration in my to-do column. And when I click on that, I can see it says, is this critical? Yes. So that's a really powerful way to add some additional context to your issues within a NextGen project without being really over-complicate it. In the classic projects, managing some of your custom fields can be a bit of a chore in trying to figure out where everything is. And so what NextGen has done is really gone leaps and bounds in making this a simple process for adding some more additional customizations to your issue types. 20. Project Settings - Notifications: In the notification settings, you can send people or roles in email when events happen on an issue. For example, when someone comments on an issue, someone assigns an issue, someone deletes an issue, the settings on this page will be overridden by a user's personal notification preferences. So you can see down here, here are all the current events that will send notifications to the recipient, which is all watchers per assignee And the reporter on an issue. You can use the actions and next to it to edit or delete these rules. So if I click Edit, lets say I want the current user, can the project role of administrator to be included and click on save and out. Those additional recipients will be added and email notified anytime and new issues created. Also, you'll notice here where it says overridden by a user's personal notification preferences. If you click on that link, that will take you to your personal account and your personal user settings. And this will override any other global settings that you just visited in your NextGen project. So any of the settings that you have here in this event list will be overridden by any settings that you have in your personal settings. So let's say you don't want email notifications at all. You can just send send me email notifications and that will effectively not send you any email notifications despite what the project global settings has. So you can see here it says, watch your issues inherit from global settings. So because that's enabled, you'll automatically get those notifications if you're watching the issues you interact with. Okay, so this is a more advanced granularity you can do to control your email notifications. You can disable this entirely. So if you click this abled and save changes, you won't get anything at all. But we're just going to leave it clicked as inherit from global settings. We're going to, I'll just discard here and go back to our global notification settings in our NextGen project. Two other things to note here are the add notifications. So you can click on add notification and it will show you any of the available events that are not currently added. In which case, right now, there's just a single one here called issue comment deleted. So I can add that and then I can send a notification to, let's say, all watchers and adds it to the very bottom here. And it adds it to our list here where it says issue comment deleted, and it says all watchers. The last thing in Hindi email notifications is the domain that you're using to send it as. So what that means is whenever you open your email, this is the address that it will show as being sent from. This'll be in your From field on the email. Well, if you want to send from a particular custom domain, you can do that. However, you must make sure that there are specific things set before that will actually work. One is you need to make sure that you're sending it from a domain that you own and that you can verify in JIRA. In order to do that verification, there's a process that is provided in the outlast even help documentation for setting up a custom domain send from address. You can click on this link to learn more. However, when clicking on this link as of this recording, it does take you to a page that doesn't exist. So just as the Internet works, sometimes you click on links and they don't necessarily take you to where you want. So I've found that Google is still my best friend when trying to get past these roadblocks, you can just type in your Google search, JIRA, email notifications from domain. And I did that. And the first thing I see here is configuring cloud to send emails on behalf of your domain. So I click on that, and this is where it should have probably taken me. But I had been now you have axis on how to troubleshoot any of those broken help links. So configuring Jura cloud to send emails on behalf of your domain. So you'll need to make sure you follow these steps specifically and that you have the administrator capabilities within your account to ensure that you can verify your domain ownership down here so that JIRA can send emails on behalf of a custom email address that you want to show up as being sent from for any of your automated email notifications. 21. Project Settings - Features: In this lesson, we'll dive deeper into the features settings within your next-gen projects. So if you have your project open, you can access your project feature settings. Under the project settings. We'll go back to the main menu here you go to Project Settings and then click on Features. And you'll notice that you have a few toggled on by default. So when you create your new combine project or Scrum project, you'll see a feel of these toggled on already for you. Now, the default features available to you that are already on may change over time. But when you create your project, it's crucial to come back here first so that we can make sure that you have all of the features available to you from the start. But don't worry if you haven't and figured something or if you want to switch something later, you can always come back to your feature settings. So let's cover some of the available features. We have. The roadmap feature, which is a high level view to help you create and manage your epics and see them visualized on a timeline similar to a Gantt chart. And you can learn more about roadmaps by clicking on the available link here to give you a full overview on the roadmap area. So give you a full rundown on the details for roadmaps. I will also cover roadmaps in a future lesson. Next is backlog. In the backlog section, this is where your team's going to plan and prioritize the work in a dedicated space. There's also a link to the backlog as well. And there's a link for every one of these features to learn more about them, to learn more about them. And again, we're going to cover most of these as when you toggle them on, there'll be a new link in the left, tan, vertical navigation for each of these areas such as the roadmap, the backlog, sprints, and we'll show you what that looks like as soon as we go on over. If I click on back to project, you can see I only have roadmap and pages enabled. Board is already there. Roadmap and pages are features. And so when I go into my project settings under features, those are the two that are toggled on roadmap and pages. So let's take a look at Sprints. Sprints is grayed out because this is a Kanban board and it's not turned on by default. So completing work in fixed units of time requires a backlog. Okay, so if I want to toggle this on and enable the backlog, and now I can toggle on the sprints. Once I toggle on the sprints, Then I can go back to my project and see I now have switched my con von project to a Scrum project because I'm going to leverage sprints. So let's just create a sprint and show you what that looks like. So create a test issue, alright, and then start the sprint when just going through this quickly. So you can see now it's got the complete Sprint button and everything. It is a Scrum board. But if I want to switch back, I will go back into my project settings, go back into my features. And now I can turn this off and I can leave the backlog if I want, or I can toggle that off as well. Now if I go back to my project, you'll see there's no longer a sprint section here and go back to my features. Now, just keep in mind when you are switching between Kanban and Scrum, there'll be different reports that are available to you. So that's the next module. So we'll enable reports and I'll show you exactly what I'm referring to. When you click on Reports, you'll be able to see a report and link. Now, there's a report link on my left navigation bar. And when I click on that, because I'm in a Kanban configuration, I only have access to cumulative flow diagrams. I will need to enable sprints in order to activate the burn up. Burned down and velocity reports. So if I go back, go into my project settings, go into features and enable the sprints again. And sometimes you might have to click this twice. That may just be a little bug in the UI, but you might have to click on it twice in order to turn that fully to green. And then we are set up for Scrum. So now if I go back to the reports, I should see all four reports available to me. So there you go. There's a burn up Report, sprint burndown chart of velocity report and accumulated flow diagram. Now you can see since this is a brand new project, it's a weighting of completed sprint before it can start to calculate some of the velocity based off of completed work makes sense. I'm gonna go back to the project, back to my project settings and back into features. So I've enabled the backlog, the sprints, the reports, and I'd also like to enable estimation by default here and a combined configuration. I did not have the estimation checked. You wanna make sure you double-check that whether you're in Scrum or combined so that you can calculate your team's velocity by estimating each issue in the backlog using points. And you can learn more about estimation by clicking on this link. This course isn't a deep dive into Agile story writing or estimation, but all the information that you'll need to know can be obtained within the additional documentation. So estimation. Now that that's enabled, go back and I can see I have a test task here. And this task shows that I have a story point estimation field here. Now, now I can enter in a 1235, whatever my point estimation value is, I can enter that and click Check. And now it shows I've got a one-point value against this issue. And I'm going to refresh the screen and now you can see that the one is showing up on the card. Okay, go back to Project Settings and into features. And the next thing is pages. Now we're not going to dive into pages. This is beyond the scope of the NextGen project because this is an additional subscription to the confluence application by Lassie. And all you need to know for this course is that you toggle this on. You'll be able to see the link in the left navigation bar. Or if you toggle it off, you will no longer see it. Some going to toggle it off. And the next one is releases and versioning. Now this is very, very useful to help you manage and package and schedule your project deliveries. So if you're building software, this is great to help you identify the versions and when they're being targeted for release and what sort of features are included within those releases. And you can learn more about released versioning here. We're going to toggle this on so that it shows up in our left navigation, but left navigation pane will also cover releases in a future lesson. Next up is the issue navigator. So this is really powerful in helping you identify where your issues are and focus and filter on specific issues, especially as your project backlog continues to grow, it will get very difficult to find what you're looking for unless you're able to effectively navigate through the list of issues within your project. So you can see this is built-in filters and text searches to find specific issues. So we're going to toggle that on. And then this last one here you probably won't see unless you have Ops Jeannie enabled. This is additional applications similar to an add-on for confluence to provide extensibility in some of the functionality in your JIRA project to view on-call schedules in your project. And this is for the ops Jeannie add on by elastin. So I want to keep that turned off. And as you subscribed to two new plug-ins and additional features that elastin offers. You may see additional feature configurations in your list over time as well. 22. Project Settings - Apps: The last project settings is probably one of the most effective areas that you can leverage to help extend your dura next-gen projects as far as what kind of functionality and what kind of automation efficiencies you can integrate. So let's take a look inside. Click on the project settings and apps Settings link in your left nav bar. And as soon as you do that, you'll see there are two native apps for project automation and slack integration that you can configure. We'll dive deeper into each one of these to get them set up inside of our app integration deep dive section. But for now, just know that there's a project automation in that you can automate different tasks within your issues, such as reassigning issues or moving them to another project, or creating new issues in another project when you've completed issue. So there's a lot of automation that you can leverage. This was pretty exciting to help you streamline your workflow and minimize the amount of manual work that you have to do to manage your project. So you can see there's a link here for all roles, Project rules in global rules. Now, as a free account, you do have some limitations. But again, for basic projects, this is probably all you really need to get started. So you can see Project rules are enabled. So just as an overview, if you take a look here, you'll see there are roles at the global level across all your projects. There are project specific rules that you can set up and configure. And you can even add labels for your rules and the slack integration, you can connect a slack account. So if you use Slack for messaging, it's a great tool for just streamlined communication that you can basically set up separate workspaces, separate channels within your workspaces, as well as direct messaging to your team members. The slack integration doesn't support direct messaging, but most importantly, you want to leverage a channel that has your team members all in it for the most effective collaboration. So in here, I don't have anything set up, but I do have a channel that I've connected before. So I'm going to click on that. This is my lean Tet creative Slack Channel. And I'm just going to click on the General and I'm going to add up. And then you can go, you see I'm logged into my Slack account already. So it's basically shown here that if I click on, I can see that the integration has been set up and that's just a high-level overview of it. Again, we'll cover the slack integration in more depth in the app integration deep dive section to help you set up your slack integration. If you've never done it before. 23. Project Navigation Overview: And this section will talk about all of the available links that you have in your project navigation. So if you're looking at my screen, you can see on the left side of your screen a navigation column. And these are all the links that you can access. Some of these are features that we enabled in a previous lesson where you can see a roadmap, your backlog, the act of board that you're using, whether you're using a Kanban or a Scrum board, the releases that your project has, the issues within your project. So within here you can do some more basic and advanced querying and filtering to locate specific issues based on certain criteria, as well as access reports, performance reports for your project. If you have the slack integration set up, you'll also see that here to quickly access that features app setting in your project, as well as an add item feature that we enabled, which will help you add links to external projects, external websites to help you quickly access those if they are related to your project. 24. Roadmap: So let's take a look at the roadmap. When you're creating a brand new project, you'll see that you don't have anything here, so you can get started by just typing in an epic name for your project. So an Epic is essentially a larger chunk of work that needs to happen over a period of time where you can add your supporting stories or tasks that are related to that epic. So that's more of the parent-child relationship for any of the issues within your epics. So the first thing we're gonna do is just say build, front end design. Okay, so we can set up these and you can see I have my JIRA slack integration set up, which is why I got notified here. But you can see in the roadmap, once I create, build front end design, I can now add a child issue to this if I want. First, I'm just going to click on the epic named build front end design. Within the roadmap, you'll see that you had the opportunity to add epics that relate to the different higher levels of work that need to be completed within your project. So you can just think of an Epic is just a larger chunk of work that has to happen over a longer period of time, then you're supporting stories or tasks. So let's just type in here what needs to be done. So if we're creating a brand new software project, we probably want to do a little bit of design, a little enablement work. Let's take a look at from a design perspective, we will create an epic for create the homepage. Click Enter. And you can see that I have the slack integration set up, so it has popped up and notification in my general channel. This is nice so that you can quickly access it and be notified within your slack channels if you use that integration. So now that I've created this epic, I can click on the epoch and I can see, and I can access all of the available options for me to configure labels, assign the assignee, put in more descriptive acceptance criteria or specific features that are part of this epoch. And the key thing here to note is the start date and due dates here. These are going to drive your roadmap. You can see there's a start date here of seven for 20-20, but there's no due date. And so you can see rounds out the edges of the end of the bar here against the epic because there is no duty. So if I were to just click on this and set a due date, let's say I'm going to create this by the end of August and went put the 31st about the end of July. So I'm going to select July 31st and then just click on outside of that. Now you can see squared off a little bit and it has that start and due date. You'll also notice that there's a link here for creating dependencies. If you have additional epics here, you can link and create dependencies. So let's just say that I have a dependency on designing the initial mockup, just hurting example. So now if I click on designing the initial mockup, I have this link as well. So what I can do is I can click on that link and now drag and drop it right to this epic. And you can see there's a dependency link there now. So now I can see that creating the homepage is dependent upon. The designing of the initial mockup. So if I drag and drop this, you can see how the dependencies are lined up. Now this says that creating the homepage has to happen before the designing of the initial mockup can happen. So that's a little bit backwards. If we wanted to make sure that this is correct, click on the View dependency detail and you can see create the homepage blocks, designing the initial mockup. Well, if we wanted to get the initial mockup completed first, and what we would need to do is we would need to simply unlink this issue and then create it from the start of Crete homepage and link it to design initial mockup. And now you can see that the dependency has been late correctly. The design has to be completed before the creation of the homepage can start. So next is the issues. So once you have your epics created, you can create supporting child issues by clicking on the plus sign here. Or you can go within the details by clicking on the epoch and going in the right navigation pane and add a child issue directly within this view. So we'll do it in both ways. I'm gonna close out of that, will create the homepage right on the roadmap, will create a, a subtask that says what needs to be done. And we'll say add header, image, click Enter. Now that you can see that's been created, I can see the status that the issue is in. I click on the epoch right view page, I can see that there is a challenge issue directly here. Now if I wanted to add another issue, I can do that right from within this view in the right hand portion of the screen. And I can say add primary navigation menu Enter, and now you have that task created as well. So two quick ways to add issues within your epics in the roadmap screen. You can also now that we have some issues here, take a look at the status. We can look at all of those to do all of those that are in progress and all of those that are done. So if I click on to-do, everything isn't the to-do column. That's why it's showing me everything. If I click on in-progress, nothing has been moved. So it says no results found. Same thing for W1. I'm just going to select them all. And if you want, you can also clear the filters and that'll show everything you can look at today. So if I just want to look at the Gantt chart view timeline for today, I can click on that and it will scale the view back so that I'm looking at this orange line that is representative of where I'm at today and how far our epics are for completion. And within the view section, if you click on that, you can see you can able to dependencies, links that we created before, or you can enable or disable progress, progresses this little bar here that you see, it's gray underneath, that shows you the progress of all the stories underneath rolling up into your epic. So if we turn that off, you see that little bar disappears, turned dependencies off, you see the gray dependency link here disappeared as well. We're going to click both of those because I want to see both of them can also click on Months and get a view of weeks, months, or quarters for your timeline view, I'm gonna click months again. And then there's a couple of things here you can do. You can share this using a link, copying it and setting it to someone. Or you can enter a name team or email to send a message with this roadmap link. You can also export your roadmap into an image and it'll give you a little preview there. And you can use that to send in other Slack channels or another emails. I'll link to the image of your roadmap. Click export, and you can see it. Download the image right to my computer and click cancel. And that's the roadmap section for Next Gen projects. If you're looking for more advanced customization and functionality, I highly recommend checking out the pricing options for the standard and premium options to see if you qualify for using the JIRA portfolio plugin, which has been baked into those software cloud experiences and gives you a lot of forecasting capabilities, as well as other items such as dragging your prioritizations and ranks in a top-down fashion. 25. Backlog: The backlog section is the area where you will prioritize your issues if you're leveraging a Scrum project or rearrange or issues if you're leveraging the Kanban Backlog. This is a feature in common bond that has to be enabled in the project settings, which we covered in another lesson. But primarily you'll see this as a default for a Scrum project. And when using a scrum configuration, you'll see the Create Sprint button here to the upper right. If you are in a Kanban backlog, you would not see that. So here we're going to create sprint just to show you what it looks like. And it says Test spread because I have an event trigger for that, showing me that I've created a new sprint in my slideshow. Now notice I already had existing things in my backlog. So if I want, I can drag and drop those issues directly into this new sprint right from my backlog. And then when I'm ready to start the sprint, I can click Start sprint. So make sure if you're using Scrum, you've already added your points. You've already refined your stories and included all the acceptance criteria and estimation points so that when you start this sprint, you're really ready to go. You can also edit the sprint or delete a sprint. So if we want to edit the sprint details, we can rename it. We can also put a golden hair, develop the primary navigation, and include header image. Okay, so that can be there, our goal for this particular spread. And when you save it, you'll see that right under the sprint name, you'll have a goal that was entered here as well. And this goal will show up on your reports when you look at your sprint reports, which we'll cover in another lesson, that you can also filter by Epic. So you can select issues without an epic if you have a big backlog and you're trying to identify which issues need to be aligned to an epic. You can also enable the Epic Panel, which will give you all of your epics in a nice view on the left, fly out of your backlog and you can see, you can drill down into that and get some more information on the start and due dates. You can click to view all details and that'll pull everything into the right of your screen. Okay, just another quick way that you can leverage the additional views within your backlog to manage your issues and your epics. So I'm just gonna close that out. You can also select version. So if you have versions that have been created in your project, you can see them in this panel here. So when you toggle on the panel, you'll be able to create versions if you don't have them. And essentially, it gives you a little explanation here at versions really helped you package and schedule project deliveries. And so if you're delivering a software version, you can enter that all the issues that are in there into a version bundle that and create a version name for it. Likewise, you can use it for even non-software projects where you have milestones and deliverables for the work breakdown structure that you might have in the form of issues that support a particular milestone. So we click Create version and we can just type in test version. We won't put a start or end. It will. We'll put a start date and we'll put a start date in here. And then we'll put an end date out a week. And we'll just put in test, release and click Save. And so you can see touch version is there. And now if I wanted to tag stories, I could tell stories to this test version. I can also drag and drop it directly so I can click on the task and I can edit it by selecting the fixed version here, which has my test version. Or if I want, I can just drag it and drop it directly in. Or if I want, I can just go into Edit version here or I can add my issue to a release and the release of section which we'll cover in another lesson, okay? And you can also filter issues. So if you're searching for a particular keyword, you can go ahead and do that, which is really nice. You can also click on add people to add additional team members to be able to view this, you can create as many sprints as you want. Just note that you'll only have one active sprint once you start it. 26. Board: And the project navigation, you'll find the main link to your board. So whether using a Kanban board or the Scrum board, you'll find the Board link right here on the left. Now, one thing I wanna point out is when you have a lot of columns here on your board, you're going to need more screen real estate. A neat little thing you can do is just collapse by dragging, hovering over until the line turns blue and then drag it over as much as you want. Or you can use the collapse icon with the arrow to close or open with the arrow to collapse, to give you that more screen real estate set, view your other columns or keep it with your navigation showing. Now as you create new columns, I'm just going to create a couple to show you what this will look like if you do not have enough screen to show all of them. So if you have, let's say testing, acceptance, just making a few up here. And let me minimize this window and drag and drop and close it. You can see at the bottom to view your board within the project navigation, you'll want to access it via the third link here on the project navigation titled board, whether you have a Kanban or a Scrum board, this is the same name you're going to see. So wherever you are within your gear NextGen project, if you click on board and it'll take you right to your board. Now, this board is showing me that I haven't started a sprint since I'm using a Scrum board. I can't do anything until I've started a sprint. I'll need to go to the backlog and start a sprint in order to, in order to move stories on this board. So I'm gonna go ahead and do that. Click Go To backlog. And I already have a sprint that I created. But now I'm going to start it. So I'm going to click Start sprint. I'm just going to leave the name as the default. Also the duration. I'm going to leave that as two weeks and I'm going to leave the time set for now. You have the option to put a sprint goal in here, which is really nice to help keep your teams on track for the particular spirit timeboxing, you have a two-week time box of a sprint duration. But the end of those two weeks, we will be looking to develop the primary navigation and include a header image for our website. And you click start, and now you can see on your board, it automatically redirects us there and shows us that we have the two stories that we identified and slotted into our sprint one along with our sprint goal directly underneath of it. You'll also see a filter issues. And this text search is just going to filter out any text that you put in there. So if I wanted to look for the navigation, I can just type in that and it will automatically filtering on that particular summary for the issue. If I wanted to put create and won't do anything because it's not looking at the epic link. It's looking at the issue itself. So this is the epic link, create the homepage. So you were particularly just looking at the contents of the issues issues title and we have the assignee is. So if you want to add people to your NextGen project, you can click Add people directly. There's also an epic dropdown here, so you can filter specifically by APIC. So whereas this filter issues text search is going to really look at the stories and bugs and tasks. All of the issues that are under the epic level. This epic one, we'll focus just on the epics. So I can click create homepage. And I only have two stories there for it. And I don't have another one. But if you can see I clicked on the other one, everything disappears because I don't have anything for designing the initial mockup in this sprint. Okay, I'm gonna uncheck those. And you'll notice that the other end of the top of your springboard, you'll see there's a lightening icon and this is automation. Will get into automation in our app integration deep dive. But this automation essentially is going to take you right to pop up here, which is going to provide you some common triggers to create some automation within your workflow. And this is really powerful when you, when you start to get into the rhythm of your project and getting the work done, you'll identify some efficiencies as far as maybe every time you move it into him progress, you want to have it assigned to a particular individual, a particular team member, and you could do that with an automation rule. Okay, so take some time to take a look at those and see if there's anything that you can leverage right out of the box. There's also a star, so you can favorite this board so that it's accessible within the your work section. It also lists the days remaining in the sprint. So this is a nice way to get a pulse on when is this sprint over? Sometimes people use the sprint name to put those dates in there. But what happens is if you ever change the dates and you forget to change the name up here, then it really doesn't provide an accurate view of when your sprint start and stop dates are. So access your start and stop dates here and then completes for it. And so when you're done the sprint, you're going to want to click complete sprint. We'll do that in just a moment to show you as an example. But let me cover a few other additional elements on this page. First, we've got edit sprint. So if I click on Edit sprint, again, I can change the name here. I can change the start and end dates, or I can update the sprint goal. I can also group my board into different swim lanes. So swimlanes are just horizontal slices of different work types are grouped by different assign 0s here, epics are subtasks. So if I wanted to do assignee, I could click on assignee. And since I don't have anyone assigned here just yet, it's going to say unassigned. So if I click on this and I assign it to myself, now you can see that I have my own swimlane with the story that was assigned to me. Or if I wanted to do epic, I could do that and just see that these are all the tasks related to the homepage. And I can click on my name right above if I just wanted to focus on the ones that were assigned to me when onClick, Nicea, everything. And then there's also subtasks. If you have subtasks, you can organize it by issues with sub-tasks. I don't really use that one at all. The primary one that I use is the epic one because you can filter again on the Epic and show an epic swimlane. And then if you want to drill in on just specific assign 0s, you can go to the very top here and click on their name. If you prefer to see by assignee, you can do that filter at the top and then filter by Epic. You'll also notice that the ability to do different things with your columns. So I've got the three dots here next to any of the columns. I can delete the columns or I can set a column limit. So let's say I want to limit my work in progress. My team is in a Kanban model and we wanna make sure that there are no more than five issues in progress at any given time. This'll help us reduce the work in progress so that we can focus on making sure we get things done rather than creating a bottleneck with taking on more work than we can handle. So I'm going to click save and you can see there's a maximum five. So that just tells me that if I see more than five and here, I shouldn't take it in. You can also notice that it will make it colored. I'm going to set the column limit to one and show you that if you have more than one in the column, it's going to color it in. And you can see here it's a little yellowish orange as she's going to highlight the fact that you've gone past your max. So really nice way to, to identify your work in progress and your work in progress limits. Additionally, if you want to track more statuses, you can create additional columns. So if I wanted to create a column that's for, let's just say testing that. And then I can just drag and drop where I'm, what that column to be placed. And there you have it. One thing you'll notice as well is the screen size here. You can see there's some empty white space over to the right. And that's so that as you add new columns, you have room on the screen. Now when you create too many columns or your screen is not large enough, you will lose some real estate and you'll have to scroll to the right in order to access those columns. If you don't like that, you can reduce this. You can collapse the project navigation by going to the top left, right next to the project name, you can click collapse and the little arrow, and that'll collapse the project navigation to give you more screen real estate to view. I personally like to leave it because I don't like to have a lot of columns and it allows me to access any of these links that I need to get to pretty quickly. And if I take my screening, just minimize it a bit. I'll show you exactly what it looks like. You can see at the bottom right-hand corner, once you get to a point where your columns start to disappear, you'll see this little icon on the bottom right pop-up that shows you how many columns you're viewing. And you can click on that and drag it side to side in order to scroll all the way to the right to see them missing columns. I'm going to remove that by just dragging it full screen again. And now finally, we're going to complete the sprint. So I'm going to complete sprint. And now you can see that I've got no completed issues. And to open issues, whenever you complete the sprint, if everything is closed, you won't see this. But if you do have things that are still in the sprint, what this will allow you to do is move the open issues to the newsprint or directly to the backlog if you no longer need to work on them at this time. So in this case we're just going to leave it to new Sprint and then we're gonna click complete sprint. Alright, now you can see the sprint has been removed. You've got sprint two on the board and it has not been started yet. Now, we talked about this in a scrum configuration. Within a Kanban configuration, there are a few different nuances here, you'll see. So let's switch over to a Kanban project. We can do that easily by just changing our project type or creating a new NextGen project specifically for Kanban. Since I'm using this one for demonstration purposes, I can toggle back and forth from Sprint to Kanban. So I'm gonna do that. I'm going to from Scrum to Kanban. So I'm going to do that. I'm going to toggle off the sprints and the backlog to show you what it looks like in a combined configuration. So it a default combined configuration. You can see this sprint days left and the complete sprint buttons are missing. Everything else pretty much remains the same except for the board name. The board name does not have the sprint. It's just a generic board name that you can rename by clicking on here and typing a new name in the board name section. You'll also notice there's no sprinkle. So with Kanban, there is no sprint goal. And you won't see that when setting this up, since the Kanban workflow is it focused on continuous development and continuous flow as opposed to sprint time boxes. So other than a few elements missing, your board essentially still works the same way. 27. Releases: And the releases section, this is where you'll find any of the release items that you'll use to slot your stories into a packaged release. Sometimes releases are referred to milestones. So if you hear that in your project management day-to-day, just know that even if you're not developing software and your team has key milestones, you can identify what these are using, a version name, and the available start and release dates. This is used for software, digital project releases where you'll be able to create versions. So let's say I wanted to create a new version. I can click on create version here. And I could call this my website, one dot o. And I could put the start date. Let's say I've began work on July tenth and and I'm going to release it in about three weeks towards the end of the month. And then I can put a description to say the MVP minimum viable product for launching my new website. We'll click save, and you can see that my website one dot o is now in my list of releases, the statuses unreleased. I don't have any issues tagged to the progress yet, so I don't see anything there. And then I see that there's the start date released a and my description. If you click on the three dots here, you can mark your release as released when it's ready. You can archive it so that it no longer is accessible within your project. Or you can edit the details that we just entered and you can delete the release as well. So what I wanna do here is I want to tag issues to this release. So if I click on the version name right now, it says that no issues were found to match my search so I can create a new issue. Here. There is a fixed version. This is the release field for issues in JIRA. So I can type in or just click on the dropdown and see what unreleased versions are there. And I have my website one dot o, so I can click on that. And I'll just say that this is the final code deployment and I'm not going to leave everything else blank. I'm just using this as an example so that you can see how it tat ties in so that you can see how it ties into the release or we're going to click create, right? It says has been successfully created. Now if I just hit Refresh on my screen, I can now see that that has been tagged and added to the release. The other way to add a release or fixed version is to directly go into your issues and tag them from your board. So you can do that in your backlog or your board and drill right into each of the issues. You can see this one has tested version, that was the other version that was in my version's list. But now I want to align it to my website, one dot o. And now I'm just going to click out of that and click on the other story that I have in progress. Click on my website 1.So oh, and now if I go back to the releases, I can see that my website my website one dot o, now has issues in progress. Well, let's say we're all done and I want to release this. Now if you have unresolved issues, it's going to pop up with a warning saying that you have three unresolved issues or however many issues that you have there unresolved, you can click on this link to take you directly to the releases issues that are unresolved. And I'm gonna go back or you can move unresolved issues to a different version. Let's say they aren't gonna go in this particular minimum viable product release. But we're going to take a few of those stories and put them in the next iteration and the next release. If we had that out there, we can go ahead and move those. Otherwise, we can ignore the unresolved issues. Sometimes people will tag stories because they are just doing manual follow-ups and checks and they like to track their stories after the code has been deployed, but they align it under the same release version. So if you have any support stories or tasks that you're going to be actively monitoring after the release that you want to tag to it. You can also click ignore unresolved issues, and that'll keep those open issues in your release version, but it will still allow you to release. It will put release date tenth, just for today's purposes, demonstration purposes, and we can say my website, one dot o released. And now if I refresh, and now you can see that it no longer shows in our unreleased filter. Now we can click the dropdown for the release statuses and we can access everything in one view, including our archive releases. If we have any archived releases, the archived release is just a way to clean up your view and move some really older releases out of the historical record for your dear project. So when you archive, you won't be able to tag stories to that particular release. If you do want to, you'll have to on archive it and then you can tag it to either any of the released releases or unreleased releases. If you want to align stories to those corresponding historical releases. The search here, you can also use this just like you did on the board. You can type in my website and just a few strings it matches and it just filters in on my version. Ok, so great tool if you have a lot of releases and you have different teams working on those releases, you can easily just find a common denominator by searching and getting a list of only those specific versions that may be a team supports, for example, and that covers the JIRA NextGen released module. 28. Issues: If you haven't the feature for issues enabled in your project settings, you'll see the link once you toggle it on. So in the project settings features, and issue Navigator, when you have that enabled, you will see when you go back to your project navigation, this issues link available. So when you click on that, that'll give you a view to filter in on your issues based on a variety of criteria. So again, this popular search issues boxes here so you can start just typing, you can start to just type in text. So final code deployment, and you can see it just filtered on the final code deployment story. It just focused on the final code deployment issue that I have here. You can also filter by assignee, reporter status and type. And that is the basic out of the box issue filtering that's available to you. Now, if you want to actually leverage some more advanced filtering, you can do that. And I highly recommend doing that because in most cases, as your projects build and as you add more teams, your backlog and all of the issues within your project can become very large. And finding specific issues can be like finding a needle in a haystack. So to leverage the event search capability, you'll notice all the way to the far right here, there's an advanced search link and you click on that. And then in there you'll see you have some additional dropdowns that you can select on. So now you can actually select across projects. You can select different issue types of statuses are there again, as well as assign 0s. But now you have a lot more options as far as assign 0s in different projects and you can look at additional criteria, so different, different fields that are available within your Issues. You can add by clicking this more plus icon and you can access by clicking this plus more icon. So for example, if I wanted to search using fixed versions, I could add that. And now you see there's a new dropdown for fixed versions that could search by the unreleased or released versions or the specific names. I can just scroll through this list and add a bunch of different fields that I can leverage to search very quickly. Now, if for some reason you need more advanced querying capabilities, and you'll notice there's a little link to the switch 2j AQL. Aql stands for JIRA Query Language, and that is the search language that's used to find all of the issues within a geo database. It's a little bit more advanced, but once you get the hang of it, it's a very, very, very powerful tool that will help you quickly find issues that meet specific criteria. So let's just click on that first sneak peak. And you can see that now this is a text search box, but it's using a particular set of logic to find things. So we say project equals and the name of the project key, which is our TK and G2 for this one, and order by the created date. So this is a basic query, but let's say I wanted to find only the issues that were assigned to myself I could do and project equals t KN G2. And now the great thing about this is, is that you don't have to know the name of the field. In most cases, it'll automatically show up here, especially as you start typing words, as especially as you start typing letters. So I can see here, assignee is available and assignee, and then when I hit space, it gives me a bunch of different operators here. I can say equals and now I can start, I can say equals. I want to hit space. It automatically populates a list of who I should choose, someone to choose myself. And when you do that, you'll see that sometimes it puts this weird number or, or other information and that is database related. So don't get hung up on if you see that. It's not very easy friendly, but it will still give you the information you need because it's using more of a database related key for that particular metadata. So let me see if I can just type in my name. You can also leverage quotations for text. So if I wanted to leverage quotes, we could do that and it's a little bit more user-friendly. So if I wanted to save this filter, it'll be much more easier to use a texturing within the quotes that is user-friendly rather than the specific ID for this element within the database that gave me that weird number. But this is an advanced topic as far as how to leverage J Q_l and search using advanced AQL, which is beyond the scope of this. But it's definitely something that you want to explore as you get more comfortable with your dear projects. 29. Add Item: The Add Item link is a very useful tool to help you quickly add reference points to any external items that might be helpful for your project. So a good example would be as I click on the Add Item in the project navigation, I can see that I can add an item to this project that's related to a shortcut. So any web link to an external website that you frequently use to support your project or a code repository. So if you have a BitBucket or a GitHub code repository to show information about your source code branches, commits, pull requests, JIRA issues, you can add that as well. So if I click on add for shortcut, let's say I want to add Stack Overflow.com as a shortcut link, I can simply reference Stack Overflow and little tooltip here it says you can start your shortcuts name with an emoji to customize its icon if you want to do that. So let's go ahead and do that. All right, and click Add. And so you can see there's a little icon there with an emoji to Stack Overflow. So when I click on, click on Stack Overflow, it'll pop up in a new tab and show me that. Okay, if this was a specific area within stack overflow that I would be able to find information that supports my project. I could do that as well. I can easily link to it to help my team access the information without wasting time. And we'll click Add Item again. And this time we'll add a repository, a BitBucket or GitHub repository that will help us show our branches commits and pull requests in directly within our JIRA issues. So in this case, I have a GitHub repository I wanna link for my personal website and I can click add and it's gonna ask me for repository link. So this is my website, a very simple website explaining what I do and some links. And I have the source code for this website in a repository in GitHub. So I'm going to click on a link and just going to call this name. I'm going to add an EIS key icon and we'll say GitHub AJ liu.com. And so I'll click Connect. And now it says nicely done, I have added a repository. So now you can see I've got a GitHub repository that has been added. So if I click on that, it'll take me directly to the GitHub repository. And now I can reference some of the commits it directly within my stories because this is connected to my repository. 30. Jira Next-Gen Reports Overview: And the reports module, you'll get access to any of the related Scrum or Kanban reports for your particular NextGen project. Now what you'll notice is that if you're running a Kanban project, which is the configuration we currently have, you will not be able to obtain burndown reports or velocity reports since they require sprints. However, if you're running Kanban, cumulative flow diagram is one of the most powerful ways to identify bottlenecks within your project and to see if your work is falling, the continuous flow, which we'll cover in just a moment. So to enable these additional reports, I can go back to the project settings. And if you go in project settings and under Features, here's where you can toggle on and off reports if you want to see the reports or not. I want to see all of them. So in order to do that, I'm going to click the backlog and then the sprints to enable my Scrum board, again, this and make sure board into a Scrum board. So keeping that in mind, you'll be using Scrum if you're going to leverage those additional reports. So going back to reports, I now see that I have the burnout Burndown Velocity and cumulative flow diagram reports. 31. Burn Up Report: The burn up report is a report that helps you visualize the sprints completed work compared with its total scope and help track progress towards the sprint completion. So the burden op, report starts at the very far left at the bottom. And as the sprint goes up, you can see this grey line here is sort of your control point for a burden report should be trending up as you progress towards the end of the sprint towards the right. So if we click on that, you'll see there's nothing here because the issues have not been transitioned in this test project. What I'm going to do is switch over to an existing project that I have so that you can see what real data looks like. Project called my digital business. And when you look at the burn up report for this, now you see some more data in here because we have historical records from past sprints. Well, we take a look at the top sprint dropped down. We can select any sprint that's been completed here so that we can get some detailed metrics on it. Can use story points or you can use issue counts. I like to use story points. And then when you take a look here you have your date range, your sprint goal, and then the completed work, the number of story points completed this sprint that's in green. And you can see down here, I've got five that were transitioned to done. And then the guideline, which is your ideal burn rate. So you want to try to get as close to this grey trending up line as possible. And then the work scope, number of story points to be completed in the spring. So in this sprint, there were eight story points added into the initial start. So I started with ten points, but then after this friend started, I also added an additional eight. So this kind of shows me that I've overcommitted to work. And that may be something that if you're looking at this from a team perspective, working with your team to identify what was taken, what can we get off of our plate and work with your product owner to help re-upped, prioritize some of that work if you have a product owner on your team. So we can see just by looking at this report, this is not ideal in any way because again, we added scope after the sprint started. We also only completed five points and around the beginning of the sprint. And when the sprint ended, there was nothing else that was completed. So reports are a powerful tool when you're leveraging agile practices. So if you're using, if you're using team retrospectives to help the team identify what's working, what's not working, and just point out some things to help the team get back on track. Something that a typical scrum master would do. But if you don't have formal roles in Agile and you're new to Agile, these reports essentially will just help you identify improvement opportunities within your teams to make sure that you're making progress using a scrum methodology. So I highly recommend if you haven't had any Agile training, it does help to get a base level knowledge of what that is. I do have some additional training available for that, but that's beyond the scope of this next-gen overview. 32. Burn Down Report: Next is the sprint burndown chart, where you can track and manage the total work remaining within a sprint. After the sprint, the summarized within a sprint, and also get a bird's eye view of both team and individual performance. And this is really important because Sprint burndown charts tend to be one of the most valuable, in my opinion and in my experience, tools to help you identify improvement opportunities within your team, especially when it comes to making sure that work is accepted and move to done and meets all of the acceptance criteria. Now, what we wanna do, again is ideally trend down towards this grey line. This gray line starts with a story point count. And by the end of the sprint, we want to get to 0. That's the ideal goal because that will tell us that we've completed all of the work that we've committed. Two, again, you have your sprint drop-down boxes here, Story Points or issue counts as your estimation field. And when it comes to. So you have your sprint goal here and you also have your date ranges for your sprint and your sprint goal, similar to the burn up chart. Now we're looking at the remaining work, the number of story points left to complete a Sprint, which is this red line. And you can see it's flat against the ideal burn rate. So this is showing us again that we've taken on too much similar to the burn up report too much in our sprint than we committed to. And we still have a substantial amount of work left at the end of the sprint. So a lot of carry over is going to occur down in the report section, you can see scope changes to the log. So this report is great because it gives you more context into what was added, what was modified, changes in any point estimation, any incomplete issues that were not done at the end of the sprint, what was completed and an issues completed outside of the spring. Ok. You also have a link to go directly into issue navigator for each of these areas. So if I wanted to look at all the scope changes, I can just click on the View issue navigator and it would pop up and bring me a list of all of those issues that had some changes. 33. Velocity Report: Next is the velocity report. The velocity report is very powerful in that it helps predict the amount of work that our team can commit in future sprints by looking at the overall past performance and previous sprints. So let's click on that velocity report. And here you can see there's again a control line for commitment, the amount of work in the Sprint when it began. So this is the amount that we actually committed to and then the completed, which is the amount of work that was actually done during the sprint. So ideally you want this to match. So I can see that sprint eight, this sprint eight name here that has a 110124 date title in the name. This was seven committed and seven completed. So this is great because this was completely on-point. What you'll be able to see is some of these sprints that, you know, you can see that there's some six were committed here and only one completed. You can see that there was nothing committed at the start of this print. So inadvertently it probably got started and there were three In, that were added in the sprint afterwards that got completed. And that at the one here where it says 21, where this Print Name is 20 dot 1.4c. We've committed to seven points and completed two story points. 34. Calculating Velocity Reports: And underneath this you'll see the actual sprints with those numbers in a more tabular view. And this is great because what you can do here is you can actually get a calculated average if you're using this scrum methodology and point estimations to get the capacity that your team can actually deliver on from an a commitment perspective versus completed, what we wanna do is calculate the number and its average. So if we're going to count all of these that say we're going to count 1234567. We have seven sprints here, and we're going to add up all of the numbers in the completed column. Let's say seven plus one is eight, plus three is 11, plus two is 13. So we have 13 completed total. So if we do the math and we divide 13 completed points by seven sprints Sabbat, just shy of two points completed on average per sprint. So that's a good number for future sprints to say, Maybe we should only commit to two points. So that way we know that we're going to deliver on a 100% of that work. And what's even better is that if we have any additional work that we can pull in, if we complete those two points before the end of the sprint, we can go ahead and pick that work off the backlog. So this is a great tool to help with identifying what your future commitments will really look like in a real-world scenario based off of past team's sprint performance. Additionally, you can click on how to read this report at the top of the report and it will, it'll tell you the team's velocity is calculated by taking the average of the total completed estimates from their last few sprints. And then you can read it how I just explained here and click on the Learn More button, which will take you to a support article to understand the velocity report in more depth, especially around requirements such as making sure that the point estimation feature has been enabled and some other areas that you may want to refresh yourself on as you interact with the report. 35. Cumulative Flow Reports: And the last one here is the cumulative flow diagram, which you can leverage in a Scrum and Kanban NextGen project type. So let's click on the cumulative flow diagram. So immediately when you click on this, you'll see that you have some available options to click on here. So the first thing that I would recommend is clicking on this how to read report, which will give you some more information on how to read it. The cumulative flow diagram shows statuses of issues over time which helps you identify potential team bottlenecks that need to be reviewed and reviewed with your team to brainstorm potential efficiencies that can be implemented to get more work done and, and work on a more continual basis. But also learn how to read the report by clicking on this Learn More link basically tells you the distance between each of these columns. These checkboxes are columns which you can toggle on, you can toggle off to compare those various transition states is how long that these issues take to get from one state to another. So the key areas you want to look for points where one band is growing at a faster rate than another to find bottlenecks. So we should always be on an even keel in an ideal state similar to, you know, we're looking at this. This is not a lot of growth in the to-do column versus the amount of work that we're completing. So it's pretty much on par, but when you want to drill into specific areas, let's go ahead and take a look at the Learn More to find out what, what more we can do with a cumulative flow diagram. So in the queue flow diagram, you'll notice some of the bullet points here. Horizontal axis represents time and the vertical axis represents the issues. So the issue count's going up and the time going across left to right, each of the colored areas are the columns, which we mentioned. You can toggle those on and off. Each of the little dots represents one issue transition. So if you're going from to-do are in progress or in progress too, in review, each of these dots represents a various state change. The key here is if your chart is contains an area that is widening vertically over time, the column that equates to the widening area will generally be a bottleneck. So you want to identify what are some of the bottlenecks within that column. So if in progress is just growing and growing and growing and growing, then that tells me that there is no work in progress limits set within the board that the team is adhering to. And then we need to look at how we can address some of the issues that have specific problems and reasons why they're not being closed out. Okay, you can look at some of the additional examples here, also some things to keep in mind. This is all based on your boards column mapping. So an issue is considered to be to do when it's in the utmost leftmost column of your board. Similarly, when issues done, it's all the way to the right side of the board. This diagram also displays data for the entirety of your project. So if you work in, if your team works in sprints, may find it more useful to use the date filter to show issues for one sprint rather than a dynamic date range. Also, if your project has backlog enabled issues and on the backlog will show up as to do in the to-do transition. Ideally, your diagram should be rising evenly, especially for except for the band representing done that should continuously get taller over time because you're completing more issues which are building up the various statuses of done because of the total number of issues within your project over time, okay, some other key things to learn from the cumulative flow diagram are visualization of specific key metrics such as cycle time. Cycle time is the time it takes to move through the in-progress statuses and become ready to deliver and Work in Progress, which is the number of issues that are actively being worked on at any given point in time. And again, you can limit work in progress on your board by setting the column limit on the very top. The board column name, cumulative flow diagram can help you get a better visualization of how much work has been committed to in any given sprint. So if you want to specify custom dates that you can do that. You can also do custom dates. You can do that by selecting the date ranges from date to date or some candidate ranges here such as past week, past two weeks, past month, past three months, six months, or all time. I'm going to select all time. And you can see that, yes, it starts out from the beginning of the project. It should be very low. But over time, that done column is growing at it at an even rate. And you can see that the bands are pretty much parallel, which doesn't show me that I have any significant issues to worry about at this point, unless I wanted to drill on a specific subset of historical data. But mostly that won't provide much benefits as we're really looking at the current work in progress and to identify immediate real-time bottlenecks and address those accordingly. 36. App Integration Overview: In this section, we'll dive deeper into some of the app integrations that are offered in your JIRA next-gen projects. The first two you see here are the project automation feature, which is basically a feature that help you automate manual tasks that you would normally take within your workflow, such as assigning someone to an issue when you move it to a certain state or column or marking issues as completed when they transition to another state. So there's a lot of different things that you can do and we'll dive deeper into those in this section. We'll also cover the slack integration. And the slack integration is something that is very powerful if you want to streamline the communication between JIRA and within your team channels to identify when new issues are created or when comments are made on issues. So that you can keep a streamlined, detailed log of all the work and keep your team in the know as issues are worked on. 37. Automation Rules: In this lesson, we're gonna take a deeper dive into the project settings app integration for project automation. Now project automation is an extremely powerful tool that can help you automate your workflow doing different types of tasks that you might normally run manually, but automate them so that you can focus on more value-added work out of the box. You can see there are some different types of rules. You have rules that are at the project level. And then you also have rules that are at the global level. To manage project level rules, you would create the rule directly within your project settings here, or edit your rule, toggle it on and off to enable it using the toggle buttons. And you can also copy, remove, or export your rule in a JSON format. The global rules are applied to your entire JIRA instance. So any project that you have, global rules will always apply. These can be toggled on and off. By default, they're all off. I'd toggled them on. And you can administer them in the global administration section. So you can click on this link. And this will take you to the global administration for your automation events. Okay? It'll show you the rules as well as the usage that you have. You have a 100 free in the free plan, a 100 executions available per month, which actually is pretty healthy for small teams. And then you can take a look and see how many you've utilized already at a high level. And then you can always upgrade to premium if you need more triggers. But we'll go back to the project automation screen. So within here, we're going to focus on our project rules. And some of the things we can do such as closing the epic went all stories have been completed. That's something that we can do very popular when you have a lot of issues. And you wanna make sure that your epics are being closed in a timely fashion. When you close the last story, it will automatically close its parent epic. Very powerful. The other thing is the label section. So when you have a label section, you can create various labels to group your rules in. So if I had one for auto assign, I've already created one called auto assigned. So you see it in the list here. I can click on that and click done. And now the label is there. Now if I want, I just saw that pop-up and it goes away very quickly. So what all you need to do to know how to get these grouped is you need to just drag and drop them. So if I wanted to create a rule for auto assign, I could do that and say that, you know, anytime in the new trigger a field value as two suits, different recommendations here and issue has created, that's the one that I want. Run the rule when an issue is created, going to click save. And now when issues created, we're going to make a new action. And here we're going to assign the issue. And we're going to assign the issue to the user who triggered the events. So I'm going to click Save. And then if I scroll over here, you can see turn it on. Now, I click turn it on without naming it. So I need to do this by saying create new issue and assigned to reporter. That's the person who created it. So turned it on. And I can see it's been turned on. And when I go back to the list, I see it's here and it says create new issue and assigned to Reporter. Well, if I want a group that into auto assign, I can drag and drop that over the label and now adds a little label next to the rule. And if I only want to look at that group of labels, I can just click on auto assigned from the left navigation or right on the label screen next to the event. And I can see only those issues related to that label. This works great if you have a lot of automations and you want to be able to quickly administer them. So let's test it out. If I go to my board here, I'm going to create a new issue. I'm going to select Create. Alright, it's in my existing project. And I'm going to say test, create, assigned. Right, right now, there's no assignee. I'm going to click create. And now if I go to my backlog where I see it says test create assigned, you can see that it's assigned to me. Now, let's say I want some real basic Board rules. I can do some of these automations without even going into the automation plugins screen. By going to the upper right-hand corner, where there's the three dots on my board. And it says Manage Rules. This is going to introduce some board level rules that I had won on. I deleted it just to show you what it looks like when you don't have one. When you don't have it, you have the ability to just add a new rule here. And you can do two basic things here. You can assign issue someone after moving it to a certain status or column. Or you can update an issue field. So you can automatically change the value of an issue field after moving an issue to a certain status or column. So if we wanted to assign an issue to someone and collect that, will select that and then choose going into in progress, going to assign it to the current user. Okay, so I'm going to select Add. Now, if I move this add header image to him progress, you can see that immediately assigns it to myself. Now if I go to Manage Rules again, I can also see there's an opportunity to update the issue after moving issue into a certain status or column. So I can say for issues moving to testing, we're going to update this field and there's a small subset of fields that you can use. So drop-down, I'm going to select priority and we're going to put the priority for this is the highest. Okay, we're gonna click Add. So now I'm going to click Close the ad primary navigation story. I'll move into testing. And now you can't see it on screen here. But if I click on the issue. You're not going to see that priority label in there either. Sometimes this happens when you don't have certain fields enabled. And so if I go back to my project settings and I go into the, the issue types screen. I know that this is a task that I created and I want to be able to view the priority. So right now this is a previous created field that I used in another issue types. I'm going to just drag and drop that and put that right in the context fields. I'm going to save changes and go back to the project. And now I can see that arrow that's showing up as highest. So now to see this in action, if I click the add header image and say it's ready for testing and move it over. Now you see the arrow has changed from orange to red. Very subtle. But now it's been changed to a high priority. So those are two ways that you can lever board rules to help automate your workflow. And if you want to go back, there's a quick lightning bolt linked to the automation section in your project settings that you, it'll take you back to in order to create more events. We can click on that and see the pop-up to select a specific trigger. To create transitioned up-to-date issues, to do branch level tasks for commits or pull requests. Any integrations for using web hooks. If you're using web hooks with your project, we can scheduled trigger rules on a regular schedule, and we can view all triggers going directly into your project settings. So for here I'm just going to select a trigger. So I'm gonna select issue. And this'll take me right to the create new automation screen in the project settings. And here I can say when it issued is transition from testing to done. And then save that. I'm going to make a new action. And that action will be to send an email. And I can type in the email address. You can use some of the the default reporter or default fields for users depending upon who's assigned to, to the issue. But you can also specify email addresses for users outside of your project as well. So I'm going to just select an email address for my email and then type in test JIRA automation. When moving from testing to W1 status. Alright, I'm just going to copy and paste the content. You can click More Options for some other advanced configuration such as who is it from? And we can say JIRA, Next, Gen demo. Okay, and then we're just going to click save. And now I'm going to name the automation is to email. When done to Danny. We're going to click turn it on. Alright, so now I have my email opened up in a separate tab. And I'm going to go back and transition the story from testing to done. When I do that, I'll check my email and notice that I have something in there. So let's see, I have the ADA header image. I'm going to move it from testing to done. Now, the automation should run in the background. And in a few moments, I should be able to click on my e-mail and I can see, boom, there you go. I have a JIRA next-gen from JIRA next-gen demo Test JIRA automation when moving from testing to Don status. Okay, so a very powerful way to quickly access your automation rules, right from within your board, as well as set-up board specific rules for columns, Status transitions. 38. Slack Integration: In this lesson, we'll walk through the slack integration setup. So click on Project Settings and then go to Apps and select slack integration. So you'll see here that you don't have anything when you're just getting started. And you may have a wizard that tells you what to click on next. Right now, I've already connected my account, my Slack account, to my AT Lassie and instance. But for demonstration purposes, we'll go and do this as if we're doing it from scratch. So one of the things you can do is if you just type in a quick Google search to how to set up Slack Jira next-gen, you can click on the support link, used your cloud for Slack. This will take you to the help article for step-by-step instructions on how to set up Jura cloud for slack. And here we're going to get started with the first step. How do I add your cloud app to my Slack workspace? Click here on this link to start setting up gcloud for Slack app. And it says that once you login with your last seen account, you'll get a direct message from the JIRA cloud app in Slack. And then from there we'll be able to connect our first year project to a Slack channel. So we'll click on the link and it'll ask you some basic permissions, actions cook, which you can expand the arrows just to get a little more information on what kind of information do your cloud will be able to view and then click allow, and then finish integrating slack enduro by logging into your last seen account. So we'll do that and we have a success message that GO cloud is now connected to Slack and we'll click go to Slack, and that'll take us to slack in our browser, but we can also open the Slack app. I'm going to open the Slack app that you can see in your slack account. There's a section called apps. And if you look at that, the bottom left of the slack navigation pane, you can see that I have google Drive already installed, but also have this additional application for JIRA. So now you know that is, has been successfully installed to your slack account. But we're not done just yet. The next step is, well, how do I connect a Slack channel to mind your project? So after you set up the gcloud app in your slack workspace, which we already, which we already completed in the previous step, we can set up a JIRA Cloud Project and particular the NextGen project that we're using to send notifications into a Slack channel of our choice and a variety of ways. So the first way is if you want to go and connect to agir project from within slack, you can do that by typing slash JIRA connect within any public or private channels. To just keep in mind that this functionality is not supported at any direct messaging with other Slack users. It's only supported in the public or private channels. So let's go to Slack and type in slashed JIRA to quickly set up a connection between RG or cloud and slack. So I'm just going to copy. This command. And then I'm gonna go in and just create a new channel for demonstration purposes. You can see in my general channel, I had already previously configured juror cloud and I disconnected it. So let's go ahead and create a new channel. We're going to call this JIRA slack integration. And we can just leave it as is and it's right now is public and click create. And we're going to skip adding people for now. And Alice is the start of the channels. So let's in our clipboard, if you copy the command, paste it directly in and hit enter. Now you can see that Europa is asking us to select a project. So from here we can select a project that we want to connect two. Now if I go to test Kanban next-gen to, I can also select which channel directly from this channel, even though I've posted the command into the gyrus lack integration channel, I can configure this to connect to any of the other channels that I have, which is really nice in case I pasted this command in a channel that I didn't intend to connect directly to my project. But for now, we're going to leave it checked his juris lack integration and then click Connect. And you can see now that if added a project connection to this channel for test Kanban next-gen too. And I'm going to click on that link and show you directly within the NextGen project where the settings now show the connection. So now you can see that I have a workspace and the channel connected, it's ended its active. Now let's go ahead and delete this. This time, we're going to add to connection directly from within our project settings panel here. So this is the way that I tend to add the channels because mostly in JIRA anyway, you can just go into the slack Integration Project Settings, select the workspace since you've already connected your slack account in the very first step this lesson, and then select the channel that you want to connect it to. So we'll select the gyrus lack integration again, we'll add it and you can see we quickly added there. So let's go back to the slack. And you can see it's been added again here. The first time was directly within slack, and the second time was from our project settings in our NextGen project. So now when you create new issues, you can get notifications directly within the channel. So I'll click Create and go back to the channel. And you can see that this channel says that the test slack notification issue has been created. Notice I didn't get a pop-up on my desktop application. This is more of a slack configuration and you'll need to go into the Slack channel itself to setup the notifications. If you want to get notified directly on your desktop, if you've set up notifications properly and you still don't receive pop-up notifications. You want to make sure in slack that you are not in a do not disturb mode. So you can go into your account by clicking on your name next to these circle of the status that you have here it says active notifications snooze to see a little z. Like you're sleeping. You're gonna click on that and we're going to make a notification change here. So it says Paused notifications, but it says Do Not Disturb notifications pause until 08:00 AM because I am recording this at 07:00 AM. It's not going to show any desktop pop-up notifications. Secondaries turned us off temporarily. So you can see now I am full green circle of active. And if I go in and create a another task, it should pop up in the upper right-hand corner of my screen. Okay, so I'm gonna go back and my juror NextGen project, I'm going to click on Test notification to I'm gonna click Create. And now you see in the upper right-hand corner, a desktop notification has popped up as well. 39. Loom Video Screen Capture: And one application that's not provided as a native default application integration is called loom. I'm covering this because for those Google Chrome users out there that love to record videos and share them with their teams. Live is a great way to say it with video. So if you're trying to maybe do an over their shoulder screen capture to show your team members how to perform a specific task or a deep dive into particular lines of code, along with an explanation, is a great way to capture that information and share it directly within your JIRA issues. So you can get started for free. There are some paid options, but I use a free account and it's really nice to quickly get that information in a JIRA issue. What's great about it is that you can get the plug-in for Chrome. So if you click get loan for free, assignable Google or slack to set up your account. Additionally, if you want to access the loom setup instructions, you can go to the loom page right here listed there's a blog article for JIRA at the JIRA integration. Or you could just type in JIRA loom. And that should give you limb is now available in JIRA. When you click on that and go to the blog post, it'll give you a setup instructions on how to get loom set up using the Chrome extension with links to the Chrome webstore to download it. If you drill into any issue, you can see, you don't see anything as far as loom is here. But when you click on the description, you can record a loom and just click record. And then it'll put you kind of camera here in the bottom right or bottom left of your screen. You can drag and drop the camera view. If you want to put yourself on camera. If you want to take yourself off of camera. You can also do that by just clicking the X, and that'll remove the camera view and just have the screen only. So right now I have screening cam. I'm just gonna click screen only. And, or you can do camera only and then it'll switch to just the main camera, so of screen only. And then you can click, start recording. I'm going to click my entire screen and then click Share. And then you can start speaking. This is a test for recording a loom inside your issue. Okay. When I'm done, I can click on Finish Recording check part, and then I can just insert the loom right there. So again, a very powerful way to quickly add over the shoulder screen views or ex, explanations that just don't quite go well over text or email or any other form of communication. So this really helps you kind of streamline your productivity within your teams. And I can play it right within the description. And then you can start, start speaking. This is intestine for recording and Lou, inside a gender issue. 40. Scrum Case Study: Building a Simple Static Website: In this lesson, we're going to cover a case study for building a new Scrum project that will help us build a simple static website for a personal brand. So this'll be the most extensive of the case studies as we will be creating a project from scratch. And you'll get to see an over the shoulder view of all of the steps it takes to configure a project using the various settings and configuration strategies that we've used in the previous lessons. We'll also cover a few other case studies such as a Kanban case study and an additional automation case study based on a few projects that are already in flight. So let's create a new Scrum NextGen project on building a simple static website. And want to refer to a simple static website. Basically, this is a web site with webpages only. There's really no dynamic functionality to it, such as back-end calls to a database or other features that would make it more of a web application. And keeping our eyes on what the result will be. We'll take a look at, this is my website for my personal brand. As an agile leader in course instructor. It's a simple static website with a few basic links and a description of my bio. So to create a new project, go to projects when you create project, and we're going to select NextGen. And I'm going to call this my personal website. And PW is the key is fine. I'm going to change the template to Scrum and click Create. And as we go through this project, if you want to follow along and create your own project for your personal website, I highly recommend you do that. If you don't have a personal website yet, how this would be a great way to showcase your skills regardless of what role you play, maybe your project manager or some sort of Agile professional or a software developer, you can be creative and create your own website. If that's something you're looking to do. Now that my personal website project has been created, you'll see that I've got pretty much a blank slate here. So before I get started with putting things in a backlog, I'm going to configure a few things that I want to see out of the gate. So I'm going to project settings, I'm going to issue types. And because it's a Scrum project, you'll see that I do have these available bugs, story and task issue types here available to me, along with some of the Story Point fields, sprint fields, labels, and assignee. I'm not going to add any additional fields. That's something that can be added later. I'm just going to leave that as is for all of my various issue type's going to leave the icon. I think that that's totally finally that I'm going to take a look at access. I don't need to grant access to anyone else. Notifications I'm going to leave as a default my features, this is where I really want to focus on. I want to focus on toggling some of these additional features such as reports, so that as my sprints are completed, I can start to view some of the historical work and estimate my capacity to ensure that I only take on as much as I can actually complete for future Sprints. I also want to take a look at releases and versioning because I'm going to put out a version for my initial launch from my website utilizing all of the stories that contribute to that release, I'll also toggle on issue navigator in case I want to search for Issues. And we'll leave this on call blank. This is for a plugin called Ops Gini, which I disabled. So you don't need to worry about that unless you're using ops Jeannie. And then I'll go back to the backlog. You see I've got nothing here. And then we'll start at the roadmap. I like to start at the roadmap because it gives me this way to kind of canvas out the high level work that needs to be completed. And then I can break down stories that support those epics as I move through the project. So in this case, we are building a website. So what needs to be done? So when I look at this, I look at this on a page by page basis for a static website. So the first thing is a homepage. Wanna create a homepage. So if we can take look, I've got a homepage here. And really that's all there is for this site is a main homepage and then there are some links to some external areas such as Linkedin for social, Twitter, GitHub account, or courses on Udemy. And I do have an internal link here for online training, which is just another page that gives direct links to the, some of the courses that I teach on Udemy. So for now, my minimum viable product is not going to include that page is just gonna be this symbol. It's just going to be this simple one pager that you're looking at on my screen. You can see down here there's a credit, copyright credit here to a split template by a designer called one-page love. And this is a Go template for a one-page website. So I'm going to go back to my project and just say that create homepage, really this is my, this is my, my minimum viable product. So create homepage for my MVP. Right now I've got the epic here. I can set a target timeline of when I want to have this completed. So let's say that I want to have this completed by the end of August, will just drag and drop that. And now I have my start and end dates there that it create additional issues. I can create them directly within my backlog or I can create them on the roadmap. I like to create them on the roadmap initially to help me get a good view, to help me get a good top down view of all of the things that need to happen. So it doesn't really matter. You can choose the roadmap or the backlog to enter this information. I'll show you how to do it in both. The first story I'll enter here is choose a Web site template. Okay, gone are the days of coding HTML and CSS from scratch to build a website. You can totally do that, but there are so many different options to leverage out there for website creation that you can get some simple templates that are available for you to manipulate and apply so that you can get a quick professional-looking site up fast. So I'm going to choose a Website Template. And then I can see that that is directly linked under this epic. But I'm going to also say that, you know, what if I created a few stories already? And I'm already working in the project and I go to the backlog and I want to create an issue really fast. I can do that here as well. Now I can click Create Issue, and here I can say upload a professional headshot photo. Okay, now you can see here, when you add stories in the backlog doesn't link to an epic automatically. So that's one of the reasons why I prefer using a roadmap because I can automatically set it under an epic of my choosing. So not the end of the world. If you click on the three dots next to your issue, you can always add a parent link. It's just a few extra clicks. And then you can choose a parent drop-down and select the right epic and click Done. So we've got that. So we've got choose a website template, upload a professional headshot photo, add in, bio, add-in, main, heading and bio. And let's take a look at the site. So we have our main heading, or bio and the image. And I'm going to say, let's put in external links to the website. So I'm going to group all of these links at the bottom down into one story. So I'm going to say add in external footer links, social, full social, My Work Connect. I'm going to add a parent, choose a parent issue for this click Done. Now, if we switch back over to the road map, you'll see that the roadmap only has these three items in it because I don't have anything tag to an epic for the most recent story at an external footer links, you won't see it on the roadmap until I actually add that within the backlog. So that's one thing to keep in. Notice that if you add stories without epic, without parent epics, they will only show up in the backlog. They will not show in your roadmap. Okay, so we'll go to backlog. And in here I'm going to assign the parent link create homepage. And now if I go back here, you should see that issue added as well. There it is at the bottom, you also see the status to do so the zonal in introduce status. Now I'm going to switch over to the backlog and we're going to create a sprint. Okay, you can see that it created a sprint. And, and now I need to drag and drop some issues into this sprint. So let's say I'm going to initially choose these first two stories. In my first sprint. I'm gonna leave the other two in a second sprint, so I can create another sprint for that and add these two and another sprint. So we can see I've got sprint one sprint too, and I don't have any active sprints yet. So if I go to the board, I don't see anything yet. So I need to start the sprint so that I can see them within my Scrum board. But there's one thing I'm missing. So before I start to sprint, I wanna make sure that I have these stories pointed because if I don't, it won't add anything to my reports such as the burn up in burndown reports or sprint velocity. So I'm going to go in here and click on the story and give it a point value. So let's just say for demonstration purposes, I'm going to select one. For choosing the website template and another one for a story point estimate. And so I've got two points in the Sprint. You can see the two story points in total and no protozoan progress and no done. So let me go ahead and click on the three dots here because I want to add in a sprint goal some going to edit the sprint. I'm going to say by the end of the sprint, I want to, by the end of this sprint, my web site template should be selected and a pro image added. Ok, so that's a nice sprint goal. Now this sprint, my website templates should be selected in a pro image edit, update. And now you can see that I have a sprint goal here for sprint one. And I will hold off on that adding a goal for Sprint two. Because when I get to the end of my first sprint, I wanna see if actually meeting that goal. And if I am, I can add a new goal here in Sprint two. But if I have some carry over work, I might want to carry that over into sprint two. And therefore I'll need to add that as a goal for Sprint two. But for all intensive purposes, let's click on Start Sprint to get our sprint finally started. And we're going to keep the duration of two weeks and the default start and end dates. You can always change these, but I'm going to leave them for this video. I click start. And now we've got our issues in a to-do column on our Scrum board. Okay, it's just me in this project, so I'm not going to mess with any groupings or anything like that. But you can see here, I'm going to pull in, Choose a website template that's in progress. And I'm gonna go back in the project settings. So we have all of the features enabled that we wanted. Okay, I just had to refresh the screen and the reports link is now showing there, as well as the issues and releases that we've added. Sometimes if you turn on different features and you don't see them in the project navigation, the best thing to do is just click refresh and you should see them show up once you do that. So now that I'm done with the backlog and moving some stories into a sprint and starting the sprint along with a sprinkle. Now I can go in, take a look at the releases. So I wanted to look and see, I want to create a version for this and this is going to be MVP launch for Danny J.com version one. Okay, you can come up with a description if you'd like, and then just say this is the initial launch, including homepage, image, bio, and external links. Okay, so you can see after I hit Create, the version has been created and I don't have a start date or release date. These you can enter by clicking Edit on the three dots and the far right of your version, you can select a date to start. I'll select the date I'm recording this video and then the release date. I'm going to select August 31st. Click save. And now you see that you have a release here, but there's no issues tag to the release. So let's go back and fix that. If I go back to the board, I can go right into each one of these issues and tag them to a fixed version. And we can see there's the fixed version. And fixed version is just another name for releases. And it's the field in your issues that you can find your release name. And if you don't have one, you can create a new version right from within your issues as well. So I've tagged that one. Now I'm going to tag the next one. Alright, now if I go back to my Releases tab and I can see that I've got one issue in progress. And if I click on the release, will get more information. And I can see there's a total of two tag within that release and the report section, you'll notice I don't have any data except for the actual start of the sprint. So I've started the sprint with two points that I've committed to. And I've got a burned chart here that starts at 0 and it moves all the way up to the two-story point counts. So by July 25th, both of those should be completed. You should see this line starts to increase as stories are completed. The burndown chart, so same thing, it's just opposite. So we've got a total of two points committed. But now we're going to see the work burned down as we move across the sprint all the way to the end. So we should see stories dropping off of this chart, wants the sprint is closed out. We can also take a look at some of those scopes, changes, a complete issues in more detail as we get closer to the end of the spring. And then the cumulative flow diagram you can see here, these are all of the issues that were created. So into the to-do column, you can see that there are five issues in total. And you can also see that there is one issue that was moved from to-do to in-progress, and they also have a Github repository. So I can go in to add item in the project navigation. When I click on that, I can add a repository to GitHub by clicking Add. And here's where I need to put in a link in the name. So if I go into my GitHub account and I can click on my repository and just leave the name as is. And when it clicked Connect. And I can see this is my code repository right in the navigation pane. If I want to rename it, I can click on this and say maybe I want some more description to say that this is a GitHub repository for Danny J liu.com. And we'll click Update. And you can see that if I drag and drop a little bit more, there's the full description. I'm also going to add an item to the domain name, the direct name for my website. So I can take a look at that and refresh it as well as I move through the project. So a shortcut link I'm going to use and when you click add HTTPS, AJ liu.com, and there's can put my production website. Ok, so now I've got that link. So if I click on that, it's going to pop open a new tab with my website in there. Okay, so this is great, again for reference points to help you quickly access resources related to your project. Now, let's say our sprint is just about closed. You'll see up top here, the top right, it's a 0 days remaining if you're at the end of your sprint, in which case you can complete the Sprint. And we're going to pretend that that is the case. We're going to complete the Sprint and I'm going to put in, I chose a Website Template. However, there's still one in progress story for my headshot photo. Ideally speaking, you want to have all your stories done in Scrum model. But there are times when you don't complete everything, life happens, other things get in the way and you aren't able to finish everything. So we're going to click complete spread. And it's going to say the spring contains one completed issue and one open issue. I have the option to move issues that are still open to the next sprint or directly to the backlog. So the reason you might want to move them to write directly to the backlog is if your priorities change and those issues no longer apply to the upcoming sprint. But in this case, uploading a professional headshot and photo is high priority in order for me to move forward with my project. So I'm going to leave, move open issues to the second sprint and then click complete sprint. And now spirit one has been completed. And when you look at the backlog, you'll see sprint one is no longer viewable and an additional story has been added into the scope, which was the carry-over story for uploading a professional headshot and photo. And let's take a look at the reports. Now if I look at the burn up report, it's still going to show the same information. And the reason for that is is because the day is still today. I started it and stop this sprint within the same day. So you're not gonna see anything here. But just note that if this were the end of the sprint, you would see in the burn up Report a line zig-zagged, going and trending up. And again with the sprint burndown chart, you'd see something similar with it trending down. And then you can take a look at some of the information as far as scope changes. If you add anything to this sprint or incomplete issues that were captured at the time of the sprints starting and any completed issues. Now let me just refresh this. There we go. Now this looks a little bit better, okay, again, so there is a perfect case in point where sometimes you have to refresh in order to make sure that the data is accurate and up-to-date. So if I go back to the burn up report, I can see there was 1 that was ended, the sprint ended, and 1 was completed. Total of two issue counts. So I can see this print started the sprint completed, and I can see how many work completed and the total scope. So I completed one out of two. And again, that line would trend up if we were actually two weeks from today instead of stopping and starting on the same day, let's take a look at this sprint burndown chart. And here we can see we've got sprint one selected since that's our only completed sprint. And now you can see the burn down goes downward to show that story 0.1 was burned down and there's a total of two issue counts and the Sprint ended. So again, it's trending down, but it's only within the same day, so you don't see it going across the graph from left to right. You can look at the scope changes. There are no issues that were added in scope. You can see that the incomplete issues were the one story for uploading a professional headshot with a value of 1, we can see what we completed and there are no issues completed outside of the sprint. Okay, so let's go back to the project. So let's take a look at the cumulative flow diagram. Accumulo flow diagram shows us we have now a done status since we moved the one story to done. So you can see our cumulative flow diagram starting to take shape and over time, your done column is going to grow. So you want to see that steady growth over time because cumulative flow diagram is just that it's a cumulative view of all of the statuses over time within your project. But you can also select some specific date filters if you wanna look at just a subset of the data, if you just want to look at a slice of the data from specific start dates and end dates. And this works great, especially if you're looking to target different sprints. See what transition statuses your stories were in throughout the sprint to help identify bottleneck. Now if we look at the velocity report, we can also see that in sprint one, I've completed 1 and I committed to two. So committed to, to in gray and completed one in green. And as this builds up over time, this will help me create an average of how much I'm completing across sprints so that I can better estimate how much I can commit to for future Sprints. And that covers all of the reports as well as a completed sprint. And let's say we've finished all of our issues and we're ready to finally released this. Well, we want to make sure that we're looking to see that all these stories have been completed. And within here we can mark the release as released, so we'll click release. You can see here it's giving me a warning because they have some unresolved issues. You could ignore them or you can move them to another version if you have another version. In this case, I'm just going to ignore the unresolved issues and we're going to leave the release date and click release. And now the release has disappeared from our view. If we want to find it, we can click on the release status and include the released items who can see has been released. And that's the use case that you can leverage for operating a scrum model, for building a website, leveraging some of your source code repositories. And, and there's just so much else that you can do with a Scrum project like this, especially if you're building software, you can leverage some of the more advanced integrations with GitHub, such as smart commits and actually tagging your source code to automatically linked to your issues. That's the beyond the, the scope of this lesson. But just to give you a look into some of the potential that you can really leverage to streamline your software development and website creation project. 41. Kanban Case Study: Building an Online Course: In this lesson, we'll cover the Kanban case study for an existing project. And it's the project you're looking at right now. And that is building an online course. And in this case, I'm building the online course for the jeer at next-gen projects for Agile teams. So you can see I've named this project course development, and this is really just an ongoing project for any of the courses that I develop. And I have got a roadmap here that I've created with an Epic. And the way that I have structured this is that each course will be an epoch. So this is my JIRA next-gen course. And I've got all of the lectures that I have created and recorded in various statuses. And so you'll get a chance to take a sneak peek into how that workflow is working for this course. And if you are an online course creator or you work with e-learning content, you can also borrow some of the methods that I'm using to help create your own workflow. So you'll see that I've got a dependency link here as well. Dependencies can be linked by dragging this dependency link and dragging it over to another epic. So in this case, this link is here. I can remove this as well. So if I click on the actual link, I can delete this and unlink it. So now it's not there anymore. And then if I want to re-add it, I can just collapse this. And I can just select the link from the end to the start of the marketing. And that one didn't take shapes. So I'm just going to click the link here and then put it directly over the epic. You can see now that there's dependency linked and you can just hover over the line, click it to view the details. And it says, the course has to be completed before the marketing, of course can happen. Now, this is, this may not fit your marketing strategy. Some people like to market things before they build them, and that's okay. But this is just used for a demonstration purposes to say that one thing cannot happen. To say that one EPA can't be started until the other one's finished. And now you can see it's red because there's overlapping work here. If you want to move it out of red, you just need to move it so there's no overlap and dates. And now you can see as sort of grayed out and then it turns purple when you highlight on it. Okay, now let's take a look at the Kanban board. Again, there's no sprint stop, start or anything like that with a kanban board is just using a board, very simple with different statuses. Now for my course creation statuses, I like to have a backlog of all of the lectures that I need to do. I need to start recording, working on. And so once they are recorded, I moved them from recording to editing post-production. You'll notice that in the recording column I have a maximum one work-in-progress limit because I can't really work on two at the same time. If I did have a two-person team doing recording, then I probably could bump that up to two. But really this is going to be a work-in-progress limit of one, since I'm working as a solo team here. Now we've got the editing post production column and all of the lessons that are ready to be edited and post produced and cleaned up for adding to my course. Upload on the various course marketplaces that I published two, I'll go ahead and complete that work and then move it to done when it's ready to be released. So speaking of releases, the release for my next gen chorus, one dot o has been created and all of the stories had been tagged up. So it's 35 and progress. And there's two that are done with videos already uploaded. So you can see that this is the release. It's a nice way to group everything together with a target date for release. And right now I have an aggressive date for August seventh to finish all my post-production tasks. And this will be the MVP course launch of the dura. I can also take a look at some of the reports here, really only one report and that is the cumulative flow diagram, Kanban report. And you can see how the various statuses of my backlog, and you can see the various health flows of the different transition statuses within my backlog. You can see that to do column built, I've created about 40, just over 40 issues over time since July third, and that's when this was stood up. This project was stood up. And you can see the various statuses that these issues have entered. So you can see that some of them have been stuck in recording. Not too many. This is great because again, I have that work in progress limits set. So recording really shouldn't be very thick. If it does, it means I'm violating work in progress limits. You also see the editing post production column here and now that's growing and it's getting really big. So what is this telling me? This tells me that there's a potential bottleneck in that it's, nobody's picking up that work in the editing post-production column. So it's going to be more waterfall, a more of a waterfall approach and a big bang approach to getting anything shipped to production. Now, this may be a cause of concern for some that are building applications that need to be pushed out to production in a more continuous integration and delivery perspective for the course, everything that's in the course is essentially part of the minimum viable product. So all of this stuff has to get done anyway. But what this does tell me is that it says, hey, you know, you're you're having bottlenecks here because you're the only person doing all this work and you're batching the work to do all of the recording work first, and then do all of the editing work before you can move it to Done. So this is an opportunity and perhaps hiring someone out to do some of that editing and post-production for me, which I plan on doing. So we can see this cumulative flow chart in the future and start to level off as things start moving to done once I start hiring some more help. So great way to look at your health, your flow, as well as gauge and assess whether or not you'll meet your target delivery dates based on your current team capacity and whether or not it's a cost justifiable to hire someone out to get things done so that you can ship earlier rather than later. And that's a case study for creating an online course using a Kanban methodology. 42. Saving Time using the Bulk Editor: So you want to make some changes to more than one of your JIRA issues. That can be a daunting task, a very challenging task to do if you have a lot of issues. If it's just 12 or three, not a big deal, you can click on each one of them and make the same change. But if you're looking to make the same change for a lot of I'mm, going to use an example here. I've got 31 here. You're going to want to use what's called the bulk editor. And so in order to access the bulk editor, you need to make sure that your project settings shows the features enabling the issue navigator. Since I have that toggled on, you'll see in my left navigation bar here, I have the issues link. I'm going to click on that. And in here there's a sort of a basic filtering view that you can use and you can search issues with any strings of text who they're assigned to, reporters status, type. And you wanna make sure that you you hone in on the issues that you want and then you can bulk update. So right here you can't see the bulk update feature. What you'll need to do is click on advanced search. Now you can toggle between the Advanced Search or the basic search depends on what your comfort level with searching using the advanced J QL function is. But you want to switch the basic if you wanna do something more basic, or if you know how to search for the issues that you have using SQL, you can do that as well. So for this particular, for this particular one, we're going to use basic. And we're going to select all standard, all stories, all the stories that I have right now and right now, projects not big. So I know there's 31 Stories. And let's say I want to assign a point value. Click on this three little dots operations and it'll show me bulk changed all 31 issues. So when I go in there, I'm going to select all of them. I'm going to choose operations. Now the key about the book editor in next ten projects is that there are some limitations. You can't bulk edit every single field. And so when you click Edit issues and next you'll see what you can and cannot edit. So there's a limited amount of things that you can edit versus using classic projects. If you use a classic project type, there's a lot more that you can bulk edit. So a good example would be my parent link. So my parent epic. This does not allow me in JIRA next-gen to bulk edit the parent epic link. So you have to do that manually. It's a bit of a pain. So that's one thing to call out. You'd want to leverage the classic projects. And in particular, if you're looking for roadmapping, there's a juror portfolio functionality that you can make those changes. Or at a minimum, the JIRA classic project types should give you the ability to edit that. So that is sort of the caveat with that. I just got done updating all 31 with a new epic link. So it took a lot of time. Alright, that said, if you want to make a basic change to any one of these particular areas, you can go ahead and do that as well. So I have, I want to make a change to the story point estimate. And let's say, I know that all of these are point of value of one. I'll go ahead and click on one. Click Next. I see and can review might change for the story point estimate to change to a value of one. I'm going to click confirm. And the bulk order editor will run and add 0 value of one to all 31 issues. Now when I acknowledge this, I can see that there are there's 1. I can see that there's 1 in each of these now you can't see that in this view here. But what I'll do is I'll enabled the column view so that you can see the story points. You can scroll through or just search by typing in story point estimate or story points. Okay, so the story point estimate field shows a value of one across the board. And that's how you would leverage the book editor. 43. Update Labels and Parent Epics for Multiple Issues: In this video, we're gonna talk about how to bulk edit using the next-gen boards. So one real cool feature that you can leverage here is if you quickly want to add a label or change the parent epic to his story, you can hold the command key down and select multiple stories in a column or multiple columns. And so here's how we're going to add in a label for a handful of lessons here, up to lecture five that are all related to Section one of the jeer next-gen course. And so I'm going to click on one of these. If I click without command, it's going to pop up and that's not what I wanna do. I want to hold down the command or control key command if you're using the, using a Mac. And so you're going to click that and then you can see it just gets a dark shade of blue here. And then select the ones that you want. So not only can you select the ones in the same column, but you can select them regardless of what column there in. So I can click these four. And then I have an option here where if I click the three dots on any one of these, since they're all selected, it'll say actions for, and the two actions I have are adding a label and changing apparent. So if it's one of these, then you're in good. You're good luck because you can edit them. So these are the only ones that you can edit as of this recording. But maybe in the future we'll add some more. But this is a great way to add a quick label to multiple issues or to change multiple issues in, align them underneath the same epic. So here we're going to add a label, which is going to click it. And I'm going to type in section one, just make sure you don't use spaces for labels because it doesn't like that, it'll throw an error. So if I were to put section one and then Enter, it'll just say that spaces or invalid. So I'm going to just cancel that and then type in section one. And there we go. It's all green. Click done. And now you see on the cards says section one as my label.