If you’ve never worked with PractiTest filters in the past, we recommend that you also take 5 minutes to read the page on how to work with Custom Filters.
Viewing your information using hierarchical filters can be very useful. With filters you can view your entities (requirements, tests, test sets, issues) based on fields criteria. It can be used, for example, to represent complex products with features and sub features (sub components), or for representing releases with sub versions/builds/sprints, etc.
Table of Contents
- Hierarchical filters' tree overview
- Creating Filters with multiple criteria
- Auto Filters
- Cross Filters
Hierarchical filters’ tree overview
This article is a step-by-step guide for creating a hierarchical tree of filters to show tests by features and sub-features. This example is relevant to the Test Library module, but you can create hierarchical filter trees for each one of the modules: Issues, Requirements, Test Library, and Test-Sets & Runs.
Step 1
First, we will need two kinds of fields: a List field and a linked-list field. In this example, the parent list field is called “features” and the child linked list field is called “sub-features” (the fields are created under Settings –> Fields).
If you do not know how to create a linked-list field, click here to read more.
Start by creating a filter, you can add it under the top level or within an existing filter tree.
Create a Filter for each main feature and for each sub feature.
Step 3
When creating a new test, fill in the values for the “Feature” and “Sub Feature” fields.
Creating Filters with multiple criteria
Custom Filters help you organize your information and make it more easily accessible. You can use them any way you want, but you don’t have to organize your information using single criterion – adding a filter with multiple criteria is simple.
In the following example, we will show you how to create a view that will display all issues that are:
assigned to you (the current user), and are related to version 1.5 or 1.6,
OR
in highest priority and are related to version 1.5 or 1.6.
{assigned to me + (version 1.5 or version 1.6)}
OR
{Priority highest + (version 1.5 or version 1.6)}.
For this we will use the “OR” &
“AND” queries for filter criteria.
- Create a new filter and name it.
-
Then, in the Filter criteria section, click the “+ AND criteria” button
-
Choose the first criterion you would like to filter by. In this example, we’ve chosen to filter by the 'assigned to' user field.
-
Now we can add another criterion. Click the “+ AND criteria” again, and add more criteria to your filter. In this example, we have based the second criteria on the version field.
-
If more than one version is relevant to this criteria, you can press the “+OR” button to add more versions.
-
For this example we want to show issues from version 1.5 or 1.6 that are either assigned to current user OR are in high priority. Press the "+OR criteria".
-
This time, our first criteria is based on the Priority field.
-
After choosing the relevant filters, click the “Create filter” button. This will take you back to the issues page to the filter view you just created.
You can see that just as we defined, the issues shown in this view are only the ones related to the versions we chose (1.5 or 1.6) and are either assigned to a specific user (the current one) OR are in high priority.
Auto filters
To learn about Auto filters, please visit this page
Cross filters
To learn about Cross-filters, please visit this page