In this lesson, I would like to give an overview of a very popular agile tool called JIRA. So JIRA is built by a company called Atlassian. It's a quartered in Australia. It has offices around the world, including many in the US. It's, like said it's one of the most popular agile project management tools. It also includes other products, which can be integrated with JIRA, Confluence, Bitbucket, HipChat, and others and you can visit Atlassian site to get some information if you want to get more into it conference is basically a documentation tool that basically works with JIRA.

But also many add ons available in JIRA has its own marketplace if you go and there are many Free and, you know, subscription based add ons that are available from third parties. Other than installation that you can subscribe and add on to JIRA to make it more powerful. So here's kind of a little bit about Cheeta. The the main components of JIRA are the following three issues. Everything kind of revolves around issues in JIRA, and we will see that in a minute. Again, this is a very high level overview, but I just want to make sure that you have kind of an understanding of JIRA that hopefully will get you going with the tool, if you will.

The next one is a project and then the following on is the third one is workflows. workflows is basically kind of working with the issues so it's it's built around the workflows are built around the issues and issues are part of a project if you will, so issues can be further delayed. That there are different types of issues, JIRA can act as a bug tracking tool. So hence, you know, the issue can be just that type of issue can be just issues or issues. Another issue type can be epic, or stories that you aren't familiar with from from the scrum, if you will. So an issue can be a type story, or if it's a big story, then you can make it and a type epic, if you will.

And then also tasks which are basically, you know, the activity work packages for stories, the activities that need to happen in order to accomplish a story. So you can have all these are types of issues, if you will. So you can basically define and create an issue and assign it a type issue, epic story, tasks, etc. So that's, that's a little bit about issues. Now. There's a hierarchy of the different objects that you haven't used.

You have a dashboard that basically kind of gives you an overview of all the projects that you have access to. And this is a customizable dashboard, you can basically subscribe to the system dashboard that the admin is customizing, or you can basically create your own dashboard or multiple dashboards, if you will, that can, you know, capture that can summarize the viewpoint of the different projects or what have you in dashboard, as you'll see in a minute, but there are other, you know, different gadgets and you know, some are basically a patient gadgets out of the box, but there are others that you can basically, you know, that are provided by third parties that you can subscribe to as well. So under dashboards that are projects, and under projects, you have the backlog if you remember the product backlog that's under a project, and you also have sprints and as we know from Scrum that are associated with project as well.

Backlogs as you can imagine, are going to have stories which are issues. So you have issues as part of the backlog, or within a sprint, you're going to have a sprint backlog and the sprint backlog, in turn is going to have issues. So that's kind of a high level hierarchy of JIRA. Here are the things that are associated with an issue. We talked about workflow already a little bit. Basically, workflows are associated with issues.

So out of the box, basically, you have a rough drop off to be completed, if you will, new tasks, if you will. And then the next one would be in progress. And then the final one would be 10. Done. So that's the workflow so new in progress and done is an out of the box workflow that is available from JIRA, you can customize it but that's basically associated with an issue that you know if an issue is a new issue, or if it's in progress, or if it's completed. Also, you can have labels for the issue so you can basically live a day as you please.

So for example, maybe kind of a, you know, if you want to categorize the issue a certain way that, you know, it's associated with, you know, maybe kind of a supplier or a vendor, you can basically label this as a vendor type issue, if it's associated with something else that you want to categorize that you can create a label and you can basically associated with that, that issue with that label. Also, you have version so basically, the release version that this issue is part of that this is that this issue will be going live with that release or should be completed with that definitely is that's a version of that release, if you will, that is associated with that issue. Type is what we just talked about, you know, that an issue can be of type issue, it can be epic, it can be story or it can be a task.

That's that's type priority as as you can imagine. That's basically how important this issue is high medium low priority. If you You can also customize the priorities to have like Moscow, that'd be talked about must have, should have could have would not have, if you will, you also have points that are associated with an issue. So all these things are basically items are the main items that are associated with an issue of evil. There can be others that issue detail, title, etc, but these are the main items that are associated with an issue. workflow also, as I mentioned, that, you know, I mean, out of the box, it has new in progress completed, you know, workflow statuses, so the status are part of a workflow.

Again, as I mentioned, those are customizable. You can add more statuses if you will. So, you can basically for example, add a new status, in code status, you know, in QA status, complete status, so you can add different status. Within, you know, the workflow, if you will, and you can basically define that the what service comes before, you know, the next status, etc, if you will. So you can all customize that you need to have admin level privileges in order to do that, but that can be done. So that's kind of just a, an issue hierarchy, if you will.

Here's a typical workflow, like I mentioned that this is a you know, out of box you can have, you have like a to do status in progress and done in you basically can go back and forth between these statuses. So that's kind of a high level overview of JIRA, and you know, through PowerPoint. Now, here's a link to it lations site, if you will, that you can basically sign up for JIRA if you want. You, you can sign up for a trial version. You don't need to have credit card if you will, that you need to provide, if you will. So next I'm going to show you a high level demo of it.

And and also how to sign up for a trial account.