For example let’s say you have a large project that exists as a ticket such as updating a hosted application. This would include several tasks such as updating the application on the server and then updating the client application at your business locations across the country.
Atera could have a ticket that will act as a parent (For this example it will generically be called Update Application)
Update Application could be assigned to a manager so they can monitor the ticket and create the child tickets update server, update computers at HQ, update computers at branch 1, update computers at branch 2, update computers at branch 3
The child tickets could all be assigned to techs independently of each other with different due dates, statuses, priorities, and comments/replies.

Additionally, the comments/replies posted to parent tickets could be pushed to the child tickets (though ideally this would be prompted) and technician replies in child tickets could also be pushed to the parent as well.