I’m having an issue in ClickUp with task statuses. When I move a parent task from Backlog to Sprint Backlog — that is, the user story — the subtasks remain in Backlog, and this has a huge impact on the reports I use to track the team’s workload points. The sum of the points from these subtasks in Backlog isn’t counted; only the points entered directly in the parent task are considered, which isn’t how we assign points. How is this not solved yet?

Should inherit other things like priority too

How is this not already done? It should be optional, but it should 110% have been done by now when CLEARLY people want this. Come on, ClickUp!

Any updates on this?

It's nonsense that this option isn't the default. Moreover, it works in table mode... but not in list view... I will look to change the software. Really disappointing

No i do not think that subtasks should inherit the parent tasks status. If implemented then it should be an option not a default

Update on this please?

PLEASE CLICKUP TEAM make every subtask automatically inherit the parent status (color)!!!!! it's hard to recommend the system as intelligent when you have to manually change the status if each subtask

Or AT LEAST allow me to create an automation that says.. "When a new subtask is created THEN set status to "PARENT STATUS".

Today I stumbled on to a feature that I have not seen documented anywhere. The scenario is this: I am working on a project for a client. Let's call it "Matter 1." I created a Task called "Matter 1." I use Subtasks to track the specific deliverables, such as "Negotiate Purchase Agreement" or "Deliver Financial Schedule." I have lots of client projects, so I have lots of Tasks set up like this. When I want to focus on a specific project, I apply a filter on a custom field such as "Matter Name" or "Client" to hide other projects. I have found that when I apply a filter and then create a Subtask, the fields corresponding to the filtered values populate automatically in the Subtask. So, if I create a filter based on values in 5 different custom fields, when I create a Subtask, the custom fields in the Subtask are automatically populated with the values I specified in the filter. This somewhat replicates field inheritance from Task to Subtask. I'm wondering if anyone else has observed this behavior and if it is documented anywhere.

Please implement this - but as an OPTION!