Jira Beginner: Filters

Transcript of the free preview lesson. Remaining lessons unlock with the full course.

Hello, my name is Josephine Cheetah and in these lessons, I will show you what a filter is and explain how to create a filter. Let's get started. We can get to our filters quickly by going to our top navigation, clicking on filters, and let's start with the filter for the JPK board. Once you launch it, it will open with what we call the criteria. What is a filter? A filter is a way to search and find data within JIRA. I have a total of 25 issues, 1 through 25 are being shown here now. This button here is a refresh results so that as we start to limit the criteria for each filter, we can refresh the results without reloading the entire page. One is start off with the navigation. As you can see along the left, we went through our filters through our first. You can view them all or all the issues. You can also get to your filter screen by searching and there are some defaults that are already built for you. Sometimes, I like to start with them. If I go to my open issues, the criteria fills out automatically and then I can start to customize my filter from there. Let's go back to search issues and now we have all of the issues in our entire JIRA instance that includes all of the projects. If I click on projects, I will see them all here and I can limit my filters to only see issues from one project. Once I select my JPK project, now I'm back to only 25 issues. The next fields will go through each one left to right and then we'll go through our menu items across the top. So let's continue with how to create a filter. So we're starting with one project and we'll look at the benefits to this as well. The type is the issue type. What type of issue do we want to look for? All of them? All of our subtasks? Or perhaps you only want to pull up the stories. You can select it, click it. As soon as you select story, you still now have only 18 issues. You don't even have to refresh your results, JIRA does it automatically. So if you watch I have one through 18, I come back, I unselect stories and now I'm back to 25 issues. Let's keep filtering to go through all of the fields. We have our status. Perhaps you only want to see the items that are in progress, in QA, or need to be done. And you don't want to see completed issues. You may do this to help find out all the tickets that are open at one time. Now we have 23 open in one project. That means two issues are closed. So if I clicked on in progress and I clicked on done, I'd come back to 25. And if I unselect all of my other issues, you'll see I was correct. We only have two. So now we'll go back and make sure we're looking at all of our issues except for those issues that are done because we want to see things that are open or in progress or need to be done. The assignee, you can go with your current user. The current user function is great. Anyone who opens the filter, it will show them all of the issues assigned to them. So you don't have to build a custom filter for each JIRA user. Maybe you're completing a filter for developers. You can just say, whoever the current user is, is all I want to see. Or you can look for suggested users myself. I want to see all issues that I have assigned to me. Perhaps you want to look for more fields. Every field in JIRA can be filtered on. As you see, there are over 100 as I click through. And again, this depends on your project or your environment, your business environment. There's also a hidden criteria. And if you hover over, it'll tell you why you're not able to see them. In this case, it says these criteria are hidden because they are not applicable to the current project. And for these issue types, which we've already said, we're looking at all of them, but we're only looking at what's in progress to do or QA. Then you can also search by keyword. So perhaps you want to have anything with the word drive. You can click on search, we've got none. So if you just take that out, delete it and click on search again. Now you get all of your issues back. And I will search for a keyword like car search. Now any user story that has the word car in it and it also meets the criteria of in progress QA to do will show up for me. I'll go ahead and remove that and click on search to get my full list back. You can also add additional fields. One common field is reporter. I want to know who opened the ticket. So you can now search by reporter. Maybe it's whoever's opening it as a current user or your suggested users. Any additional criteria you would like to search on, simply find it in the drop down by checking it and you'll be able to get to it quickly. I also created a label. I like to use labels so that I can find tickets I created. So I would click on my name, Josephine, and any issues that I gave the label to of Josephine will show up. Labels are ways to customize your filters and your searches without having to have a field in JIRA dedicated to information you want to store. This is how you create a filter quickly and what a filter is. JQuil is the advanced search for JIRA. So we have SQL in some databases, JIRA uses its own custom JIRA query language. For more advanced users, you can switch over to JQuil and write advanced queries. This is for beginners, so we'll switch back to basic and keep it basic because all of the things that we need to search for can just come up within the normal basic filters. Stay tuned for the next lesson where I will show you the views and the columns. Thanks for watching!