This documentation relates to version 1.15 of Rich Filters for Jira Dashboards. Documentation for previous versions is available via the documentation index.
In this section:
- About Dynamic Filters
- Dynamic Filter Types
- Adding & Editing Dynamic Filters
- Supported Fields & Compatibility With 3rd Party Apps
1. About Dynamic Filters
Dynamic Filters allow the users to further filter the collection of issues displayed by gadgets based on the current rich filter. Dynamic filters are based on Jira fields (built-in or custom) and allow filtering issues by field values. Once configured, the dynamic filters are displayed in Rich Filter Controller gadgets as buttons with drop-down menus (for option/user/label/etc fields), text search boxes (for text-based and number fields), or date search boxes with calendar drop-downs (for date fields). When a dynamic filter is activated in a Rich Filter Controller gadget, all the other gadgets in the same dashboard and which are based on the same rich filter apply the selected criteria (the required JQL is automatically generated).
2. Dynamic Filter Types
There are four types of dynamic filters, depending on the type of field they are based on:
Option dynamic filters are used for fields that can take predefined values, such as check-boxes, select lists (single or multi select), status, priority, labels, user pickers, etc. Controller gadgets display these as buttons with drop-down menus, which allow selecting among the options available for each field.
When activated, dynamic filters limit the results to only those issues that match the selected options. If more than one option is selected, the filters will pass issues that have any of the selected values. (In JQL syntax, the selected options are
ORed together, then the result is
ANDed with the other JQL parts)
The options available are chosen only based on issues returned by the base Jira filter – it doesn’t show options that are defined by the field configurations but do not occur among your issues, increasing the relevance of the filter. For example, this is very useful if you add a dynamic filter for the Assignee field. The drop-down menu displays only users who have at least one issue assigned.
Also, for each option dynamic filter, the controller displays a search-box so that the user can easily find the options he is looking for. The user can easily select/deselect the options one by one or a range of options using SHIFT + click. These mechanisms combined are particularly useful for fields with a large number of options.
Text dynamic filters are used for string and text fields, such as the issue summary and description. Text filters don’t use a menu: instead, they just display a text box. The required JQL is automatically generated to filter only issues that contain the entered text.
Jira has two different text searchers, one for exact string search and one for full-text search. Dynamic filters will use one or the other, depending on how your field is configured. Advanced search features such as prefix and wildcard queries are supported. See Jira’s documentation for the syntax.
Besides issue fields, there are two extra text dynamic filters that you can add in your rich filters: one is labeled Contains Text, and allows searching at the same time the summary, environment, description, the comments of an issue, as well as all custom text fields; the other is labeled Comments, and searches exactly what the name suggests.
Number dynamic filters are used for number fields, such as Story Points or Business Value fields but also for searches based on the number of votes or watchers. These filters too display a text box where the user can type multiple values or ranges to use for the search. Several searching options are supported:
Search by value: the user can insert one or several space-separated values to search for – e.g. “
1 2 3” for issues having the values 1, 2, and 3;
- Search values greater or lower than a given value: the operators '
<=', and '
>=' are accepted – e.g. “
>=1” for issues having the values greater or equal to 1;
- Search for intervals: the form “
a:b” can be used to search values between a and b included – e.g. “
1:10” for values between 1 and 10;
- Search for issues with the value empty or not empty: the user can type '
empty' to see the issues having the field empty or '
!empty' for the issues with the field not empty.
1 2 <0 4:8” returns the values 1 or 2 or the values inferior to 0 or in the range 4–8.
Date dynamic filters are used for date/time fields, such as created, updated, resolution date and custom date fields. Date filters allow the user to filter only issues with date field values on, before, after or between two dates.
Each dynamic filter has two date inputs – Since and Until:
- If Since is filled, then only issues having values on or after the inserted value are displayed;
- If Until is filled, then only issues having values on or before the inserted value are displayed;
- If both Since and Until are filled, then only issues having values between Since and Until (inclusive) are displayed.
The inputs Since/Until can be picked from a calendar or entered manually as an absolute date (
“yyyy/MM/dd” or “
yyyy-MM-dd”) or time relative to the present (e.g. “
If you need to search for issues on a single date, enter that date in both Since and Until at the same time. In order to insert 'now' in Since/Until, one option is to use the value '
Rich Filter Extensions
Rich filter extensions are separate Jira apps that can be installed on top of the Rich Filters for Jira Dashboards app to extend the rich filters and rich filter gadgets with new specific functionality.
New dynamic filter options are available if you add any of the these extensions:
Rich Filters::Service Desk Dashboards allows you to add dynamic filters based on Service Desk specific fields – Customer Request Types and Organizations
3. Adding & Editing Dynamic Filters
You can add new and see existing dynamic filters and their configuration in the Dynamic Filters section of your rich filter.
The Dynamic Filters section of your rich filter allows you do to the following operations:
|To do the following:||Do this:|
|Add a Dynamic Filter|
Click on the Pick a field... button at the bottom of the page. A drop-down menu is displayed, showing all supported fields. Either scroll down or use the search to find the field you want, then click on the “plus” icon on the right, or press
|Delete a Dynamic Filter|
Click the delete icon at the right of the dynamic filter.
|Reorder the Dynamic Filters|
Hover over the vertical “grid” icon, then drag-and-drop the dynamic filter up or down to its new position.
When the dynamic filters of this rich filter are displayed by Controller gadgets, by default the dynamic filters are shown in the order configured in this section.
|Change the options order of a Dynamic Filter|
This applies only to option dynamic filters (check-boxes, select lists (single or multi select fields), status, priority, labels, user pickers, etc).
Hover over the dynamic filter and click on the Edit icon.
For single-select or multiple-select custom fields, you can chose between Alphabetical and Natural (the order of the options as defined by Jira administrators).
This can be very useful. For example, if you have a single-select field called Size with options S, M, L, XL, then the alphabetical order is not very intuitive. It makes more sense to use the natural order in this case.
The same menu allows you to invert the order of the options.
For all the other option fields, the system default order is used but you can chose to invert the order of the options.
4. Supported Fields & Compatibility With 3rd Party Apps
We support dynamic filters for most of the built-in Jira issue fields and custom fields: Key, Project, Project Category, Summary, Issue Type, Status, Priority, Resolution, Affects and Fix Version(s), Component(s), Labels, Environment, Description, Assignee, Reporter, Due Date, Created, Updated, Resolved, Sprint and Epic Link (for Jira Software), Select List (single/multiple choices and cascading), Checkboxes, Radio Buttons, Labels Custom Field, User Picker (single/multiple users), Group Picker (single/multiple groups), Project Picker, Text Field (single/multi line), URL Field, Date Picker and Date Time Picker.
We also support dynamic filters for all custom fields added by 3rd party apps that use one of Jira's built-in custom field searchers: Single/Multi/Cascading Select Searcher, Labels Searcher, Group Picker Searcher, Project Dropdown Searcher, Exact Text Searcher, Free Text Searcher, Date Range Picker, Date Time Range Picker.
Moreover, we do our best effort to support dynamic filters for some of the custom field searchers added by popular 3rd party apps. Click here to see the list of 3rd party apps we provide support for.
Troubleshooting dynamic filters based on 3rd party searchers
In order for the dynamic filters to work for custom fields based on searchers added by 3rd party apps, the minimum requirement is that the searcher needs to have implemented a Statistics Mapper. A quick test would be to see if the field can be used as a statistic criteria in a 'Issue Statistics' built-in Jira gadget. Also, it is important to make sure the field and searcher are correctly configured. Make sure the options are displayed correctly in the 'Issue Statistics' Jira gadget.
The performance of the dynamic filter (display/search speed) depends entirely on the configuration and implementation of the 3rd party custom field. When used as a dynamic filter, the field will have exactly the same performance as when used in Jira's built-in Issue Navigator and 'Issue Statistics' gadget.