Content
View differences
Updated by Ivana Šugić 5 days ago
###
Before filing a report
_Before you file a report, please ensure you are running the latest version of OpenProject and_
_have searched for similar bug reports._
### Steps to reproduce
1. Select a work package/task which is allocated to a version (open or locked)
2. Duplicate the work package/task
3. The "version" dropdown of the newly created (duplicate) work package/task seems empty. Try to allocate a new version.
4. Save the duplicated work package
### What is the buggy behavior?
* The duplicate work package is not saved
* There was an error notification shown with the message "version and target versions cannot both be changed at the same time"
### What is the expected behavior?
1. The application should save the duplicate work package, with the newly assigned version.
### Workaround
* Save the duplicate work package / task, with the seemingly empty version field.
* After saving, the version field is not empty, but the version of the original work package which was duplicated is retained.
* The version can be changed now.
###
###
### Screenshots and other files
_Screencapture of the workflow with error message is attached, including the workaround which is executed afterwards._
_<img class="image_resized op-uc-image op-uc-image_inline" style="width:1179px;" src="/api/v3/attachments/923864/content">_
<br>
### Environment information
**OpenProject installation type**
* Packaged installation
* Ubuntu
<br>
**OpenProject version**
OpenProject 17.7.2 - The bug appeared after upgrade from 17.6
**Browser**
* [ ] Chrome
* [x] Firefox
* [ ] Safari
* [ ] Mobile Safari
* [ ] Other (please specify)
**Operating System**
* [x] Windows
* [ ] Mac OS X
* [ ] Mobile iOS
* [ ] Mobile Android
* [x] Linux (please specify distro)
* [ ] Chrome OS
* [ ] Other (please specify)
**Language**
_Please specify the browser language and the language of the OpenProject user for which the bug occurred._
_Before you file a report, please ensure you are running the latest version of OpenProject and_
_have searched for similar bug reports._
1. Select a work package/task which is allocated to a version (open or locked)
2. Duplicate the work package/task
3. The "version" dropdown of the newly created (duplicate) work package/task seems empty. Try to allocate a new version.
4. Save the duplicated work package
### What is the buggy behavior?
* The duplicate work package is not saved
* There was an error notification shown with the message "version and target versions cannot both be changed at the same time"
### What is the expected behavior?
1. The application should save the duplicate work package, with the newly assigned version.
### Workaround
* Save the duplicate work package / task, with the seemingly empty version field.
* After saving, the version field is not empty, but the version of the original work package which was duplicated is retained.
* The version can be changed now.
###
###
### Screenshots and other files
_Screencapture of the workflow with error message is attached, including the workaround which is executed afterwards._
_<img class="image_resized op-uc-image op-uc-image_inline" style="width:1179px;" src="/api/v3/attachments/923864/content">_
<br>
### Environment information
**OpenProject installation type**
* Packaged installation
* Ubuntu
<br>
**OpenProject version**
OpenProject 17.7.2 - The bug appeared after upgrade from 17.6
**Browser**
* [ ] Chrome
* [x] Firefox
* [ ] Safari
* [ ] Mobile Safari
* [ ] Other (please specify)
**Operating System**
* [x] Windows
* [ ] Mac OS X
* [ ] Mobile iOS
* [ ] Mobile Android
* [x] Linux (please specify distro)
* [ ] Chrome OS
* [ ] Other (please specify)
**Language**
_Please specify the browser language and the language of the OpenProject user for which the bug occurred._