Purpose of Custom quick filters for Reports
Custom quick filters are one of the three types of predefined filters for a report. They are set up by report creators in advance and can be applied by a report viewer later.
This capability allows report creators to define 'presets' of filters. It saves time of report viewers as later they just select and apply a proper preset instead of configuring individual filters over and over.
Custom quick filters affect all views in a report. They are shown in the report header area.
All the filters are configured in Set up Report mode.
Only report creators (Owners) and Administrators are allowed to change permanent settings of reports.
Report creators can customize behavior of default context selectors of Projects (Products/Portfolios) and Teams, and custom quick filters. These filters for reports are configured quite similar way as it is done for other Targetprocess views — lists, boards, roadmaps.
Customize default context selectors
Report creators can customize behavior of default context selectors of Projects (Products/Portfolios) and Teams.
It is possible to customize:
- What Projects (Products/Portfolios) and Teams are visible and available for selection by report viewers
- What Projects (Products/Portfolios) and Teams are pre-selected for all report viewers by default
- Whether Projects (Products/Portfolios) and Teams selectors themselves are visible or not in a report header
Customize quick filters
It is possible to filter report records by Targetprocess entities, by dropdown custom fields, by custom text and numeric values.
To configure a custom quick filter, add "target" field or formula to source data fields in advance.
Filters by Targetprocess entities
Filters by Targetprocess entities allow to filter records by related items. Say, you can filter Features by Epic, Agile Release Train, or Program Increment, filter User Stories and Bugs by Feature or Team Iteration, filter Requests by Product, filter Initiatives by Objectives and so on.
To filter report records by Targetprocess entities — for example, by Agile Release Train — add special field
Agile Release Train ID to source data fields. Then configure your custom quick filter by selecting Agile Release Train in Type area and selecting corresponding data field
Agile Release Train ID in Apply to field area.
Filters by custom fields
Filters by custom fields allow to show or hide record records based on values in DropDown custom fields. For example, it is possible to create a report by Features with quick filter by Value Type.
To filter report records by custom fields — for example, by Value Type — make sure that custom field
Value Type is already added to source data fields. Then configure your custom quick filter by selecting Custom field in Type area, choosing custom field, and selecting of corresponding data field
Value Type in Apply to field area.
Filters by custom values
Filters by custom values allow to compose flexible filtering conditions: by entity type names, by workflow states, by people names, and anything else that can be searched in a text or numeric field of a report record. It is possible to build a single Cumulative Flow Diagram for User Stories, or Bugs, or both types together without creating a separate report for each of the type. It is also possible to build a portfolio management report, and quickly switch across deliverables and people groups of your portfolio.
To filter report records by custom text values — for example, by entity type — make sure that special field
Type is already added to source data fields. Then configure your custom quick filter by selecting Custom values in Type area, providing names of types one per line to Values area, and selecting of corresponding data field
Type in Apply to field area. Enter visual label of the filter to Name area to guide report viewers visually.