Context:

When a Jira Cloud project (CMP) has multiple boards, each filtered by Team via board-level JQL filters, the List and All Work views do not inherit those board filters. Instead, they display all work items in the entire project. This creates confusion for organizations that rely on board filters to segment work by team, as users expect the List/All Work views to reflect the same scoping as the board they navigate from.

Requested Enhancements:

1. List/All Work views should respect board-level JQL filters

• When navigating to the List or All Work view from a board context, the view should inherit and apply the board's configured JQL filter by default, rather than displaying all project work items. Users should still be able to clear or modify the inherited filter within the view.

2. Hierarchy (parent-child nesting) should be retained when filters are applied

• Currently, when applying filters in the List and All Work views, parent-child relationships can flatten into a flat list. The hierarchy should continue to display in its nested structure when filters are applied, preserving the parent-child context that is essential for understanding work item relationships.

3. Team field as a grouping option in the All Work view

• The ability to group work items by the Team field within the All Work/List view, similar to how items can currently be grouped by Assignee, Status, Priority, or Sprint. This would allow teams that use Jira's Team field to quickly organize and visualize their work within a project.

Use Case:

A company-managed project has several boards, each filtered by Team. When team members navigate to the List or All Work view, they expect to see only the work relevant to their team's board, not the entire project. The current behavior forces users to manually re-apply filters in the List view, which is error-prone and creates significant confusion, especially across organizations with multiple teams sharing a single project.

Customer Impact:

This affects all company-managed projects with multiple board filter configurations. Customers perceive this as a defect because the user experience creates a strong expectation of filter inheritance when navigating between views within a board context.