A work type describes what a record represents. Stories describe a user outcome, tasks describe work to perform, bugs describe a defect, and an epic groups a larger body of work. A subtask divides one parent item into smaller work. These are process choices, not a ranking of importance.
Use the parent identifier when a relationship matters. Two records can share a summary and still represent different work. Changing the work type doesn't automatically add acceptance criteria or fix a weak description. In service work, a customer request type is also different from the internal work type. The local model checks the selected type and parent relationship. Hosted hierarchy customization and cross-project moves remain scenario decisions rather than simulated administrative actions.
Match work types and parent relationships to the request.