Jira Epics - Prefilter Functionality

  • Updated

What does this functionality do?

The pre-filter feature is designed for clients managing substantial data in their Jira environment who seek to selectively migrate a limited amount of data to OnePlan. 

The functionality operates through Jira Query Language (JQL) and relies on user-created filters accessible in the Filters page. These pre-filters are applicable to both the Epics - Plans table and the Issues - Backlogs table. The pre-filter functionality only influences the transfer of data from Jira to OnePlan.

Enabling Pre-Filter 

To enable pre-filtering, two things need to occur:

  1. The Use Pre-Filter for filtering checkbox must be checked. 
  2. Filters must be applied to either the Epics - Plans table or the Issues - Backlogs table within the Mappings > Filters section.

Applying the Filters

Filters are broken down into four segments: Select Field, Select Operator, Value Field, and Logical Connector.

Select Fields are all fields mapped within the Mappings > Fields tables. Please note that the field mapping must match the table that the filter is being applied to (i.e., Epics - Plans table vs Issues - Backlogs).

Select Operators enable you to define the type of comparison (or operation) to be performed on the Select Field. The set operators allow you to precisely specify how the field value should relate to the condition you are establishing. This selection determines the criteria for including or excluding data based on the chosen field, enhancing the flexibility and precision of your filters. 

Value Fields are where you input a specific value against the chosen field and will be compared during the filter process. Depending on the operator selected in the Select Operator field, this value defines the condition that the data in the chosen field must meet to be included in the result set. 

Logical Connector serves as the bridge for constructing sophisticated queries or filters by connecting multiple conditions. When you have more than one query condition, the logical connector lets you specify how these conditions should interact. You can choose between 'AND' and 'OR' to dictate whether all conditions must be met, or if at least one of the conditions should be satisfied.  To extend the current filter to apply the Logical Connector, click Add Filter

Once a suitable filter has been created, click Save.  

Filtering and Comparing Date Fields

When directly comparing with a date field (e.g., Due Date = 12-31-2000), setting up the filter remains straightforward. However, when dealing with comparisons like Due Date >= 12-31-2000, the filter may not function as intended. This is because the dates are treated as string values in this scenario. For proper date field comparisons, please ensure the date value is enclosed within number signs (e.g., Due Date >= #12-31-2000#).

Filtering and Comparing Label Fields

When opting to filter based on a label, make sure to set the Select Operator to the value β€˜IN’ (e.g., Labels IN BringIntoOnePlan). Please note that label values should not include an apostrophe (β€˜) or a comma (,) in their names.

Pre-Filter Best Practices

Test Filters one at a Time

It is recommended to apply filters based on a single value at a time. Utilizing multiple filters might introduce unintended complexities, potentially resulting in the inclusion or exclusion of unexpected data during the transfer process. Keeping the filtering focused on a single value enhances precision and reduces the risk of unintended data being brought into OnePlan. 

Ensure all Issue Types have the Pre-Filter Value

When applying filters to the backlog, it's important to note that most issue types in OnePlan appear in a hierarchy. If a task in Jira doesn't meet the pre-filtering criteria, but its sub-task does, neither item will be displayed in the OnePlan backlog. Both Jira issue types must meet the pre-filtering criteria to be included in OnePlan.

 

Was this article helpful?

0 out of 0 found this helpful

Have more questions? Submit a request