Server-side filters per product

This topic describes how to define named filters in products in which Filter and query data is supported.

Define a Jira filter

This section describes how to define filters for a Jira data source.

For named filters, OpenText queries Jira's Favorites Filters to determine the issue type and project.

For example, if you select type Bug in OpenText for a Jira filter, only filters in which the Bug allowed type are shown.

Filter type Procedure Learn more
Named

To create a filter in Jira:

  1. In the project's Issue tab, click View all issues and filters in the top right.

  2. Click New search and add your JQL code to the input area.

  3. Click Save as and provide a filter name. The filter is displayed in the Favorite Filters area.

 See "Save your search as a filter" in the Jira documentation.
Free form

Write code that defines the filter and enter it into the Free from filter area. For details, see Filter and query data.

 See "Use advanced search with Jira Query Language (JQL)" in the Jira documentation.

Back to top

Create an OpenText Application Quality Management filter

This section provides links for information on defining filters for an OpenText Application Quality Management data source.

Filter type Learn more
Named Filter dialog box
Free form Query a collection of entities

Known issues

If you encounter issues when using an OpenText Application Quality Management filter with a date field, use the format YYYY-MM-DD in the filter. For example:

Back to top

Create an OpenText Software Delivery Management/OpenText Core SDP filter

This section describes how to define filters for an OpenText Software Delivery Management/OpenText Core SDP data source.

For information about creating Free Form filters, see Collections.

Named filters are views that you saved in OpenText Software Delivery Management as favorites. For details, see Favorites.

To use a OpenText Software Delivery Management favorite:

  1. In OpenText Software Delivery Management, save favorites for the items you want to use, for example Defects.

  2. In Connect, open a connection for editing and navigate to the Projects and Rules page.

  3. Click the Edit connection type rule button for your rule.
  4. Select the Use Named Filter button.
  5. Expand the Selected Filter dropdown and select or search for your named filter. Make sure that the filter's details are represented in the Filter Details section.
  6. Expand the Test Filter dropdown, and select a field to show in the test results.

  7. Click OK.

Known issues

OpenText Software Delivery Management favorites are displayed for all types, including types that you did not select or specify. This is due to OpenText Software Delivery Management's behavior of not explicitly assigning favorites to specific types. As a result, items that were not specific to your type, may also be displayed.

Back to top

Create an Azure DevOps filter

For information on defining filters for an Azure DevOps data source, see the following:

Filter type Learn more
Named In Azure documentation, search for "View and filter Azure resource information."
Free form In Azure documentation, search for "WIQL syntax reference."

Tip: Install the Work Item Query Language (WIQL) Editor Marketplace extension in order to allow you to create queries in the Query Editor. You can then copy and modify the WIQL query and run it using the Board > Wiql Playground node.

Back to top

Create a ServiceNow filter

Data queried from a ServiceNow data source can be filtered in one of three ways:

  • Per type: For each data source type, you can apply a unique server filter. This filter is applied to the ServiceNow server and only returns data that meets the filter criteria, for all connections associated with that data source. For an example, see Data source settings.
  • Per connection: For each ServiceNow connection, you can apply a server filter for each type (and associated project, if relevant) to limit the data returned from the server. For details, see Server-side filtering overview.
  • Client filters. A client filter can be applied for each type in the Sync Criteria area. For details, see Client-side filtering using sync criteria.

These methods allow you to apply different levels of filtering. You can first constrain the data by filtering at the data source level, further constrain it at the connection level, and then tighten the constraint even further at the synchronization criteria level.

In most cases, you do not need to use all three levels. A best practice is to use server-side filters per connection. For OpenText Application Quality Management and ServiceNow, server-side filters are very effective in fetching limited quantities of server data at optimal throughput rates.

We recommend applying connection-level filters for entities such as a ServiceNow Incident and an OpenText Application Quality Management Requirement, where projects may contain thousands of artifacts.

The table below describes how to create a named filter for server-side filtering. For details, see the ServiceNow documentation.

Filter type Procedure
Named

To create a filter in ServiceNow:

  1. In the ServiceNow dashboard, go to All > System Definition > Filters.

  2. Create a new filter in ServiceNow. For example, Product is MFConnect AND Short description is not empty.

  3. Add the filter to your connection. For details, see Named filters.
Free form

Write code that defines the filter and enter it into the Free form filter area. For details, see Free form filters.

Back to top

Next steps: