...
This specific feature will be extended in future Syndeia releases with a setting to allow the user to either delete the requirement or not delete it. The latter use case is for scenarios where the given requirement may have relations from/to other elements and the user may decide to not delete it, or refactor the model and then delete. Currently, Syndeia moves the requirements to the parent package and does not delete it during sync when using custom mappings specifically to address this scenario. For any questions, please reach us on our helpdesk.
...