Filtering Work Items in Agile Hive Cloud

Filtering Work Items in Agile Hive Cloud

Most views in Agile Hive provide a variety of filtering options. All available filters can be combined, enabling highly customized board and planning views tailored to your team’s workflow.

JQL Filter

Bildschirmfoto 2025-11-28 um 11.25.30.png

To account for more complex filtering needs, most views in Agile Hive can be filtered using Jira Query Language (JQL).

On the left side of the view's toolbar, you can enter any JQL query and apply the filter by pressing ‘Enter.’ After submitting a filter query, Agile Hive will validate your input and indicate whether it is a valid JQL query.

Please note that due to technical restrictions, auto-completion and search suggestions are not currently available in the Agile Hive JQL input field. We recommend preparing your JQL filtering queries in the Jira Work Item Search, then copying and pasting them into Agile Hive’s Team Planning Board.

For more information on how to use JQL, please refer to the official Atlassian Jira Cloud knowledge base: https://support.atlassian.com/jira-software-cloud/docs/use-advanced-search-with-jira-query-language-jql/

Extended Filter options

Bildschirmfoto 2026-01-28 um 15.37.31.png

The More filters menu next to the JQL input field in the toolbar of all planning views provides an easy way to filter visible work items using specific custom fields. The same menu is also available in the Unplanned Issue sidebars across all views.

image-20260616-093112.png

Available filter options depend on the view and SAFe level. All selected filters are saved as URL parameters, allowing links to be shared that open with the same filters already applied.

image-20251128-102811.png

To begin filtering, open any filter dropdown and select one or multiple values. The view updates instantly. To clear all active filters, click Clear filters at the bottom of the menu.

Filter options

Most filter options are powered by JQL. The corresponding queries are listed below. Queries applied through individual filter dropdowns are combined using the JQL operator AND.

You can copy the full JQL expression for the current filter configuration by clicking Copy JQL.

Filter option

Description

JQL query

Sort

Defines the field and directions the work items get sorted by

ORDER BY "" [ASC | DESC]

Text search

Searches across all indexed text fields

textfields ~ “ “

Type

Filters by Jira work item type

issuetype IN ("")

Assignee

Filters work items by assigned user(s)

assignee IN ("")

Status

Filters by Jira workflow status

status IN ("")

Priority

Filters by issue priority

priority IN ("")

Component

Filters by associated Jira components

component IN ("")

Labels

Filters work items by Jira labels

label IN ("")

Sprint

Filters based on assigned Sprint(s)

sprint IN ("")

Assigned PIs

Filters work items by their assigned Planning Intervals (PIs).

"cf[xxxxx]" IN (““)

Assigned Units

Filters work items based on the multi-select field Assigned Units.

"cf[xxxxx]" IN (““)

PI Involvement

Filters work items by involved Planning Intervals (calculated field).

"cf[xxxxx]" IN (““)

Involved Units

Filters work items based on the calculated field Involved Units.

"cf[xxxxx]" IN (““)

Owning Unit

Filters work items based on the single-select field Owning Unit.

"cf[xxxxx]" IN (““)

For more information on Agile Hive custom fields: https://agilehive.atlassian.net/wiki/x/LYB6Zg

Additional filter options

Swimlanes

Swimlane filtering provides an additional way to narrow down the ART-level work item swimlanes in the Team Planning boards. It helps teams concentrate on specific focus areas during PI Planning. This filter option operates independently of JQL.

Quick Filter

The Quick Filters option is available across all views in Agile Hive. Filters are loaded from the corresponding Jira space. Therefore the correct Primary Board must be selected inside the Agile Hive project settings. You also get a short link to edit them.

All selected quick filters are combined using an AND condition in JQL. Any sorting syntax (for example, ORDER BY) is ignored and will be removed from the resulting query. In this case, a message is displayed.