Using Jira Filters with qTest Manager
This topic covers the use case for customers that want to utilize Jira filters with the Jira Integration: qTest Enterprise, and provides understanding for the behavior of the Jira filters and how they impact the data synced to qTest.
How to add a Jira filter as a Favorite
A user can create Jira filters and those filters will automatically become that users Personal Favorite filters, however, it will not become everyone's Favorite. Even when those filters are shared for everyone, other users will not see the shared filters as a Favorite until they add those filters as a Favorite within their personal Jira user account.
With Jira's filter rules above, the qTest Admin that maintains the Jira Integration within qTest, needs to add the Jira filter as their Favorite. This enables the qTest Admin to populate the favorited Jira filter to the qTest Projects Integration Settings.
Understanding the Jira filter behavior
The Favorite Jira filter is a "one-time filter" that affects the first retrieval of Requirements. When the filter is changed in Jira, it only affects new issues that are not imported to qTest yet.
If you set the Jira filter in Requirement's retrieval, qTest will import only the objects that are configured in the Requirement Integration and exist in the Jira filter at the time of retrieval, regardless of auto-sync or manual import.
Once Jira artifacts are already imported to qTest, they will be updated (via auto-sync or manually) based on their mapping, integration configuration, and their Jira IDs stored in the database.
Also, read theWhy can't I see a Jira filter to import requirements? FAQ for additional information on using Jira filters in qTest.