Using complete work-package trees as templates (e.g. via a category) is a common work-around. Unfortunately, copying (i.e. instantiating) such a template does not retain all relational information (follows etc.) among the copies as they were in the template.
# Reproduction Steps
### **Steps Steps to reproduce** reproduce
1. Create create work-package A
2. Create create work-package B
3. Create create a relation relationship of type T between A and B (syntax: R(A,B,T) ) 4. Bulk-copy bulk copy A and B as A' and B'
### What is the buggy behavior?
* The relation there is no relationship of type T between A' and B' (copied versions) * R(A', B', T) is not preserved missing
### What is the expected behavior?
1. Relational relational information between A' and B' is retained (like when moving in bulk)
2. Should should work with all types of relationships (e.g. parent-child, follows-preceeds, etc.)
### # Details
* add behavior of copying relationships to https://github.com/opf/openproject/blob/dev/app/services/work\_packages/bulk/copy\_service.rb
* ~~add add a checkmark to disallow/allow the current behavior~~
### Context
Using complete work-package trees as templates (e.g. via a category) is a common work-around. Unfortunately, copying (i.e. instantiating) such a template does not retain all relational information (follows etc.) among the copies as they were in the template.
### Out of scope
This bugfix won't introduce any options to let users pick if relations between original and copied work packages should be preserved. This will be dealt in a separate feature: