Issue Summary

There is a discrepancy in how Jira boards handle subtask visibility when switching between grouping modes while filters are active. Currently, the board's Quick Filters appear to be constrained by the primary workflow of the project. If subtasks are governed by a dedicated, separate workflow, they are often excluded from the view unless a specific "order of operations" is followed. While Custom JQL Filters can successfully retrieve these subtasks (as JQL is not limited by workflow state), the board UI fails to dynamically refresh and display these results when the "Group by" setting is changed after the filter is already active.Steps to Reproduce

Current Behavior:

1. A user applies a filter (Quick Filter or Custom JQL).

1. The user then changes the Group by setting to Subtask.

1. Result: Subtasks matching the filter criteria do not appear. This is because the board's initial state is tied to the primary workflow, and changing the grouping does not trigger a re-evaluation of the subtask-specific workflow.

1. Workaround: Users must select Group by: Subtask before applying the filter, or perform a full page refresh to force the UI to recognize the subtask hierarchy.

Technical Context:

• Workflow Isolation: In many complex project configurations, subtasks utilize a dedicated workflow. Standard board filtering logic often prioritizes the "main" workflow, leading to the omission of subtasks in the UI layer.

• JQL vs. Quick Filters: Custom JQL filters are the preferred method for surfacing these items as they bypass workflow-specific limitations. However, the UI requires a more robust refresh mechanism to ensure JQL results are correctly mapped to the board's "Subtask" grouping in real-time.

Expected Results

The board UI should dynamically re-evaluate the entire issue set—including all issue types and their respective workflows—whenever the "Group by" setting is modified. The visibility of subtasks should be consistent regardless of whether they share a workflow with their parent issues.

Actual Results

1. User applies a filter (Standard or Custom JQL).
2. User changes "Group by" to Subtask.
3. Subtasks matching the filter do not appear on the board.

Workaround

User must either refresh the page or remove the filter, select "Group by: Subtask" first, and then re-apply the custom filter.