A optional type of subtask, like "simple subtask" where only uses to appoint basic informations, as in a production process steps: without Activity, Attachments, Relationships - they will come these informations from your respective parent task.

It will work where these "simple subtasks" are used solely to record those responsible, dates, status and time, but the information fed to instruct the work to be performed is common to all subtasks (so it would carry activity information, attachments and relationships fed into the parent task). This way, for the employee to consult attached information, they do not need to go to the parent task to consult, or have to enter the same information repeated in each subtask. (Also, additional information generated in the "simple subtask" activity will feed the respective field of the parent task.)

For the employee who will execute the subtask, whether on mobile or desktop, the assigned "simple subtask" will appear, but with attachments and activity from the parent task, where they will have all the information they need to consult.

Or, another option, perhaps even more suitable, would be to create a "Complete Check-list" that has all properties like a task: Status, Dates, Estimated time and time to track, tags and also some custom fields different from the task fields. So when you have a "complete checklist" assigned to someone responsible, they will view the Parent Task whether on mobile or desktop, but will make their records (time, status...) in this "complete checklist". The same should be used to display work views such as workload, timeline, etc., as when we set subtasks to appear in these views as well (it should allow the task to appear when it has a "complete checklist" also assigned). Evaluate how this would work when there will be several different "complete checklists" of the same task to appear in these views.

We'll can configure where this "simple subtask"/"complete check-list" is standard, as in Space, Folder or List, or Task Types.