Current behavior:

When sorting a List view by a Custom Field (e.g., a Dropdown field called "Phases"), the sort only applies to top-level/parent tasks. Subtasks remain grouped under their parent task and are not reordered based on the Custom Field value. This means a subtask with Phase "1 - Pre-Production" can appear visually between subtasks with Phase "2 - Production" or "3 - Post-Production" because the sort is ignored at the subtask level.

Expected behavior:

When a sort is applied to a Custom Field on a List view, subtasks nested under a parent task should also be sorted by that same field within their parent group. The nesting/hierarchy should be preserved (subtasks remain under their parent), but their order within the nest should respect the active sort.

Why this matters:

We manage development projects where each parent task is a project and each subtask is a module. Modules move through phases (Pre-Production → Production → Post-Production → Done). We need to see modules nested under their project for context, but sorted by phase so we can quickly identify what stage each module is in. Currently the only option is to display subtasks "as separate tasks", which breaks the project-module relationship and makes the view unusable for project tracking.

Workaround attempted:

Displaying subtasks as separate tasks does allow sorting, but removes the parent-child grouping which is essential for our workflow.