This video discusses Quick Search and Basic Search. We will start with a searching overview. There are several topics related to searching in Jira. We will discuss them quickly now and then discuss them in more detail in this and the next video. The first is called quick search. This is accessed by clicking the search icon in the global sidebar. This allows you to quickly search for text in issues, board names, project names and filter names using a text-based search. You can also quickly access recently used items as shown here. The star is another way to access recently used and favorite items. Another type of search is called basic search. This is accessed on the application level contextual sidebar in the issues and filters tab. This is called the issue navigator. In a basic search, issues are searched for using a row of user-friendly interface elements as shown here. Changes to these elements will change the resulting list of issues. Advanced search is an alternative to basic search where you can specify your search using Jira query language or JQL. This is a way to execute more complicated searches than with basic search. Filters are used to limit the issues that are displayed in search results. You can see filters in the application level contextual sidebar as shown here. These are the default filters provided by Jira. For example, if you click on the "Open issues" filter, the results will show all issues in all projects that have not been closed. You can also add custom filters such as the filter called my custom filter here. Even though filters are usually presented as user interface elements, they have an underlying JQL statement associated with them. That JQL statement defines which issues to show. In addition to the application level issue navigator, there are project level filters shown in the projects contextual sidebar as shown here. These are used to limit which issues from that project to show. The final search topic that we will discuss is quick filters. Quick filters are used to limit which issues are shown on a board. Here are two out of the box quick filters used to show only your issues or recently updated issues. You can also add custom quick filters to the board. Like standard filters, quick filters have an underlying JQL statement associated with them. We are discussing searching JQL and filters because they are used to help adapt to your Jira experience to your team's processes. We have seen that each Agile team is unique and constantly improving. So, the tools that are used need to be flexible enough to adapt to changing circumstances. Next, we will discuss quick search. Quick search is accessible using the icon in the global sidebar. When you initially open the quick search, the results show recent items. You can click on an item to display it. Typing into the quick search box changes the results from recent items to items that match the text that you are searching for. As you type in the search box, the results are updated. Here you can see that there are two issues with the field value of feature two. Searches in Jira are generally not case sensitive. The quick search does not return just issues. When you open quick search, you can also access recent boards, projects, and filters. When you perform a search, all of these items that match will be displayed. Usually, you will just be entering simple text when searching with quick search. You also have the option of adding slightly more sophisticated syntax. As an example, on the left we are searching for the text feature. You can see that this text is in the summary for six issues in our Jira account. We can exclude feature one by adding a capitalized not followed by the number one. You can see that the two issues containing feature one are excluded from the results. In the search, not must be in all caps. The search terms are not case sensitive but text field search keywords such as; not, or and and must be capitalized. In this example, we use the OR keyword to search for a feature or a sample. For more information on this type of searching, see the link shown here on search syntax for text fields. If you include multiple terms in the search, the default is to combine them with "and". You can see that if we search for feature one, we receive the same results as if we search for feature, AND 1. You can use the wildcard character which is an asterisk in text field searches to match parts of words. Next, we will discuss basic search. Basic search uses user-friendly interface elements in the "Issue" navigator to search for issues. This row of elements shows that we are in the basic search. We can click on the "Advanced" link to switch to the advanced search. Likewise, if we are in the advanced search, we can click on the basic link to switch to basic search. You can see that this search searches all projects for issues of any type, in any status and with any assignee. This is searching for all issues in the Jira account. You can see that there are currently 29 issues in this account, assuming that we have permission to see all issues. If we click on the "Project" drop-down and choose "projectA" you can see that three issues are returned. Notice that basic search includes a text box with the words "Contains text". This behaves much like the quick search but is limited to searching issues. If you enter text in this text box, Jira will search in fields that typically hold texts such as summary or description. In this example, we have changed the project drop-down to projectA and added "feature NOT 1" to the contains text box. This will filter the "Add feature 1" issue from the project and you can see that we are left with two issues. You can see that the capital "NOT" in the quick search can also be used here. If you type text into the quick search box, the search results are immediately updated as shown. Here we have typed "feature NOT 1" into the quick search box. If you press the "Enter" key after typing in the search text, you will be brought to the issue navigator with your text already entered in the search. The resulting issues match the issues from the quick search. As a simpler way to enter the issue navigator, you can open the "Quick Search" and simply press "Enter". If you want to search for values and fields that are not listed in basic search, you can click on the "More" drop-down to add searches for other fields. We will click on the updated date checkbox to add a search related to the day that an issue was modified. Here we have clicked on "Updated date" and you can see that Jira adds a dialog allowing you to specify the date values to search for. We have chosen to search for any issues that have been updated within the last three days. Adding the search for the updated date, reduced the results to the three issues shown here. We can click on the "More" drop-down to add additional search criteria if we would like. Here, we have selected "Priority" from the "More" drop-down menu. Notice that Jira will automatically provide the appropriate interface depending on the type of field chosen. We have just seen that when we selected the "Update date" field, we were provided an interface related to dates. In this case, we have selected the "Priority" field so Jira provides us a set of priorities to choose from. Next, we will discuss working with search results. The icon shown here is the "Change view" icon. There are two modes for the view of the search results. The first is "List view", which we see here. If we change the view to the "Detail view", we see a list of search results on the left, along with the details of the currently selected issue on the right. In list view, you can select the columns drop-down and pick and choose which columns that you want to display in your search results. To rearrange the columns in the search results of list view, you can click on the column heading and drag the heading to the new location. To sort the search results by column, click on the column that you'd like to sort by. In this example, we've clicked on the "Updated" column. The downward facing arrow means that the items will be displayed in descending order. In this case, it means that the issues in the search results are sorted with the most recently updated issues first. You can click on the "Updated" column header again to change the arrow to upward facing. Meaning that the most recently updated issues will be at the bottom of the list. If you have search results that you would like to share with another member of the team, you can click on the "Share this search" icon in the upper right and specify the user or users that you'd like to share the search with. This will email a link to the project that includes the underlying JQL for the search. When the user clicks on the link in their email, their browser will open with the search results. The query will be executed again, so the results might look different from when you originally performed the search. You can export the search results by clicking on the "Export" icon in the upper right. You have a variety of export options to choose from. We will export the search results as XML as an example. When you export the search results as XML, the XML opens in a browser window and maybe downloaded to your computer. This contains the field names and values for the issues of the search results. Besides a handy backup, this is a way to see what the actual field names and values are for an issue, providing you a better understanding of how Jira defines an issue. You can click on the "More Options" icon in the upper right. You can change all of the resulting issues at once by selecting the "Bulk change" option. For example, if someone has left the team, you could bulk assign all of that person's issues to another user. In more options, you also have the ability to import issues from a saved comma separated value document. Here is a review of what we've discussed in this video. Quick search is accessible from the global sidebar and searches the text of issues, board names, project names and filter names. Basic search is a user friendly way to search for issues and is accessible from the issue navigator. Search results can be reordered, exported and used to bulk change issues. Now, it's time for you to work on the things discussed in this video. Separate hands-on instructions are provided for you.
