The ‘’Open issues filter of your project shows bugs, along with epics and stones. You then view the project's Scrum board where you only see epics and stories but not bugs. Which configuration is responsible for this behavior?

A Jira board's content is fundamentally determined by its saved JQL (Jira Query Language) filter. This filter's query dictates which issues are pulled from the project(s) to be displayed on the board. In this scenario, the "Open issues" filter shows all issue types, including bugs. However, the Scrum board does not. This discrepancy indicates that the board's specific filter query is written to explicitly include only epics and stories, while excluding bugs (e.g., project = "XYZ" AND issuetype in (Story, Epic)). The board filter is the primary configuration controlling the set of issues available for display.

B. issue type scheme: This defines which issue types are available in a project. Since bugs exist in the project (visible in the "Open issues" filter), the scheme is not the cause.
C. board filter shares: Sharing permissions control who can view the board, not which specific issues are displayed on it for a user who already has access.
D. swimlanes: Swimlanes are used to group and organize issues that are already present on the board based on criteria like assignee or epic; they do not filter issues out entirely.
E. board sub-filter: A sub-filter (or Quick Filter) can further refine the issues shown, but it cannot add issues that are already excluded by the main board filter query.

1. Atlassian Jira Software Cloud Documentation, "Configure a board": Under the "General configuration" section, it states, "Every board is based on a saved filter. This filter, also known as the board's query, determines which issues are displayed on your board." This directly confirms that the board filter query is the responsible configuration. (Accessed via Atlassian's official support and documentation site).

2. Atlassian Jira Software Cloud Documentation, "Configure filters": This documentation explains that the JQL query for a saved filter is what defines the search criteria. It notes, "Your board's filter must be a shared filter." The query itself, such as issuetype != Bug, is what would cause the described behavior. (Accessed via Atlassian's official support and documentation site).

3. Atlassian Jira Software Cloud Documentation, "Configure Quick Filters": This page clarifies the role of sub-filters: "Quick Filters refine the issues displayed on your board that the board's filter has already returned." This shows that the main board filter is the primary determinant, making the sub-filter a secondary refinement tool. (Accessed via Atlassian's official support and documentation site).