In fu3e, tickets can be structured using parent, child and associate relationships to build workflows, related activities and shared information. 
Definitions:
Associate Ticket - These tickets are related but not directly part of a parent-child structure. Association is used for referencing or linking tickets that have a connection. Connect the tickets by linking exiting ones or creating from the linked tickets area.
For Example: Incident Record Form, Project Risks, Executive Risks, Business Impacts Form.
Parent Ticket - A primary or top-level ticket that may represent a broader task, objective, or process.
For Example: A parent 'New Supplier Request Form' which requires a child 'New Supplier Approval form'. The child is created directly under the specific Supplier and linked.
Child Ticket - A sub-ticket that is automatically linked from the creation via a parent ticket. They are usually specific tasks or activities required to complete the parent ticket. They can only be linked to their direct 'parent'. Your administrator can enable them to be created without a parent ticket.
For Example: The 'parent' Purchase Order serves as the main record, while various child tickets allow tracking and management of related actions and information tied to the specific PO to ensure that all relevant processes and documents are neatly organised.
The parent Purchase Order could have children or associate forms such as:
- Variation Order Form: Created for order changes or variations
- Goods Receipt Form: Confirms when the goods have been delivered
- Non-Conformance Report: Raised for delivery issues, such as faulty or incorrect items