A saved filter remembers four things: the conditions that choose the work, the columns shown, the order they are sorted in, and whether it opens as a board or a list.
Save a filter#
- On Work items, set the filters, columns and sort you want.
- Save it as a filter and give it a name.
- Choose who can see it.
All the saved filters you can see are on the Filters page. Star one to keep it in the sidebar.
Conditions#
A condition is a field, an operator and a value, for example Priority is Urgent or Customer is one of Contoso, Northwind.
- Conditions are matched all or any.
- A group nests conditions inside each other, for a filter like (type is Bug or priority is Urgent) and release is the current release.
- Every field on a work item can be used, including your organisation’s custom fields.
Values that move#
Some values are worked out each time the filter runs:
| Value | Means |
|---|---|
| Me | Whoever is looking at the filter. |
| The current release | The release being built at that moment. |
That is what makes a shared filter useful. “Assigned to me in the current release” means the right thing to everybody who opens it, this month and next.
Who can see a filter#
| Shared with | Who can do that | Who looks after it |
|---|---|---|
| Only you | Anybody | You |
| A project | That project’s admins | That project’s admins |
| Everybody | Admins | Admins |
Changing a filter#
Open the filter, change what you want, and save it again. If you change a shared filter’s conditions without saving, only your view changes.