Some issues in your project have labels and others do not. Some tasks in your project are identified by a distinct label: daily_business. You need to prevent these issues from being displayed on the team's Scrum board Which solution meets this requirement?

The board's saved filter defines the fundamental set of issues that appear on it. To permanently prevent certain issues from being displayed, this filter must be modified. The JQL clause labels != "dailybusiness" would incorrectly exclude issues that have no labels at all. The correct JQL must explicitly include issues with no labels using OR labels IS EMPTY. Therefore, appending AND (labels != "dailybusiness" OR labels IS EMPTY) to the existing board filter correctly removes only the issues with the "dailybusiness" label while retaining all others, including those with no labels.

A: A quick filter only provides a temporary view for users on the board; it does not permanently prevent issues from being part of the board's scope. B: A board sub-filter is used to configure the Epics panel on a Kanban board, not to filter the primary issues displayed on a Scrum board. C: The JQL syntax labels NOT IN (..., EMPTY) is invalid. The EMPTY keyword must be used with the IS or IS NOT operators.

1. Atlassian Documentation, "Configure a board": This document explains that the "Filter" in the board's General configuration settings determines which issues are displayed on the board. Modifying this JQL query is the correct method to permanently add or remove issues. (Reference: Atlassian Cloud Documentation > Jira Software > Configure a board > General configuration).

2. Atlassian Documentation, "JQL fields reference": The documentation for the labels field explains the use of operators like != and IN. It also clarifies that a negative query (e.g., labels != "X") will not match issues where the field is empty. (Reference: Atlassian Cloud Documentation > Jira Software > Advanced searching - JQL fields reference > labels).

3. Atlassian Documentation, "JQL keywords reference": This reference confirms that the EMPTY keyword is used to find issues where a field has no value and must be used with the IS or IS NOT operators. This validates the syntax labels IS EMPTY and invalidates the syntax used in option C. (Reference: Atlassian Cloud Documentation > Jira Software > Advanced searching - JQL keywords reference > EMPTY).

4. Atlassian Documentation, "Configure quick filters": This page describes Quick Filters as "buttons at the top of a board that let you quickly see only the issues you're interested in." This confirms they are for user-driven, temporary filtering, not for defining the board's core issue set. (Reference: Atlassian Cloud Documentation > Jira Software > Configure quick filters).