Content
View differences
Updated by Jens Ulferts over 2 years ago
**As a** person moving/copying work packages ### **Environment**:
**I want** a warning/confirmation message upon copying/moving work packages in case the copied to project does not support the work package type
**so that** I don't loose data.
This feature was created out of a bug: Your OpenProject Version: Cloud Edition 11
### **Steps to reproduce:**
1. set up a main project with an sub project
2. define for the main project, that all work packages are allowed (task, bug, ...)
1. define a user defined property and assign it to e.g. task only for this main project
3. define for the sub project, that only "bug" is allowed
1. the user defined property is not selectet for the sub project
4. move/copy the work package "task" to the sub project
### **Actual Behavior**
the work package is moved/copied to the sub project
If a (new) work-package is moved into a project in which this task type is not available (allowed), the type is automatically assigned to an available work-package type. In the same way, the user-defined properties that do not exist in the project are removed from the work package and thus also the information contained there.
### **Expected Behavior**
Moving/copying should be prevented, if the target project is setup differently than the the source project.
Non-admin users should then be able to inform admin users about the project configuration mismatch.
No inadvertent data loss can occur.
**I want** a warning/confirmation message upon copying/moving work packages in case the copied to project does not support the work package type
**so that** I don't loose data.
This feature was created out of a bug:
### **Steps to reproduce:**
1. set up a main project with an sub project
2. define for the main project, that all work packages are allowed (task, bug, ...)
1. define a user defined property and assign it to e.g. task only for this main project
3. define for the sub project, that only "bug" is allowed
1. the user defined property is not selectet for the sub project
4. move/copy the work package "task" to the sub project
### **Actual Behavior**
the work package is moved/copied to the sub project
If a (new) work-package is moved into a project in which this task type is not available (allowed), the type is automatically assigned to an available work-package type. In the same way, the user-defined properties that do not exist in the project are removed from the work package and thus also the information contained there.
### **Expected Behavior**
Moving/copying should be prevented, if the target project is setup differently than the the source project.
Non-admin users should then be able to inform admin users about the project configuration mismatch.
No inadvertent data loss can occur.