...
- There is no limit on how many filters can be added - but of course creating too many of them is not recommended as it can be hard to manage them.
- Some of the fields in Jira or TFS / Azure DevOps (formerly VSTS) are truly array of values - like Labels for example. Operator chosen in filter is checked against each of the value in this array separately, so for example if filter has 'contains' operator then it's checked if at least one label in given issue contains text specified in the filter.
- Filters are case insensitive.
- Filtered field doesn't have to be mapped in Field Mapping.
- When there are no filters specified for Jira and TFS / Azure DevOps (formerly VSTS) then all of the issues / work items are synchronized.
Jira filters
- there are changes in the work of Jira filters, starting with version 7.9.4
- Jira filters are transformed to JQL in order to improve performance
- operation "Equals" is not supported for Text fields any more, it is recommended to use "Contains" instead