Creating a parent/child hierarchy

One reason to link records is to establish a hierarchy between them. A parent/child hierarchy is a useful way to decompose a large task into multiple smaller tasks. For example, you might submit a change request to track the work needed to add a feature to your product. To build this feature, your team might need to perform these tasks:

• Modify the core code base
• Modify the GUI
• Add an API
• Write new documentation

To track the progress of these tasks, you can submit change requests for them and link them to the parent change request, which represents the feature.

The process for linking records in this way is the same as for Sharing common data.