There is an approval process before a feature/release is record linked (set as a dependency) to another feature/release

This is useful for us since on how we use AHA, its our technical guys who does the linking of dependencies in terms of other features/releases to another. There are internal processes in terms of approval before a certain dependency (record link) is final already to be defined on a certain feature/release. If this is done, the tool can actually catch the manual process we will be doing before placing/defining the dependency (record link) per feature/release.