When working in the Service Manager console, you can use the different views to browse existing incidents. But if you're searching for very specific incidents and don't have a view with that given criteria, it can be very hard to locate those tickets. Besides, you're only looking for that right now and do not want to create a view to find them. This is when the search function in SCSM comes very handy.
The search bar is located in the top-right corner of the console and if you enter some text here and press Enter, the system will actually search the display name of all work items. As the display name is a combination of the ID and title of the work item, this means that if you're looking for something with a specific title or ID, it's very easy to find - just enter the information in the search bar and press Enter.
But let's say that you're looking for incidents where the affected user is working on a particular department and where the description field contains a certain keyword - that's when you have to use the advanced search function.
In this recipe, we will search for incidents where the affected user is working in the marketing department and where the Description field contains the word Intranet
.
intranet
as the search string.
Using the advanced search function you can do very advanced searches to locate any type of objects. The function is very useful to find those very specific work items or to do some quick analytics. One thing to keep in mind though, is that the search function does only search for active data in SCSM. Hence, objects that has been groomed and only exist in the SCSM Data Warehouse cannot be found using the search functions!
Using the different combination classes, you can basically search for anything. A common request is to be able to search the action log for certain keywords - this can be achieved using by using this function. If you would like to search for all incidents which have an action log comment from the analyst that contains the word test can be achieved, such as in the following screenshot: