Thanks for the confirmation and the references.
Do you know the design thinking here? It seems that by adding the project to a subtask you are effectively promoting it to a task without actually promoting it. But there’s no real parent/child relationship anyway, so it seems pointless.
I know that by adding the project, this allows the subtask to show in calendars etc but why not use a task for that if there’s no parent/child relationship anyway?
I just tested creating 3 subtasks on a task and then added those to the project. I then completed the task to see if that would automatically complete the subtasks as well. It didn’t. So that’s another design decision I don’t get - no link between the status of subtasks and tasks. Why would you want to complete a task and orphan its subtasks as uncompleted?
Lastly, I can’t imagine a scenario where subtasks would be on any other project other than their parent’s project. This also appears to be a strange feature.
At some point, your developers have chosen to keep tasks and their subtasks very loosely related (hardly at all) but I don’t get it, sorry.