Content
View differences
Updated by Cécile Guiot over 1 year ago
### Steps to reproduce
I have two separate projects (X, Y). For project X, I have the work packages a and b, and for project Y, I have the work packages b and c. I allow relationships between work packages across projects.
<figure class="table op-uc-figure_align-center op-uc-figure"><table class="op-uc-table"><thead class="op-uc-table--head"><tr class="op-uc-table--row"><th class="op-uc-table--cell op-uc-table--cell_head"><p class="op-uc-p">X Project</p></th><th class="op-uc-table--cell op-uc-table--cell_head"><p class="op-uc-p">Y Project</p></th></tr><tr Project</p></th></tr></thead><tbody><tr class="op-uc-table--row"><th class="op-uc-table--cell op-uc-table--cell_head"><p class="op-uc-p"><strong>a Work package</strong></p></th><th class="op-uc-table--cell op-uc-table--cell_head"><p class="op-uc-p"><i>b Work package</i></p></th></tr><tr class="op-uc-table--row"><th class="op-uc-table--cell op-uc-table--cell_head"><p class="op-uc-p"><i>b Work package</i></p></th><th class="op-uc-table--cell op-uc-table--cell_head"><p class="op-uc-p"><strong>c Work package</strong></p></th></tr></thead></table></figure> package</strong></p></th></tr></tbody></table></figure>
1. In project X, the b work package is created.
2. In project X, the a work package is created.
3. The parent of the a work package is set to the b work package.
4. The b work package in project X is moved to project Y.
### What is the buggy behavior?
At this point, the system behaves differently depending on the version:
* **For version 14.1.1**: When the b work package is moved from project X to project Y, its child work packages (a) are being converted to c work packages (because c is the first one listed in project Y, even though it doesn't exist in project Y). As a result, I lose all the data in the custom fields of the child work packages.
* **For version 14.5.0**: When the b work package is moved, its child a work packages remain as a, but the project information for these a work packages changes to Y. However, the a work package actually belongs to project X, while the b work package is a shared task between project X and Y.
### What is the expected behavior?
* If user changes _Therefore, even when the b work package is moved between projects, the project or type of the a parent ticket, the project of child ticket or c work packages should not be changed
change._
### Important note
Due to this issue, I lost a significant amount of data in version 14.1.1. As a temporary solution, I had to create an **a** work package within project Y. However, project Y should not have the permission to create an **a** work package. This solution only prevented the loss of custom field data and kept the work package type from changing. However, the **a** work packages created by project X continued to behave as if they were created by project Y. As a result, the members of project Y appeared to own tasks they had never worked on. Overall, this did not resolve my issue.
### Environment information
_Please check and fill out the following details to help us identify in what versions and distributions of OpenProject the error occurs_
**OpenProject installation type**
* [ ] Hosted cloud edition
* [x] Packaged installation
* installed with DEB/RPM packages
* [ ] Docker All-in-one container
* [ ] Docker-compose installation
* [ ] Other (please specify)
**OpenProject version**
* 14.1.1
* 14.5.0
**Browser**
* [x] Chrome
* [x] [ ] Firefox
* [ ] Safari
* [ ] Mobile Safari
* [ ] Other (please specify)
**Operating System**
* [x] [ ] Windows
* [ ] Mac OS X
* [ ] Mobile iOS
* [ ] Mobile Android
* [x] Linux (Ubuntu 22.04)
* [ ] Chrome OS
* [ ] Other (please specify)
**Language**
_Turkish and English language_
I have two separate projects (X, Y). For project X, I have the work packages a and b, and for project Y, I have the work packages b and c. I allow relationships between work packages across projects.
<figure class="table op-uc-figure_align-center op-uc-figure"><table class="op-uc-table"><thead class="op-uc-table--head"><tr class="op-uc-table--row"><th class="op-uc-table--cell op-uc-table--cell_head"><p class="op-uc-p">X Project</p></th><th class="op-uc-table--cell op-uc-table--cell_head"><p class="op-uc-p">Y Project</p></th></tr><tr
1. In project X, the b work package is created.
2. In project X, the a work package is created.
3. The parent of the a work package is set to the b work package.
4. The b work package in project X is moved to project Y.
### What is the buggy behavior?
At this point, the system behaves differently depending on the version:
* **For version
* **For version
### What is the expected behavior?
* If user changes
Due to this issue, I lost a significant amount of data in version 14.1.1. As a temporary solution, I had to create an **a** work package within project Y. However, project Y should not have the permission to create an **a** work package. This solution only prevented the loss of custom field data and kept the work package type from changing. However, the **a** work packages created by project X continued to behave as if they were created by project Y. As a result, the members of project Y appeared to own tasks they had never worked on. Overall, this did not resolve my issue.
### Environment information
_Please check and fill out the following details to help us identify in what versions and distributions of OpenProject the error occurs_
**OpenProject installation type**
* [ ] Hosted cloud edition
* [x] Packaged installation
* installed with DEB/RPM packages
* [ ] Docker All-in-one container
* [ ] Docker-compose installation
* [ ] Other (please specify)
**OpenProject version**
* 14.1.1
* 14.5.0
**Browser**
* [x] Chrome
* [x]
* [ ] Safari
* [ ] Mobile Safari
* [ ] Other (please specify)
**Operating System**
* [x]
* [ ] Mac OS X
* [ ] Mobile iOS
* [ ] Mobile Android
* [x] Linux (Ubuntu 22.04)
* [ ] Chrome OS
* [ ] Other (please specify)
**Language**
_Turkish and English language_