Maintain record relationship links between copied requirements

If you are using a feature as a template for repeatable work and it includes a series of child requirements, copying the feature does copy the child requirements but any record relationship links between the copied requirements are lost.

When you copy a feature, it copies the requirements but all the record links (dependencies etc) between the requirements are lost. As a result, the team must manually re-add all of these. This can be very time consuming

Maintain the record relationship links between copied requirements

or

Add Ability to choose how a copy functions - So you could decide what should be copied over and what should not.