Using system actions for the final status of an Enhancement, you can automatically change the status of the linked requirements, for example to "Implemented". This behavior lets you finalize the requirement lifecycle and build the corresponding charts and graphs of progress in implementing requirements.
The link between an Enhancement and a requirement lets the system automatically form links between the requirement and the test documentation, and between the requirement and the operational documentation. For example, while working on an Enhancement, a tester creates test documentation and a technical writer creates operational documentation. Links formed automatically in this way are later used by the "suspicions" mechanism, that is, to help locate the changes to test and operational documentation that must be made because the source requirements have changed.