Content
View differences
Updated by Alexander Stock over 2 years ago
Request by Alexander: I worked on a ticket today where a customer had issues to understand how duplicate/duplicate by relations work. He sent us the description from our documentation where it says that "(...) so if you change the status of work package A the status of work package B will change automatically to the same." This does not account for all status changes though. Actually, it only changes automatically when you change the status of work package A to a closed status. (#22364 / #39843) #39843)
Maybe we could adjust this text slightly. [https://www.openproject.org/docs/user-guide/work-packages/work-package-relations-hierarchies/#work-package-relations](https://www.openproject.org/docs/user-guide/work-packages/work-package-relations-hierarchies/#work-package-relations)
Feedback by Robin: The current implementation of the "duplicates/duplicated by" relation seems to be fairly unintuitive imo. The duplicated work package's meta status is synchronized but only for meta status closed (e.g. "rejected", "closed") and only on the first switch from meta status open to closed. If changing the duplicated work package's status to e.g. "rejected", the duplicating work package's status will be updated to "rejected" as well but any subsequent changes (e.g. to "closed" or back to "new") are ignored:
Jens explanation from <mention class="mention" data-id="39843" data-type="work_package" data-text="#39843">#39843</mention>:
>
> The behaviour described it the explicitly implemented behaviour. It dates way back so there isn't a specification for this.
>
> Whenever a work packages is "closed", and setting to "rejected" counts as a "closed" status, the duplicated work package gets closed as well (or rejected in this case). Note that this is direction dependent. Only if the work package that is the original is closed will the duplicating work package be closed as well, not the other way around.
>
> I agree that this might be surprising behaviour so I wouldn't argue against changing it. But since it is strictly speaking not a bug, I am altering the type and we would need to specify how the behaviour is to be changed.
Maybe we could adjust this text slightly. [https://www.openproject.org/docs/user-guide/work-packages/work-package-relations-hierarchies/#work-package-relations](https://www.openproject.org/docs/user-guide/work-packages/work-package-relations-hierarchies/#work-package-relations)
Feedback by Robin: The current implementation of the "duplicates/duplicated by" relation seems to be fairly unintuitive imo. The duplicated work package's meta status is synchronized but only for meta status closed (e.g. "rejected", "closed") and only on the first switch from meta status open to closed. If changing the duplicated work package's status to e.g. "rejected", the duplicating work package's status will be updated to "rejected" as well but any subsequent changes (e.g. to "closed" or back to "new") are ignored:
Jens explanation from <mention class="mention" data-id="39843" data-type="work_package" data-text="#39843">#39843</mention>:
>
> The behaviour described it the explicitly implemented behaviour. It dates way back so there isn't a specification for this.
>
> Whenever a work packages is "closed", and setting to "rejected" counts as a "closed" status, the duplicated work package gets closed as well (or rejected in this case). Note that this is direction dependent. Only if the work package that is the original is closed will the duplicating work package be closed as well, not the other way around.
>
> I agree that this might be surprising behaviour so I wouldn't argue against changing it. But since it is strictly speaking not a bug, I am altering the type and we would need to specify how the behaviour is to be changed.